io.net CTO: Third-party authentication provider Okta's rate limiting or causing connection failures

Gaurav, CTO of Solana's eco DePIN protocol io.net, said in an X posting that "the Auth0 process of third-party authentication provider Okta on the working node is experiencing issues as io.net is reaching the rate limit on Okta's end, resulting in a limited authentication rate, and some devices may be accessing the API when they are may experience problems accessing the API and encounter potential connection failures. It is suspected that a malicious user may have impersonated io.net and attacked Okta, subsequently impacting the io.net authentication solution. io.net is actively working with Okta to resolve this issue and prevent such an incident from happening again in the future, and will share more updates to follow."