Incidents reported on status page for Logto https://status.logto.io/ https://d1lppblt9t2x15.cloudfront.net/logos/cbf43f954be13b7cbfdc9bda14b0fd55.png https://status.logto.io/ en https://status.logto.io/incident/801019 Sat, 10 Jan 2026 00:39:00 -0000 https://status.logto.io/incident/801019#656620ddd26424a534c5c89302a64b75c9707f3dcc055f35f6751c7ea13fa1da Postmortem is available at [here](https://blog.logto.io/postmortem-jwks-cache). https://status.logto.io/incident/801019 Sat, 10 Jan 2026 00:39:00 -0000 https://status.logto.io/incident/801019#656620ddd26424a534c5c89302a64b75c9707f3dcc055f35f6751c7ea13fa1da Postmortem is available at [here](https://blog.logto.io/postmortem-jwks-cache). https://status.logto.io/incident/801019 Sat, 10 Jan 2026 00:39:00 -0000 https://status.logto.io/incident/801019#656620ddd26424a534c5c89302a64b75c9707f3dcc055f35f6751c7ea13fa1da Postmortem is available at [here](https://blog.logto.io/postmortem-jwks-cache). https://status.logto.io/incident/801019 Sat, 10 Jan 2026 00:39:00 -0000 https://status.logto.io/incident/801019#656620ddd26424a534c5c89302a64b75c9707f3dcc055f35f6751c7ea13fa1da Postmortem is available at [here](https://blog.logto.io/postmortem-jwks-cache). https://status.logto.io/incident/801019 Sat, 10 Jan 2026 00:39:00 -0000 https://status.logto.io/incident/801019#656620ddd26424a534c5c89302a64b75c9707f3dcc055f35f6751c7ea13fa1da Postmortem is available at [here](https://blog.logto.io/postmortem-jwks-cache). https://status.logto.io/incident/801019 Fri, 09 Jan 2026 01:10:00 -0000 https://status.logto.io/incident/801019#5088aea92f5737fcaeda77f006fc972d871ea6fdd78a26bd430687d344c2f1e0 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. https://status.logto.io/incident/801019 Fri, 09 Jan 2026 01:10:00 -0000 https://status.logto.io/incident/801019#5088aea92f5737fcaeda77f006fc972d871ea6fdd78a26bd430687d344c2f1e0 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. https://status.logto.io/incident/801019 Fri, 09 Jan 2026 01:10:00 -0000 https://status.logto.io/incident/801019#5088aea92f5737fcaeda77f006fc972d871ea6fdd78a26bd430687d344c2f1e0 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. https://status.logto.io/incident/801019 Fri, 09 Jan 2026 01:10:00 -0000 https://status.logto.io/incident/801019#5088aea92f5737fcaeda77f006fc972d871ea6fdd78a26bd430687d344c2f1e0 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. https://status.logto.io/incident/801019 Fri, 09 Jan 2026 01:10:00 -0000 https://status.logto.io/incident/801019#5088aea92f5737fcaeda77f006fc972d871ea6fdd78a26bd430687d344c2f1e0 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. https://status.logto.io/incident/801019 Fri, 09 Jan 2026 00:01:00 -0000 https://status.logto.io/incident/801019#a2fe552cf393a1803500cf0aca35a468a4ae85970f1e4c4e56414703fd38b572 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. https://status.logto.io/incident/801019 Fri, 09 Jan 2026 00:01:00 -0000 https://status.logto.io/incident/801019#a2fe552cf393a1803500cf0aca35a468a4ae85970f1e4c4e56414703fd38b572 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. https://status.logto.io/incident/801019 Fri, 09 Jan 2026 00:01:00 -0000 https://status.logto.io/incident/801019#a2fe552cf393a1803500cf0aca35a468a4ae85970f1e4c4e56414703fd38b572 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. https://status.logto.io/incident/801019 Fri, 09 Jan 2026 00:01:00 -0000 https://status.logto.io/incident/801019#a2fe552cf393a1803500cf0aca35a468a4ae85970f1e4c4e56414703fd38b572 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. https://status.logto.io/incident/801019 Fri, 09 Jan 2026 00:01:00 -0000 https://status.logto.io/incident/801019#a2fe552cf393a1803500cf0aca35a468a4ae85970f1e4c4e56414703fd38b572 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. https://status.logto.io/incident/785599 Tue, 16 Dec 2025 03:30:00 -0000 https://status.logto.io/incident/785599#4af04f9924d1550db32db9b1afa7840eaa3c423b11c8abb2bf73ff0d07836540 Maintenance completed https://status.logto.io/incident/785599 Tue, 16 Dec 2025 03:30:00 -0000 https://status.logto.io/incident/785599#4af04f9924d1550db32db9b1afa7840eaa3c423b11c8abb2bf73ff0d07836540 Maintenance completed https://status.logto.io/ Tue, 16 Dec 2025 03:20:33 +0000 https://status.logto.io/#4267337354be2569f8a9e5190764525010e32585a8ef8b90db439dec5b188bbb Auth service (Europe) recovered https://status.logto.io/ Tue, 16 Dec 2025 03:19:20 +0000 https://status.logto.io/#4267337354be2569f8a9e5190764525010e32585a8ef8b90db439dec5b188bbb Auth service (Europe) went down https://status.logto.io/incident/785599 Tue, 16 Dec 2025 03:00:00 -0000 https://status.logto.io/incident/785599#c6e87f4b50fb02594f4eda4a89db8dbe588c0a6c7461f5392ed9abb7a7573d82 We’re upgrading our EU database server to a higher performance tier. The change is near-zero downtime, but active connections may briefly reset during the window. All services will resume automatically. https://status.logto.io/incident/785599 Tue, 16 Dec 2025 03:00:00 -0000 https://status.logto.io/incident/785599#c6e87f4b50fb02594f4eda4a89db8dbe588c0a6c7461f5392ed9abb7a7573d82 We’re upgrading our EU database server to a higher performance tier. The change is near-zero downtime, but active connections may briefly reset during the window. All services will resume automatically. https://status.logto.io/incident/784114 Thu, 11 Dec 2025 01:18:00 -0000 https://status.logto.io/incident/784114#f6dbc793b82666b2f99c459bd65a856cc22b201986a6bbe59383ccf9c26812a8 The AU auth service has recovered. Azure completed the database update and traffic is stable again. https://status.logto.io/ Thu, 11 Dec 2025 01:17:39 +0000 https://status.logto.io/#ac1b4ad1b9b893b22c603002fa99161964ce5f4f1e8a656ebd6d84ea34a54b4f Auth service (Australia) recovered https://status.logto.io/ Thu, 11 Dec 2025 01:13:47 +0000 https://status.logto.io/#ac1b4ad1b9b893b22c603002fa99161964ce5f4f1e8a656ebd6d84ea34a54b4f Auth service (Australia) went down https://status.logto.io/incident/784114 Thu, 11 Dec 2025 01:13:00 -0000 https://status.logto.io/incident/784114#71e2b6dc9432af099e82d5d82d41d15e5306de0f9e2aa6897b29dfcb797999c0 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. https://status.logto.io/incident/782176 Mon, 08 Dec 2025 10:34:00 -0000 https://status.logto.io/incident/782176#0f54dfb4dbd17038a59e99354935713dfe82b1fa665b039ef2c794b0144c7afa 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. https://status.logto.io/ Mon, 08 Dec 2025 10:23:22 +0000 https://status.logto.io/#d8ade8f8f8aa66dde6e42314fd10fb10b4579dcd54db78dc1395414afa74cc3c Auth service (US) recovered https://status.logto.io/ Mon, 08 Dec 2025 09:34:20 +0000 https://status.logto.io/#d8ade8f8f8aa66dde6e42314fd10fb10b4579dcd54db78dc1395414afa74cc3c Auth service (US) went down https://status.logto.io/incident/782176 Mon, 08 Dec 2025 09:34:00 -0000 https://status.logto.io/incident/782176#fc13b1d39ba56101aa2e48688db10dc0151e2149e0e68a5183482aae25dcca6b The issue was limited to the monitoring endpoint. Tenant traffic was not affected, and the US region is now fully operational. https://status.logto.io/incident/782176 Mon, 08 Dec 2025 09:34:00 -0000 https://status.logto.io/incident/782176#a9c0bb4ba13e2293acd205580d79d209e0baa293c33d33e94b657daa00f49e2b The US region is reporting a false outage while services are operating normally. We're investigating. https://status.logto.io/incident/777555 Mon, 01 Dec 2025 11:45:00 -0000 https://status.logto.io/incident/777555#88e4a571d9b033bea093ea6105d126dd5c157b9d200f86765e351f81235c1df3 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. https://status.logto.io/incident/777555 Mon, 01 Dec 2025 11:45:00 -0000 https://status.logto.io/incident/777555#88e4a571d9b033bea093ea6105d126dd5c157b9d200f86765e351f81235c1df3 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. https://status.logto.io/incident/777555 Mon, 01 Dec 2025 09:56:00 -0000 https://status.logto.io/incident/777555#95b837bba92c6e3b2fc36d3aca26a70a52c8c33407c3bd7a2148e38dc6ce5cb9 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. https://status.logto.io/incident/777555 Mon, 01 Dec 2025 09:56:00 -0000 https://status.logto.io/incident/777555#95b837bba92c6e3b2fc36d3aca26a70a52c8c33407c3bd7a2148e38dc6ce5cb9 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. https://status.logto.io/incident/774258 Wed, 26 Nov 2025 00:51:00 -0000 https://status.logto.io/incident/774258#c3c36d3789e84db9cbd0b063858e84e05ec41aca74e05a7bbe22065c4b8c7bb8 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. https://status.logto.io/incident/774258 Wed, 26 Nov 2025 00:26:00 -0000 https://status.logto.io/incident/774258#d69b43a78c767ddc9584dd571dce5cbda13a530decfe4f5a5368e99bcc73fe2b 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. https://status.logto.io/incident/774258 Wed, 26 Nov 2025 00:10:00 -0000 https://status.logto.io/incident/774258#880ede383b88b42d531b28e412c649c42efcadabc4c3e6f32378c90490743ebd We’re seeing elevated errors on the US auth service and are investigating. https://status.logto.io/incident/770389 Wed, 19 Nov 2025 19:25:00 -0000 https://status.logto.io/incident/770389#e1ec2b01fc463031fc16f44cb99896a7ae88aa1930698cf65b679ae91cfbf8e8 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. https://status.logto.io/incident/770389 Wed, 19 Nov 2025 18:24:00 -0000 https://status.logto.io/incident/770389#90157f7e78b5ee6cccf731e707638f11dc779ad52f473842a4ba79183fed7a56 The monitor The error rate has returned to normal and the service is fully operational. We’re investigating the root cause. https://status.logto.io/ Wed, 19 Nov 2025 18:23:36 +0000 https://status.logto.io/#f081c038c83890f20142ece4cd782f6ade8d5ac7b577f116c57f3139601a0a54 Auth service (US) recovered https://status.logto.io/ Wed, 19 Nov 2025 18:18:27 +0000 https://status.logto.io/#f081c038c83890f20142ece4cd782f6ade8d5ac7b577f116c57f3139601a0a54 Auth service (US) went down https://status.logto.io/ Wed, 19 Nov 2025 18:17:04 +0000 https://status.logto.io/#c1ee07e1f8923e7af7e81b6323670604b3c3c4384b45b37a9667a139329b5452 Auth service (US) recovered https://status.logto.io/ Wed, 19 Nov 2025 18:10:26 +0000 https://status.logto.io/#c1ee07e1f8923e7af7e81b6323670604b3c3c4384b45b37a9667a139329b5452 Auth service (US) went down https://status.logto.io/incident/770389 Wed, 19 Nov 2025 18:10:00 -0000 https://status.logto.io/incident/770389#17699296fc996280e932f1d4fa569202524514d80f2cff167615a05dceb0ecab We’re seeing elevated errors on the US auth service and are investigating. https://status.logto.io/incident/769542 Tue, 18 Nov 2025 14:30:00 -0000 https://status.logto.io/incident/769542#091d0f29c1b624d52e0379ad47c8b78695cd9774c46a40c7e3873b2cc475f213 All authentication services are now fully restored. Traffic is back to normal. We’ll keep monitoring. https://status.logto.io/incident/769542 Tue, 18 Nov 2025 14:30:00 -0000 https://status.logto.io/incident/769542#091d0f29c1b624d52e0379ad47c8b78695cd9774c46a40c7e3873b2cc475f213 All authentication services are now fully restored. Traffic is back to normal. We’ll keep monitoring. https://status.logto.io/incident/769542 Tue, 18 Nov 2025 14:30:00 -0000 https://status.logto.io/incident/769542#091d0f29c1b624d52e0379ad47c8b78695cd9774c46a40c7e3873b2cc475f213 All authentication services are now fully restored. Traffic is back to normal. We’ll keep monitoring. https://status.logto.io/incident/769542 Tue, 18 Nov 2025 14:30:00 -0000 https://status.logto.io/incident/769542#091d0f29c1b624d52e0379ad47c8b78695cd9774c46a40c7e3873b2cc475f213 All authentication services are now fully restored. Traffic is back to normal. We’ll keep monitoring. https://status.logto.io/incident/769542 Tue, 18 Nov 2025 14:30:00 -0000 https://status.logto.io/incident/769542#091d0f29c1b624d52e0379ad47c8b78695cd9774c46a40c7e3873b2cc475f213 All authentication services are now fully restored. Traffic is back to normal. We’ll keep monitoring. https://status.logto.io/ Tue, 18 Nov 2025 11:59:37 +0000 https://status.logto.io/#b9bfb19d5bf42a296d9a7a7569c218189353f8513f2b69eaadf4757f57d36d22 Cloud service recovered https://status.logto.io/ Tue, 18 Nov 2025 11:59:09 +0000 https://status.logto.io/#b51943738aef4bdd674a85668e72503378122c16a68cdddd533b75be71d1bc8c Auth service (Australia) recovered https://status.logto.io/incident/769542 Tue, 18 Nov 2025 11:59:00 -0000 https://status.logto.io/incident/769542#688b52efc7b66ca62dd67ced0141a0ea1a21f03abe420e40dc3b4d4a84cd0d32 Cloudflare services are recovering and most authentication flows are working again. Some regions or tenants may still see intermittent errors while systems settle. https://status.logto.io/incident/769542 Tue, 18 Nov 2025 11:59:00 -0000 https://status.logto.io/incident/769542#688b52efc7b66ca62dd67ced0141a0ea1a21f03abe420e40dc3b4d4a84cd0d32 Cloudflare services are recovering and most authentication flows are working again. Some regions or tenants may still see intermittent errors while systems settle. https://status.logto.io/incident/769542 Tue, 18 Nov 2025 11:59:00 -0000 https://status.logto.io/incident/769542#688b52efc7b66ca62dd67ced0141a0ea1a21f03abe420e40dc3b4d4a84cd0d32 Cloudflare services are recovering and most authentication flows are working again. Some regions or tenants may still see intermittent errors while systems settle. https://status.logto.io/incident/769542 Tue, 18 Nov 2025 11:59:00 -0000 https://status.logto.io/incident/769542#688b52efc7b66ca62dd67ced0141a0ea1a21f03abe420e40dc3b4d4a84cd0d32 Cloudflare services are recovering and most authentication flows are working again. Some regions or tenants may still see intermittent errors while systems settle. https://status.logto.io/incident/769542 Tue, 18 Nov 2025 11:59:00 -0000 https://status.logto.io/incident/769542#688b52efc7b66ca62dd67ced0141a0ea1a21f03abe420e40dc3b4d4a84cd0d32 Cloudflare services are recovering and most authentication flows are working again. Some regions or tenants may still see intermittent errors while systems settle. https://status.logto.io/ Tue, 18 Nov 2025 11:53:11 +0000 https://status.logto.io/#09de1a1e7dcdca14caae6efba6e126cff2b6f80ef7371417ee59e3baa55c1615 Auth service (US) recovered https://status.logto.io/ Tue, 18 Nov 2025 11:52:30 +0000 https://status.logto.io/#915d37583bf41c50cb8c110c88e29bbeb4547e6b5ee0f926ffe5e01793511a29 Auth service (Japan) recovered https://status.logto.io/ Tue, 18 Nov 2025 11:42:04 +0000 https://status.logto.io/#09de1a1e7dcdca14caae6efba6e126cff2b6f80ef7371417ee59e3baa55c1615 Auth service (US) went down https://status.logto.io/ Tue, 18 Nov 2025 11:40:43 +0000 https://status.logto.io/#915d37583bf41c50cb8c110c88e29bbeb4547e6b5ee0f926ffe5e01793511a29 Auth service (Japan) went down https://status.logto.io/ Tue, 18 Nov 2025 11:40:13 +0000 https://status.logto.io/#b9bfb19d5bf42a296d9a7a7569c218189353f8513f2b69eaadf4757f57d36d22 Cloud service went down https://status.logto.io/incident/769542 Tue, 18 Nov 2025 11:40:00 -0000 https://status.logto.io/incident/769542#ff7538ef0f7d8470959d9197b83fd9b4a31ae117306be8b855f338f841073614 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. https://status.logto.io/incident/769542 Tue, 18 Nov 2025 11:40:00 -0000 https://status.logto.io/incident/769542#ff7538ef0f7d8470959d9197b83fd9b4a31ae117306be8b855f338f841073614 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. https://status.logto.io/incident/769542 Tue, 18 Nov 2025 11:40:00 -0000 https://status.logto.io/incident/769542#ff7538ef0f7d8470959d9197b83fd9b4a31ae117306be8b855f338f841073614 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. https://status.logto.io/incident/769542 Tue, 18 Nov 2025 11:40:00 -0000 https://status.logto.io/incident/769542#ff7538ef0f7d8470959d9197b83fd9b4a31ae117306be8b855f338f841073614 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. https://status.logto.io/incident/769542 Tue, 18 Nov 2025 11:40:00 -0000 https://status.logto.io/incident/769542#ff7538ef0f7d8470959d9197b83fd9b4a31ae117306be8b855f338f841073614 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. https://status.logto.io/ Tue, 18 Nov 2025 11:39:26 +0000 https://status.logto.io/#b51943738aef4bdd674a85668e72503378122c16a68cdddd533b75be71d1bc8c Auth service (Australia) went down https://status.logto.io/incident/758037 Wed, 05 Nov 2025 00:36:00 -0000 https://status.logto.io/incident/758037#96c2842a46e88146c05ebdb9dbc319c27fb95ff14512804accd33e9552a7f541 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. https://status.logto.io/incident/758037 Wed, 05 Nov 2025 00:36:00 -0000 https://status.logto.io/incident/758037#96c2842a46e88146c05ebdb9dbc319c27fb95ff14512804accd33e9552a7f541 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. https://status.logto.io/incident/758037 Tue, 04 Nov 2025 22:04:00 -0000 https://status.logto.io/incident/758037#662dd7549106001098b8411e4614eefadcc597b0031b6ab233792168881cc028 Japan region is recovered. We're investigating the root cause. https://status.logto.io/incident/758037 Tue, 04 Nov 2025 21:51:00 -0000 https://status.logto.io/incident/758037#365a5635c2d783dde51b9a3fbfb57e6f06787eb91d3ba037865cc908da859cd8 US region is recovered. https://status.logto.io/incident/758037 Tue, 04 Nov 2025 21:51:00 -0000 https://status.logto.io/incident/758037#365a5635c2d783dde51b9a3fbfb57e6f06787eb91d3ba037865cc908da859cd8 US region is recovered. https://status.logto.io/incident/758037 Tue, 04 Nov 2025 21:50:00 -0000 https://status.logto.io/incident/758037#bc6948b33518a07ccd029b349d8d915e8eb401a52e568a18eb206459342fdfe8 Japan region is also affected. https://status.logto.io/incident/758037 Tue, 04 Nov 2025 21:50:00 -0000 https://status.logto.io/incident/758037#bc6948b33518a07ccd029b349d8d915e8eb401a52e568a18eb206459342fdfe8 Japan region is also affected. https://status.logto.io/incident/758037 Tue, 04 Nov 2025 21:36:00 -0000 https://status.logto.io/incident/758037#72d51ccf03c21d8e9063a7d67c7be667b2b74b3ed0a2c7de8163e6ee53b81b6d We're investigating elevated error rates and timeouts affecting the US region. https://status.logto.io/incident/621448 Thu, 17 Jul 2025 16:00:00 -0000 https://status.logto.io/incident/621448#32d1fdba33759ca6b226a760b229d0e3e5ae8c46ff1acb1ab4415f9a51e2145e The issue has been fixed. We'll publish a postmortem soon. https://status.logto.io/incident/621448 Thu, 17 Jul 2025 15:29:00 -0000 https://status.logto.io/incident/621448#cf2036f0db1b5626aa49b40aebfdb4891028582d4e1423562db4e75ea350bb1c We’ve identified the issue and are working on a fix. https://status.logto.io/incident/621448 Thu, 17 Jul 2025 14:50:00 -0000 https://status.logto.io/incident/621448#4427b5bd57bf5a50f505c8208de005addadf24b6092f9022ffc6c3354dac7ddd We acknowledge that the auth service in the Australia region is currently down and are actively investigating the issue. https://status.logto.io/incident/601737 Thu, 12 Jun 2025 21:00:00 -0000 https://status.logto.io/incident/601737#239d90f581878f46aecec31ec5058afa14ebe1ed4ebe29f4c34e4f2e6aea6ee7 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). https://status.logto.io/incident/601737 Thu, 12 Jun 2025 21:00:00 -0000 https://status.logto.io/incident/601737#239d90f581878f46aecec31ec5058afa14ebe1ed4ebe29f4c34e4f2e6aea6ee7 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). https://status.logto.io/incident/601737 Thu, 12 Jun 2025 21:00:00 -0000 https://status.logto.io/incident/601737#239d90f581878f46aecec31ec5058afa14ebe1ed4ebe29f4c34e4f2e6aea6ee7 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). https://status.logto.io/incident/601737 Thu, 12 Jun 2025 21:00:00 -0000 https://status.logto.io/incident/601737#239d90f581878f46aecec31ec5058afa14ebe1ed4ebe29f4c34e4f2e6aea6ee7 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). https://status.logto.io/incident/601737 Thu, 12 Jun 2025 18:58:00 -0000 https://status.logto.io/incident/601737#cb9b218c0b0adb1eced54cc5e22d34560eef7b1ceb15c18a81ea63d5296164e9 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. https://status.logto.io/incident/601737 Thu, 12 Jun 2025 18:58:00 -0000 https://status.logto.io/incident/601737#cb9b218c0b0adb1eced54cc5e22d34560eef7b1ceb15c18a81ea63d5296164e9 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. https://status.logto.io/incident/601737 Thu, 12 Jun 2025 18:58:00 -0000 https://status.logto.io/incident/601737#cb9b218c0b0adb1eced54cc5e22d34560eef7b1ceb15c18a81ea63d5296164e9 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. https://status.logto.io/incident/601737 Thu, 12 Jun 2025 18:58:00 -0000 https://status.logto.io/incident/601737#cb9b218c0b0adb1eced54cc5e22d34560eef7b1ceb15c18a81ea63d5296164e9 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. https://status.logto.io/incident/601737 Thu, 12 Jun 2025 18:35:00 -0000 https://status.logto.io/incident/601737#d045b0f3523ec39765734eea54267da1d48d99ea4e6b663e22f58b018ac9808b Cloudflare has acknowledged the incident. We’ll keep you updated. https://www.cloudflarestatus.com/incidents/25r9t0vz99rp https://status.logto.io/incident/601737 Thu, 12 Jun 2025 18:35:00 -0000 https://status.logto.io/incident/601737#d045b0f3523ec39765734eea54267da1d48d99ea4e6b663e22f58b018ac9808b Cloudflare has acknowledged the incident. We’ll keep you updated. https://www.cloudflarestatus.com/incidents/25r9t0vz99rp https://status.logto.io/incident/601737 Thu, 12 Jun 2025 18:35:00 -0000 https://status.logto.io/incident/601737#d045b0f3523ec39765734eea54267da1d48d99ea4e6b663e22f58b018ac9808b Cloudflare has acknowledged the incident. We’ll keep you updated. https://www.cloudflarestatus.com/incidents/25r9t0vz99rp https://status.logto.io/incident/601737 Thu, 12 Jun 2025 18:35:00 -0000 https://status.logto.io/incident/601737#d045b0f3523ec39765734eea54267da1d48d99ea4e6b663e22f58b018ac9808b Cloudflare has acknowledged the incident. We’ll keep you updated. https://www.cloudflarestatus.com/incidents/25r9t0vz99rp https://status.logto.io/incident/601737 Thu, 12 Jun 2025 18:24:00 -0000 https://status.logto.io/incident/601737#c1bff2160357682a09c79974d8cd375d2eac07864e66db3f253c2b89e7064ef9 Our Azure services are healthy. We’ve noticed the error was thrown by Cloudflare Workers, and we’re working on locating the issue. https://status.logto.io/incident/601737 Thu, 12 Jun 2025 18:24:00 -0000 https://status.logto.io/incident/601737#c1bff2160357682a09c79974d8cd375d2eac07864e66db3f253c2b89e7064ef9 Our Azure services are healthy. We’ve noticed the error was thrown by Cloudflare Workers, and we’re working on locating the issue. https://status.logto.io/incident/601737 Thu, 12 Jun 2025 18:24:00 -0000 https://status.logto.io/incident/601737#c1bff2160357682a09c79974d8cd375d2eac07864e66db3f253c2b89e7064ef9 Our Azure services are healthy. We’ve noticed the error was thrown by Cloudflare Workers, and we’re working on locating the issue. https://status.logto.io/incident/601737 Thu, 12 Jun 2025 18:24:00 -0000 https://status.logto.io/incident/601737#c1bff2160357682a09c79974d8cd375d2eac07864e66db3f253c2b89e7064ef9 Our Azure services are healthy. We’ve noticed the error was thrown by Cloudflare Workers, and we’re working on locating the issue. https://status.logto.io/incident/601737 Thu, 12 Jun 2025 18:07:00 -0000 https://status.logto.io/incident/601737#c12b800190b7c85a55ae1cc6af52dec3a0e3b0ade5a9394ae5623d49c83f170c Auth service APIs are currently returning 500. We are investigating the issue. https://status.logto.io/incident/601737 Thu, 12 Jun 2025 18:07:00 -0000 https://status.logto.io/incident/601737#c12b800190b7c85a55ae1cc6af52dec3a0e3b0ade5a9394ae5623d49c83f170c Auth service APIs are currently returning 500. We are investigating the issue. https://status.logto.io/incident/601737 Thu, 12 Jun 2025 18:07:00 -0000 https://status.logto.io/incident/601737#c12b800190b7c85a55ae1cc6af52dec3a0e3b0ade5a9394ae5623d49c83f170c Auth service APIs are currently returning 500. We are investigating the issue. https://status.logto.io/incident/601737 Thu, 12 Jun 2025 18:07:00 -0000 https://status.logto.io/incident/601737#c12b800190b7c85a55ae1cc6af52dec3a0e3b0ade5a9394ae5623d49c83f170c Auth service APIs are currently returning 500. We are investigating the issue. https://status.logto.io/incident/545773 Tue, 15 Apr 2025 17:35:00 -0000 https://status.logto.io/incident/545773#ece3c6eedc718f62f8f71a8601be19efc917b2061d9daa6cf03d01e318628569 ## 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. https://status.logto.io/incident/545773 Tue, 15 Apr 2025 17:35:00 -0000 https://status.logto.io/incident/545773#ece3c6eedc718f62f8f71a8601be19efc917b2061d9daa6cf03d01e318628569 ## 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. https://status.logto.io/incident/545773 Tue, 15 Apr 2025 17:28:00 -0000 https://status.logto.io/incident/545773#9bd8f2dd3b1286097c7dd11f84c078cd9b592ee352a162b948ebcaed60541755 Services are back online. https://status.logto.io/incident/545773 Tue, 15 Apr 2025 17:28:00 -0000 https://status.logto.io/incident/545773#9bd8f2dd3b1286097c7dd11f84c078cd9b592ee352a162b948ebcaed60541755 Services are back online. https://status.logto.io/incident/545773 Tue, 15 Apr 2025 17:21:00 -0000 https://status.logto.io/incident/545773#8f69290d555678117e43609e7850eb5ff4ae38b01953cfbaee7bfd8dc747500c We acknowledge that our Cloud and US Auth services are currently down, and we are investigating the issue. https://status.logto.io/incident/545773 Tue, 15 Apr 2025 17:21:00 -0000 https://status.logto.io/incident/545773#8f69290d555678117e43609e7850eb5ff4ae38b01953cfbaee7bfd8dc747500c We acknowledge that our Cloud and US Auth services are currently down, and we are investigating the issue. https://status.logto.io/incident/450597 Fri, 25 Oct 2024 22:07:00 -0000 https://status.logto.io/incident/450597#6a51f5e71afe94ddc1b3af5e3ce278dd95c2e6fa7d0df357ae0910f718dc500d Blog is up. https://status.logto.io/incident/450597 Fri, 25 Oct 2024 15:23:00 -0000 https://status.logto.io/incident/450597#65ac799994b2dbd9b5dbad91c130c14aa08d1497c7c0262a645ac8d5fc2ac442 The website has been recovered. The blog is still experiencing downtime. https://status.logto.io/incident/450597 Fri, 25 Oct 2024 14:59:00 -0000 https://status.logto.io/incident/450597#29ced484e2e548f9d3a54ebf49c2d59be1ef8f463febf911de88ee1f8b4c0f5c 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. https://status.logto.io/incident/399966 Thu, 18 Jul 2024 12:00:00 -0000 https://status.logto.io/incident/399966#1d4847ba03e2587683426f4ce49945f979033acdd07d21b59add8ce6a3880d85 You can find the postmortem [here](https://blog.logto.io/postmortem-database-breaking-change-causes-500-error/?ref=status). https://status.logto.io/incident/399966 Thu, 18 Jul 2024 12:00:00 -0000 https://status.logto.io/incident/399966#1d4847ba03e2587683426f4ce49945f979033acdd07d21b59add8ce6a3880d85 You can find the postmortem [here](https://blog.logto.io/postmortem-database-breaking-change-causes-500-error/?ref=status). https://status.logto.io/incident/399966 Thu, 18 Jul 2024 09:32:00 -0000 https://status.logto.io/incident/399966#3e43b90cf5ef89f5487c6b8f109388bc90982010155a8fcbe3f326d3d0e322a8 The sign-in experience has recovered. **Cause**: During a recent deployment, a breaking database schema change caused an exception when swapping between the staging and production environments. We apologize for any inconvenience this may have caused. We are currently discussing and planning preventative measures to ensure this issue does not occur again in the future. These measures will be implemented as soon as possible. https://status.logto.io/incident/399966 Thu, 18 Jul 2024 09:32:00 -0000 https://status.logto.io/incident/399966#3e43b90cf5ef89f5487c6b8f109388bc90982010155a8fcbe3f326d3d0e322a8 The sign-in experience has recovered. **Cause**: During a recent deployment, a breaking database schema change caused an exception when swapping between the staging and production environments. We apologize for any inconvenience this may have caused. We are currently discussing and planning preventative measures to ensure this issue does not occur again in the future. These measures will be implemented as soon as possible. https://status.logto.io/incident/399966 Thu, 18 Jul 2024 08:57:00 -0000 https://status.logto.io/incident/399966#4f1d408181f4556f325ec52dbaed417a2f6a3b2a2648ebed78185f8d7817db36 The sign-in experience shows error code 500. https://status.logto.io/incident/399966 Thu, 18 Jul 2024 08:57:00 -0000 https://status.logto.io/incident/399966#4f1d408181f4556f325ec52dbaed417a2f6a3b2a2648ebed78185f8d7817db36 The sign-in experience shows error code 500. https://status.logto.io/incident/394292 Sat, 06 Jul 2024 02:35:00 -0000 https://status.logto.io/incident/394292#8bf70b557bc381d93fb1c6b31d3244504bff28bc08d491cf51088065f7016ebd We've removed some false positives on timeout. https://status.logto.io/incident/394292 Sat, 06 Jul 2024 02:35:00 -0000 https://status.logto.io/incident/394292#8bf70b557bc381d93fb1c6b31d3244504bff28bc08d491cf51088065f7016ebd We've removed some false positives on timeout. https://status.logto.io/incident/389705 Wed, 26 Jun 2024 09:35:00 -0000 https://status.logto.io/incident/389705#a6a44d2ecfc64b86623f80d6825645e4d1ee43e99e8d88ce747620301ca69417 The US region database (Azure) experienced an unexpected "Updating" status, causing a service outage for about 1 minute. The issue has now been resolved. https://status.logto.io/incident/378536 Mon, 03 Jun 2024 04:03:00 -0000 https://status.logto.io/incident/378536#7e23b910b7312e15d0d5525cbeafb90bf7fe15c26f5bc4fd26fe4c6fd0895690 We've removed a false positive incident for accuracy. https://status.logto.io/incident/378536 Mon, 03 Jun 2024 04:03:00 -0000 https://status.logto.io/incident/378536#7e23b910b7312e15d0d5525cbeafb90bf7fe15c26f5bc4fd26fe4c6fd0895690 We've removed a false positive incident for accuracy. https://status.logto.io/incident/378536 Mon, 03 Jun 2024 04:03:00 -0000 https://status.logto.io/incident/378536#7e23b910b7312e15d0d5525cbeafb90bf7fe15c26f5bc4fd26fe4c6fd0895690 We've removed a false positive incident for accuracy. https://status.logto.io/incident/371064 Sat, 18 May 2024 01:50:00 -0000 https://status.logto.io/incident/371064#9f56f09ecfb95ec91fb16bef658fdef3f5888ddbe901a50bd97f3a076c6772fd We've noticed some false negatives of downtime. We're taking a look on the logs to find out the cause. https://status.logto.io/incident/371064 Sat, 18 May 2024 01:50:00 -0000 https://status.logto.io/incident/371064#9f56f09ecfb95ec91fb16bef658fdef3f5888ddbe901a50bd97f3a076c6772fd We've noticed some false negatives of downtime. We're taking a look on the logs to find out the cause. https://status.logto.io/incident/366902 Thu, 09 May 2024 04:42:00 -0000 https://status.logto.io/incident/366902#e55645c6006085922b1ffb3e977f024b7e6ff6ae61063c074cdc7b39e5d84370 The Azure database met some unknown issues and it's recovered. We are discussing about the mitigate plans including relocating database to a region that supports zone redundant high availability. https://status.logto.io/incident/366902 Thu, 09 May 2024 04:42:00 -0000 https://status.logto.io/incident/366902#e55645c6006085922b1ffb3e977f024b7e6ff6ae61063c074cdc7b39e5d84370 The Azure database met some unknown issues and it's recovered. We are discussing about the mitigate plans including relocating database to a region that supports zone redundant high availability. https://status.logto.io/incident/366902 Thu, 09 May 2024 04:41:00 -0000 https://status.logto.io/incident/366902#18b04424e62504c3a35920ee7235fb33da9d3c7081677159862b53e663560dc7 We've noticed that our services are randomly responding 503. We are investigating it. https://status.logto.io/incident/366902 Thu, 09 May 2024 04:41:00 -0000 https://status.logto.io/incident/366902#18b04424e62504c3a35920ee7235fb33da9d3c7081677159862b53e663560dc7 We've noticed that our services are randomly responding 503. We are investigating it. https://status.logto.io/incident/361697 Sun, 28 Apr 2024 09:51:00 -0000 https://status.logto.io/incident/361697#1e5a39adf0baf515851c2c672f5be2c8726a6f239f3678dc97655d3ca7957ed6 **Root Cause:** Our Azure database experienced downtime due to an unknown issue. Here's the communication we received from Azure: > **Unknown Reason** > > Status: At 08:18 PM, Saturday, 27 April 2024 UTC, the Azure monitoring system detected an issue with your resource logto-eu: Your Azure Database for PostgreSQL - Flexible server is currently unavailable. We are actively working to resolve the problem. We're contacting the Azure team to see how we can mitigate similar issues in the future. https://status.logto.io/incident/361697 Sun, 28 Apr 2024 00:00:00 -0000 https://status.logto.io/incident/361697#a4f2f99d5f15278b5c47a768e1225c2f59297254996a959575d1d7ce56a3b7a9 We've noticed the increasing status code 500 error reports and we're investigating it. https://status.logto.io/incident/343488 Wed, 20 Mar 2024 09:04:00 -0000 https://status.logto.io/incident/343488#5f026ef138a131e7bad5de61033ef6826ce7ca0e50e29ad09aa78cac26b0a8ce ## Background We have recently resolved a bug related to the issuance of access tokens when using custom domain endpoints. Previously, even when a custom domain endpoint was used to request an access token, the issuer (the `iss` field) would still default to our standard domain (tenant-id.logto.app). We are pleased to announce that this issue has been fixed, and now the `iss` field will automatically reflect the domain used in the request. ## Action required If you are using a custom domain and have implemented `iss` field validation in your code, you will need to make an update. This change is critical for those who are validating the `iss` field against the expected issuer URL. ## How to proceed To align with this update, please ensure that the expected value for the `iss` field in your resource server or any relevant components is set to your custom domain format. For example, if your Logto custom domain is https://auth.your-domain.com/, it should now be https://auth.your-domain.com/oidc. --- This change was intended as a bug fix; however, it may lead to a breaking change in your existing code. If you are affected, please do not hesitate to contact us so we can make things right. We apologize for any inconvenience it may have caused. https://status.logto.io/incident/343488 Wed, 20 Mar 2024 09:04:00 -0000 https://status.logto.io/incident/343488#5f026ef138a131e7bad5de61033ef6826ce7ca0e50e29ad09aa78cac26b0a8ce ## Background We have recently resolved a bug related to the issuance of access tokens when using custom domain endpoints. Previously, even when a custom domain endpoint was used to request an access token, the issuer (the `iss` field) would still default to our standard domain (tenant-id.logto.app). We are pleased to announce that this issue has been fixed, and now the `iss` field will automatically reflect the domain used in the request. ## Action required If you are using a custom domain and have implemented `iss` field validation in your code, you will need to make an update. This change is critical for those who are validating the `iss` field against the expected issuer URL. ## How to proceed To align with this update, please ensure that the expected value for the `iss` field in your resource server or any relevant components is set to your custom domain format. For example, if your Logto custom domain is https://auth.your-domain.com/, it should now be https://auth.your-domain.com/oidc. --- This change was intended as a bug fix; however, it may lead to a breaking change in your existing code. If you are affected, please do not hesitate to contact us so we can make things right. We apologize for any inconvenience it may have caused. https://status.logto.io/incident/328835 Wed, 20 Mar 2024 09:00:00 -0000 https://status.logto.io/incident/328835#44f7753c23d7830630c176fbfa03c7601ea112ba3e9d2cbe2e4d9449f0349dfa The false positive timeout issue has been mitigated recently after adding BetterStack IPs to the whitelist. We've cleaned up those incidents for accuracy. We'll keep an eye on it. https://status.logto.io/incident/328835 Wed, 20 Mar 2024 09:00:00 -0000 https://status.logto.io/incident/328835#44f7753c23d7830630c176fbfa03c7601ea112ba3e9d2cbe2e4d9449f0349dfa The false positive timeout issue has been mitigated recently after adding BetterStack IPs to the whitelist. We've cleaned up those incidents for accuracy. We'll keep an eye on it. https://status.logto.io/incident/328835 Mon, 19 Feb 2024 06:43:00 -0000 https://status.logto.io/incident/328835#d8835c0afa8713aea5a6467f0abec0f0f8418cfc3d149a2c907fa473317caa9d We have recently detected several false positives related to timeouts. Although the services were operational, incidents were still triggered. We are investigating this to ensure a more accurate display of status. https://status.logto.io/incident/328835 Mon, 19 Feb 2024 06:43:00 -0000 https://status.logto.io/incident/328835#d8835c0afa8713aea5a6467f0abec0f0f8418cfc3d149a2c907fa473317caa9d We have recently detected several false positives related to timeouts. Although the services were operational, incidents were still triggered. We are investigating this to ensure a more accurate display of status. https://status.logto.io/incident/311523 Fri, 12 Jan 2024 10:34:00 -0000 https://status.logto.io/incident/311523#4c7d88596599ced56f3bd1b623ae7a67323eb0eeae36134677181d1d7675f209 Postmortem is available [here](https://blog.logto.io/postmortem-bad-gateway/). https://status.logto.io/incident/311523 Fri, 12 Jan 2024 10:34:00 -0000 https://status.logto.io/incident/311523#4c7d88596599ced56f3bd1b623ae7a67323eb0eeae36134677181d1d7675f209 Postmortem is available [here](https://blog.logto.io/postmortem-bad-gateway/). https://status.logto.io/incident/311523 Fri, 12 Jan 2024 00:49:00 -0000 https://status.logto.io/incident/311523#830726293191bb759035ea296c4ea9d50b2dae81bc81def8481fd653c17dca02 The issue has been resolved. Services are getting gradually recovered. A postmortem will be posted soon. https://status.logto.io/incident/311523 Fri, 12 Jan 2024 00:49:00 -0000 https://status.logto.io/incident/311523#830726293191bb759035ea296c4ea9d50b2dae81bc81def8481fd653c17dca02 The issue has been resolved. Services are getting gradually recovered. A postmortem will be posted soon. https://status.logto.io/incident/311523 Fri, 12 Jan 2024 00:24:00 -0000 https://status.logto.io/incident/311523#0eac2bd765689b05f558ef22f08fe3a6e295878cbdc8d0a9938ae938cfcd5231 We have identified the error. We are working on the fix. https://status.logto.io/incident/311523 Fri, 12 Jan 2024 00:24:00 -0000 https://status.logto.io/incident/311523#0eac2bd765689b05f558ef22f08fe3a6e295878cbdc8d0a9938ae938cfcd5231 We have identified the error. We are working on the fix. https://status.logto.io/incident/311523 Thu, 11 Jan 2024 15:42:00 -0000 https://status.logto.io/incident/311523#b46c8ae3ccdee83bb7d55a36f8f28a23d17a1770a2f53fcf50dcee5caf7c4cd0 Logto services may return 502 bad gateway error for some users. We are taking a look on it. https://status.logto.io/incident/311523 Thu, 11 Jan 2024 15:42:00 -0000 https://status.logto.io/incident/311523#b46c8ae3ccdee83bb7d55a36f8f28a23d17a1770a2f53fcf50dcee5caf7c4cd0 Logto services may return 502 bad gateway error for some users. We are taking a look on it. https://status.logto.io/incident/301545 Sun, 17 Dec 2023 10:50:00 -0000 https://status.logto.io/incident/301545#b625661b4ba46ec9b2065a6343bd3aa721407eb96c0be07ad3e601e62c657c38 Postmortem is available [here](https://blog.logto.io/postmortem-docker-image-not-found/). https://status.logto.io/incident/301545 Sun, 17 Dec 2023 04:14:00 -0000 https://status.logto.io/incident/301545#d8ba48626bd4c6191b602d966ad46222646b821e5f9d9b84635355d432ab45bc The incident has been resolved. We are delving into the details and working on protocols to ensure that a similar case will not happen again. A post-mortem will be published later. https://status.logto.io/incident/301545 Sun, 17 Dec 2023 04:09:00 -0000 https://status.logto.io/incident/301545#7bf3af41d5d831d620119ebe55414d2da29ed84634526850cc10a0819f359395 We acknowledged this incident and we are working on the fix.