CTO of io.net: The third-party authentication provider Okta's Auth0 process on the worker nodes encountered issues, resulting in io.net hitting the rate limit on the Okta side

ChainCatcher message, Gaurav_IO, the Chief Technology Officer of io.net, posted on Twitter that the third-party authentication provider Okta's Auth0 process on the worker nodes encountered issues, resulting in io.net hitting the rate limit on the Okta side.

This may affect the connectivity of some devices when accessing the API, potentially leading to connection failures with the backend servers.

Although this does not directly threaten the worker nodes or backend servers, it may impact 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.