According to TechFlow, io.net CTO Gaurav_IO tweeted that the Auth0 process of Okta, a third-party authentication provider, on the working node encountered problems, causing io.net to reach the rate limit on the Okta side.

This may affect the connection of some devices when accessing the API, and may cause the connection to the backend server to fail.

Although this does not directly threaten the worker nodes or backend servers, it may affect the normal operation of the worker nodes.

io.net is actively working with Okta to resolve the issue and is taking steps to prevent similar incidents in the future.