Logto Outage History
Logto is up right nowPingoru has recorded 52 incidents for Logto: 36 in the last 12 months and 3 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 6 | 0 of 720 (0%) |
| May 2026 | 5 | 0 of 744 (0%) |
| June 2026 | 1 | 0 of 720 (0%) |
| July 2026 | 8 | 1 of 744 (0%) |
| August 2026 | 4 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 114 (0%) |
Incidents, newest first
Minor March 12, 2026 Auth service (US) recovered –
Started Mar 12, 2026, 04:22 PM UTC· resolved Mar 12, 2026, 04:22 PM UTC
No vendor updates were posted for this incident.
Minor March 12, 2026 Auth service (US) recovered –
Started Mar 12, 2026, 03:51 PM UTC· resolved Mar 12, 2026, 03:51 PM UTC
No vendor updates were posted for this incident.
Minor March 5, 2026 Auth service (Japan) recovered –
Started Mar 05, 2026, 10:12 PM UTC· resolved Mar 05, 2026, 10:12 PM UTC
No vendor updates were posted for this incident.
Minor March 3, 2026 Auth service (Japan) recovered –
Started Mar 03, 2026, 01:12 PM UTC· resolved Mar 03, 2026, 01:12 PM UTC
No vendor updates were posted for this incident.
Minor January 9, 2026 Service interruption 1d Status by service (Cloud service), Status by service (Auth service (Europe)), Status by service (Auth service (US)), Status by service (Auth service (Australia)) and 1 more
Started Jan 09, 2026, 12:01 AM UTC· resolved Jan 10, 2026, 12:39 AM UTC
- investigating Jan 09, 2026, 12:01 AM UTC
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.
- investigating Jan 09, 2026, 01:10 AM UTC
The JWT signing key issue has been fixed and authentication services have recovered. We’re monitoring to ensure stability. If you still can’t sign in to the Console, please hard refresh and clear/disable your browser cache (or use an incognito window) and try again.
- resolved Jan 10, 2026, 12:39 AM UTC
Postmortem is available at here.
- investigating Jan 10, 2026, 12:39 AM UTC
Postmortem is available at [here](https://blog.logto.io/postmortem-jwks-cache).
Minor December 11, 2025 Service disruption in AU region 5m Status by service (Auth service (Australia))
Started Dec 11, 2025, 01:13 AM UTC· resolved Dec 11, 2025, 01:18 AM UTC
- investigating Dec 11, 2025, 01:13 AM UTC
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.
- resolved Dec 11, 2025, 01:18 AM UTC
The AU auth service has recovered. Azure completed the database update and traffic is stable again.
Major December 8, 2025 Incorrect US status 1h Status by service (Auth service (US))
Started Dec 08, 2025, 09:34 AM UTC· resolved Dec 08, 2025, 10:34 AM UTC
- investigating Dec 08, 2025, 09:34 AM UTC
The US region is reporting a false outage while services are operating normally. We're investigating.
- investigating Dec 08, 2025, 09:34 AM UTC
The issue was limited to the monitoring endpoint. Tenant traffic was not affected, and the US region is now fully operational.
- resolved Dec 08, 2025, 10:34 AM UTC
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.
Minor December 1, 2025 Abnormal traffic spike affecting some tenants 1h 49m Status by service (Cloud service), Status by service (Auth service (Europe))
Started Dec 01, 2025, 09:56 AM UTC· resolved Dec 01, 2025, 11:45 AM UTC
- investigating Dec 01, 2025, 09:56 AM UTC
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.
- resolved Dec 01, 2025, 11:45 AM UTC
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.
Minor November 26, 2025 US service degraded 41m Status by service (Auth service (US))
Started Nov 26, 2025, 12:10 AM UTC· resolved Nov 26, 2025, 12:51 AM UTC
- investigating Nov 26, 2025, 12:10 AM UTC
We’re seeing elevated errors on the US auth service and are investigating.
- investigating Nov 26, 2025, 12:26 AM UTC
Azure has an active incident in West US 3, and our monitoring shows correlation with the ongoing platform issue. Our systems remain online, but some requests may fail intermittently. We’re monitoring the Azure incident and will update as soon as we have more information.
- resolved Nov 26, 2025, 12:51 AM UTC
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.
Minor November 19, 2025 US auth service degraded 1h 15m Status by service (Auth service (US))
Started Nov 19, 2025, 06:10 PM UTC· resolved Nov 19, 2025, 07:25 PM UTC
- investigating Nov 19, 2025, 06:10 PM UTC
We’re seeing elevated errors on the US auth service and are investigating.
- investigating Nov 19, 2025, 06:24 PM UTC
The monitor The error rate has returned to normal and the service is fully operational. We’re investigating the root cause.
- resolved Nov 19, 2025, 07:25 PM UTC
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.
Major November 18, 2025 Service partially unavailable 2h 50m Status by service (Cloud service), Status by service (Auth service (Europe)), Status by service (Auth service (US)), Status by service (Auth service (Australia)) and 1 more
Started Nov 18, 2025, 11:40 AM UTC· resolved Nov 18, 2025, 02:30 PM UTC
- investigating Nov 18, 2025, 11:40 AM UTC
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.
- investigating Nov 18, 2025, 11:59 AM UTC
Cloudflare services are recovering and most authentication flows are working again. Some regions or tenants may still see intermittent errors while systems settle.
- resolved Nov 18, 2025, 02:30 PM UTC
All authentication services are now fully restored. Traffic is back to normal. We’ll keep monitoring.
Minor November 4, 2025 Performance degradation in some regions 3h Status by service (Auth service (US)), Status by service (Auth service (Japan))
Started Nov 04, 2025, 09:36 PM UTC· resolved Nov 05, 2025, 12:36 AM UTC
- investigating Nov 04, 2025, 09:36 PM UTC
We're investigating elevated error rates and timeouts affecting the US region.
- investigating Nov 04, 2025, 09:50 PM UTC
Japan region is also affected.
- investigating Nov 04, 2025, 09:51 PM UTC
US region is recovered.
- investigating Nov 04, 2025, 10:04 PM UTC
Japan region is recovered. We're investigating the root cause.
- resolved Nov 05, 2025, 12:36 AM UTC
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.
Major July 17, 2025 AU auth service down 1h 10m Status by service (Auth service (Australia))
Started Jul 17, 2025, 02:50 PM UTC· resolved Jul 17, 2025, 04:00 PM UTC
- investigating Jul 17, 2025, 02:50 PM UTC
We acknowledge that the auth service in the Australia region is currently down and are actively investigating the issue.
- investigating Jul 17, 2025, 03:29 PM UTC
We’ve identified the issue and are working on a fix.
- resolved Jul 17, 2025, 04:00 PM UTC
The issue has been fixed. We'll publish a postmortem soon.
Major June 12, 2025 Auth services are down 2h 53m Status by service (Auth service (Europe)), Status by service (Auth service (US)), Status by service (Auth service (Australia)), Status by service (Auth service (Japan))
Started Jun 12, 2025, 06:07 PM UTC· resolved Jun 12, 2025, 09:00 PM UTC
- investigating Jun 12, 2025, 06:07 PM UTC
Auth service APIs are currently returning 500. We are investigating the issue.
- investigating Jun 12, 2025, 06:24 PM UTC
Our Azure services are healthy. We’ve noticed the error was thrown by Cloudflare Workers, and we’re working on locating the issue.
- investigating Jun 12, 2025, 06:35 PM UTC
Cloudflare has acknowledged the incident. We’ll keep you updated. https://www.cloudflarestatus.com/incidents/25r9t0vz99rp
- investigating Jun 12, 2025, 06:58 PM UTC
We’ve implemented a temporary solution, and your service should now be up and running again. There may still be some performance impacts as we continue to work with Cloudflare on a full resolution.
- resolved Jun 12, 2025, 09:00 PM UTC
Update: Cloudflare services have mostly recovered, and your Logto service performance should now be back to normal. The postmortem can be found here.
- resolved Jun 12, 2025, 09:00 PM UTC
Update: Cloudflare services have mostly recovered, and your Logto service performance should now be back to normal. The postmortem can be found [here](https://blog.logto.io/postmortem-june-12-2025).
Major April 15, 2025 Cloud and US service down 14m Status by service (Cloud service), Status by service (Auth service (US))
Started Apr 15, 2025, 05:21 PM UTC· resolved Apr 15, 2025, 05:35 PM UTC
- investigating Apr 15, 2025, 05:21 PM UTC
We acknowledge that our Cloud and US Auth services are currently down, and we are investigating the issue.
- investigating Apr 15, 2025, 05:28 PM UTC
Services are back online.
- resolved Apr 15, 2025, 05:35 PM UTC
Incident Summary Logto Cloud and US Auth services experienced approximately 7 minutes of downtime due to an unplanned disruption during a computing resource SKU upgrade. Root cause The downtime was caused by a SKU change in our cloud provider’s compute resources, which doesn't support 0 downtime. The upgrade process led to temporary unavailability as instances were replaced and rescheduled. Resolution Once the issue was identified, the team monitored the redeployment and confirmed service recovery within minutes. No manual intervention was required beyond observation. Action Items Improve pre-upgrade impact assessment for infrastructure changes. Explore zero-downtime deployment strategies for compute upgrades. We sincerely apologize for the inconvenience and are committed to preventing similar incidents in the future.
- investigating Apr 15, 2025, 05:35 PM UTC
## Incident Summary Logto Cloud and US Auth services experienced approximately 7 minutes of downtime due to an unplanned disruption during a computing resource SKU upgrade. ## Root cause The downtime was caused by a SKU change in our cloud provider’s compute resources, which doesn't support 0 downtime. The upgrade process led to temporary unavailability as instances were replaced and rescheduled. ## Resolution Once the issue was identified, the team monitored the redeployment and confirmed service recovery within minutes. No manual intervention was required beyond observation. ## Action Items - Improve pre-upgrade impact assessment for infrastructure changes. - Explore zero-downtime deployment strategies for compute upgrades. We sincerely apologize for the inconvenience and are committed to preventing similar incidents in the future.