Auth service (Japan) recovered
Timeline · 1 update
- investigating Jul 21, 2026, 04:59 PM UTC
Auth service (Japan) went down
Logto had 18 outages in the last 2 years totaling 47h 20m of downtime — averaging 0.7 incidents per month.
There were 18 Logto outages since October 25, 2024 totaling 47h 20m of downtime. Each is summarised below — incident details, duration, and resolution information.
Auth service (Japan) went down
Cloud service went down
Auth service (Europe) recovered
We acknowledge that the EU service is experiencing timeouts. We are investigating the issue and will share updates as soon as we have more information.
We have applied a temporary fix, and the EU service should be operating normally now. We are continuing to investigate the root cause.
Auth service (US) recovered
Website went down
Auth service (Australia) recovered
We’re investigating an issue affecting authentication due to a JWT signing key problem. You may see sign-in failures across Logto services, including the Console.
Postmortem is available at here.
We’re seeing intermittent failures on the AU auth service due to an internal Azure database update. Impact is limited to some requests. We’re tracking the upstream change.
The AU auth service has recovered. Azure completed the database update and traffic is stable again.
The US region is reporting a false outage while services are operating normally. We're investigating.
The issue came from an internal component used by our proxy, which caused incorrect status reporting. We're updating our error handling to prevent this going forward. Service availability was not affected.
We observed a sudden traffic spike from a single tenant that caused elevated response times for some Logto Cloud tenants. The load originated from an unexpected pattern and triggered protective limits on our side. We began investigation immediately.
The abnormal traffic source was contained and affected domains were temporarily blocked. Performance returned to normal for all tenants. We’re contacting the customer involved to verify intent and ensure proper setup going forward.
We’re seeing elevated errors on the US auth service and are investigating.
Azure has mitigated the underlying incident affecting services in West US 3. Our monitoring shows that error rates have returned to normal. If you still see any issues, please let us know.
We’re seeing elevated errors on the US auth service and are investigating.
Our components were healthy throughout. Upstream infrastructure logs showed 5xx responses and timeouts, while our own service logs showed no corresponding errors. This indicates an issue in the underlying platform. We’re continuing to confirm.
We’re experiencing service disruption due to a Cloudflare outage affecting our infrastructure. Authentication requests may fail for some tenants. We’re monitoring the upstream issue and will update once recovery progresses.
All authentication services are now fully restored. Traffic is back to normal. We’ll keep monitoring.
We're investigating elevated error rates and timeouts affecting the US region.
The incident was traced to transient network jitter from our cloud provider. Service performance has recovered, and we’ll continue to monitor for any recurrence.
We acknowledge that the auth service in the Australia region is currently down and are actively investigating the issue.
The issue has been fixed. We'll publish a postmortem soon.
Auth service APIs are currently returning 500. We are investigating the issue.
Update: Cloudflare services have mostly recovered, and your Logto service performance should now be back to normal. The postmortem can be found here.
We noticed that website and blog are not available at this time and we are working on a fix. Your Logto instances and Logto Cloud services are safe.
Blog is up.