Incidents reported on status page for Clerk.io https://status.clerk.io/ https://d1lppblt9t2x15.cloudfront.net/logos/624b434589872a01643163827954e073.png https://status.clerk.io/ en https://status.clerk.io/ Fri, 30 May 2025 00:11:27 +0000 https://status.clerk.io/#34937c53bf90155f8625f8584375b7ac49e68a03533373f7aa50855e37d781d5 docs.clerk.io recovered https://status.clerk.io/ Fri, 30 May 2025 00:07:22 +0000 https://status.clerk.io/#34937c53bf90155f8625f8584375b7ac49e68a03533373f7aa50855e37d781d5 docs.clerk.io went down https://status.clerk.io/ Mon, 19 May 2025 09:44:22 +0000 https://status.clerk.io/#ac76dc0308d95669a47af24f66efda08016d8e7b1e5cea12423d5461f6cb734a api.clerk.io recovered https://status.clerk.io/ Mon, 19 May 2025 09:43:54 +0000 https://status.clerk.io/#ac76dc0308d95669a47af24f66efda08016d8e7b1e5cea12423d5461f6cb734a api.clerk.io went down https://status.clerk.io/ Mon, 19 May 2025 08:08:16 +0000 https://status.clerk.io/#dec993c754fe6eab1b96ae6dfbb1afb31f9d4a8cfe3eb1585da7d63b7fd94c61 api.clerk.io recovered https://status.clerk.io/ Mon, 19 May 2025 08:07:45 +0000 https://status.clerk.io/#dec993c754fe6eab1b96ae6dfbb1afb31f9d4a8cfe3eb1585da7d63b7fd94c61 api.clerk.io went down https://status.clerk.io/ Mon, 19 May 2025 06:42:43 +0000 https://status.clerk.io/#579cbbe6222fda6dc063717454017cd62df000a08e84b45e2faf3f7d4c71d456 api.clerk.io recovered https://status.clerk.io/ Mon, 19 May 2025 06:40:44 +0000 https://status.clerk.io/#579cbbe6222fda6dc063717454017cd62df000a08e84b45e2faf3f7d4c71d456 api.clerk.io went down https://status.clerk.io/ Thu, 15 May 2025 10:12:43 +0000 https://status.clerk.io/#d5555babd6b8e093c7e8f681f8d9af9f8d907254497bff86de2f6b4d342e862e api.clerk.io recovered https://status.clerk.io/ Thu, 15 May 2025 10:10:43 +0000 https://status.clerk.io/#d5555babd6b8e093c7e8f681f8d9af9f8d907254497bff86de2f6b4d342e862e api.clerk.io went down https://status.clerk.io/ Thu, 15 May 2025 07:53:59 +0000 https://status.clerk.io/#bbb9ee820bf0fc6c77ec8dbecfdc928efa02608ae207d3160b76dd79be3d4d48 api.clerk.io recovered https://status.clerk.io/ Thu, 15 May 2025 07:53:27 +0000 https://status.clerk.io/#bbb9ee820bf0fc6c77ec8dbecfdc928efa02608ae207d3160b76dd79be3d4d48 api.clerk.io went down https://status.clerk.io/ Thu, 15 May 2025 07:41:27 +0000 https://status.clerk.io/#3e898a55ace9016bd92a665a53282824f05851d5bbf8e7fd3db6c608235e1bd5 api.clerk.io recovered https://status.clerk.io/ Thu, 15 May 2025 07:41:00 +0000 https://status.clerk.io/#3e898a55ace9016bd92a665a53282824f05851d5bbf8e7fd3db6c608235e1bd5 api.clerk.io went down https://status.clerk.io/incident/530142 Fri, 04 Apr 2025 01:00:00 +0000 https://status.clerk.io/incident/530142#493f987009e0deea2450d621cc8d0df0021aa83930c990735da8904836113b45 Maintenance completed https://status.clerk.io/incident/530142 Fri, 04 Apr 2025 01:00:00 +0000 https://status.clerk.io/incident/530142#493f987009e0deea2450d621cc8d0df0021aa83930c990735da8904836113b45 Maintenance completed https://status.clerk.io/incident/530142 Fri, 04 Apr 2025 01:00:00 +0000 https://status.clerk.io/incident/530142#493f987009e0deea2450d621cc8d0df0021aa83930c990735da8904836113b45 Maintenance completed https://status.clerk.io/incident/530142 Fri, 04 Apr 2025 01:00:00 +0000 https://status.clerk.io/incident/530142#493f987009e0deea2450d621cc8d0df0021aa83930c990735da8904836113b45 Maintenance completed https://status.clerk.io/incident/530142 Fri, 04 Apr 2025 01:00:00 +0000 https://status.clerk.io/incident/530142#493f987009e0deea2450d621cc8d0df0021aa83930c990735da8904836113b45 Maintenance completed https://status.clerk.io/incident/530142 Fri, 04 Apr 2025 01:00:00 +0000 https://status.clerk.io/incident/530142#493f987009e0deea2450d621cc8d0df0021aa83930c990735da8904836113b45 Maintenance completed https://status.clerk.io/incident/530142 Fri, 04 Apr 2025 01:00:00 +0000 https://status.clerk.io/incident/530142#493f987009e0deea2450d621cc8d0df0021aa83930c990735da8904836113b45 Maintenance completed https://status.clerk.io/incident/530142 Fri, 04 Apr 2025 01:00:00 +0000 https://status.clerk.io/incident/530142#493f987009e0deea2450d621cc8d0df0021aa83930c990735da8904836113b45 Maintenance completed https://status.clerk.io/incident/530142 Thu, 03 Apr 2025 23:00:00 -0000 https://status.clerk.io/incident/530142#c21ddbb7030ab889d52334810a4c6fc003690d55b539f5dc2bd5a3156a1d38a0 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530142 Thu, 03 Apr 2025 23:00:00 -0000 https://status.clerk.io/incident/530142#c21ddbb7030ab889d52334810a4c6fc003690d55b539f5dc2bd5a3156a1d38a0 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530142 Thu, 03 Apr 2025 23:00:00 -0000 https://status.clerk.io/incident/530142#c21ddbb7030ab889d52334810a4c6fc003690d55b539f5dc2bd5a3156a1d38a0 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530142 Thu, 03 Apr 2025 23:00:00 -0000 https://status.clerk.io/incident/530142#c21ddbb7030ab889d52334810a4c6fc003690d55b539f5dc2bd5a3156a1d38a0 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530142 Thu, 03 Apr 2025 23:00:00 -0000 https://status.clerk.io/incident/530142#c21ddbb7030ab889d52334810a4c6fc003690d55b539f5dc2bd5a3156a1d38a0 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530142 Thu, 03 Apr 2025 23:00:00 -0000 https://status.clerk.io/incident/530142#c21ddbb7030ab889d52334810a4c6fc003690d55b539f5dc2bd5a3156a1d38a0 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530142 Thu, 03 Apr 2025 23:00:00 -0000 https://status.clerk.io/incident/530142#c21ddbb7030ab889d52334810a4c6fc003690d55b539f5dc2bd5a3156a1d38a0 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530142 Thu, 03 Apr 2025 23:00:00 -0000 https://status.clerk.io/incident/530142#c21ddbb7030ab889d52334810a4c6fc003690d55b539f5dc2bd5a3156a1d38a0 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/ Thu, 03 Apr 2025 14:28:25 +0000 https://status.clerk.io/#327131fbe0fa7a081e6db9ee7e4eb4491db555210618d16733db14eaa3bc81d7 api.clerk.io recovered https://status.clerk.io/ Thu, 03 Apr 2025 14:27:55 +0000 https://status.clerk.io/#327131fbe0fa7a081e6db9ee7e4eb4491db555210618d16733db14eaa3bc81d7 api.clerk.io went down https://status.clerk.io/incident/530140 Thu, 03 Apr 2025 01:00:59 +0000 https://status.clerk.io/incident/530140#75c36836b400044fcbe27ee9b1f4e3acdcd8e3c5c94317dba7e74067c8540b43 Maintenance completed https://status.clerk.io/incident/530140 Thu, 03 Apr 2025 01:00:59 +0000 https://status.clerk.io/incident/530140#75c36836b400044fcbe27ee9b1f4e3acdcd8e3c5c94317dba7e74067c8540b43 Maintenance completed https://status.clerk.io/incident/530140 Thu, 03 Apr 2025 01:00:59 +0000 https://status.clerk.io/incident/530140#75c36836b400044fcbe27ee9b1f4e3acdcd8e3c5c94317dba7e74067c8540b43 Maintenance completed https://status.clerk.io/incident/530140 Thu, 03 Apr 2025 01:00:59 +0000 https://status.clerk.io/incident/530140#75c36836b400044fcbe27ee9b1f4e3acdcd8e3c5c94317dba7e74067c8540b43 Maintenance completed https://status.clerk.io/incident/530140 Thu, 03 Apr 2025 01:00:59 +0000 https://status.clerk.io/incident/530140#75c36836b400044fcbe27ee9b1f4e3acdcd8e3c5c94317dba7e74067c8540b43 Maintenance completed https://status.clerk.io/incident/530140 Thu, 03 Apr 2025 01:00:59 +0000 https://status.clerk.io/incident/530140#75c36836b400044fcbe27ee9b1f4e3acdcd8e3c5c94317dba7e74067c8540b43 Maintenance completed https://status.clerk.io/incident/530140 Thu, 03 Apr 2025 01:00:59 +0000 https://status.clerk.io/incident/530140#75c36836b400044fcbe27ee9b1f4e3acdcd8e3c5c94317dba7e74067c8540b43 Maintenance completed https://status.clerk.io/incident/530140 Thu, 03 Apr 2025 01:00:59 +0000 https://status.clerk.io/incident/530140#75c36836b400044fcbe27ee9b1f4e3acdcd8e3c5c94317dba7e74067c8540b43 Maintenance completed https://status.clerk.io/incident/530140 Wed, 02 Apr 2025 23:00:59 -0000 https://status.clerk.io/incident/530140#4e85c322c9a5b2ae6275696a8b9b319e78bd218ca0ba405c6bd629c4e2eb8f47 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530140 Wed, 02 Apr 2025 23:00:59 -0000 https://status.clerk.io/incident/530140#4e85c322c9a5b2ae6275696a8b9b319e78bd218ca0ba405c6bd629c4e2eb8f47 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530140 Wed, 02 Apr 2025 23:00:59 -0000 https://status.clerk.io/incident/530140#4e85c322c9a5b2ae6275696a8b9b319e78bd218ca0ba405c6bd629c4e2eb8f47 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530140 Wed, 02 Apr 2025 23:00:59 -0000 https://status.clerk.io/incident/530140#4e85c322c9a5b2ae6275696a8b9b319e78bd218ca0ba405c6bd629c4e2eb8f47 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530140 Wed, 02 Apr 2025 23:00:59 -0000 https://status.clerk.io/incident/530140#4e85c322c9a5b2ae6275696a8b9b319e78bd218ca0ba405c6bd629c4e2eb8f47 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530140 Wed, 02 Apr 2025 23:00:59 -0000 https://status.clerk.io/incident/530140#4e85c322c9a5b2ae6275696a8b9b319e78bd218ca0ba405c6bd629c4e2eb8f47 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530140 Wed, 02 Apr 2025 23:00:59 -0000 https://status.clerk.io/incident/530140#4e85c322c9a5b2ae6275696a8b9b319e78bd218ca0ba405c6bd629c4e2eb8f47 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530140 Wed, 02 Apr 2025 23:00:59 -0000 https://status.clerk.io/incident/530140#4e85c322c9a5b2ae6275696a8b9b319e78bd218ca0ba405c6bd629c4e2eb8f47 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530137 Wed, 02 Apr 2025 01:00:16 +0000 https://status.clerk.io/incident/530137#f90902111df8f7d6f350fd073f53ebe8784275461de4839b51d70a855076e2cf Maintenance completed https://status.clerk.io/incident/530137 Wed, 02 Apr 2025 01:00:16 +0000 https://status.clerk.io/incident/530137#f90902111df8f7d6f350fd073f53ebe8784275461de4839b51d70a855076e2cf Maintenance completed https://status.clerk.io/incident/530137 Wed, 02 Apr 2025 01:00:16 +0000 https://status.clerk.io/incident/530137#f90902111df8f7d6f350fd073f53ebe8784275461de4839b51d70a855076e2cf Maintenance completed https://status.clerk.io/incident/530137 Wed, 02 Apr 2025 01:00:16 +0000 https://status.clerk.io/incident/530137#f90902111df8f7d6f350fd073f53ebe8784275461de4839b51d70a855076e2cf Maintenance completed https://status.clerk.io/incident/530137 Wed, 02 Apr 2025 01:00:16 +0000 https://status.clerk.io/incident/530137#f90902111df8f7d6f350fd073f53ebe8784275461de4839b51d70a855076e2cf Maintenance completed https://status.clerk.io/incident/530137 Wed, 02 Apr 2025 01:00:16 +0000 https://status.clerk.io/incident/530137#f90902111df8f7d6f350fd073f53ebe8784275461de4839b51d70a855076e2cf Maintenance completed https://status.clerk.io/incident/530137 Wed, 02 Apr 2025 01:00:16 +0000 https://status.clerk.io/incident/530137#f90902111df8f7d6f350fd073f53ebe8784275461de4839b51d70a855076e2cf Maintenance completed https://status.clerk.io/incident/530137 Wed, 02 Apr 2025 01:00:16 +0000 https://status.clerk.io/incident/530137#f90902111df8f7d6f350fd073f53ebe8784275461de4839b51d70a855076e2cf Maintenance completed https://status.clerk.io/incident/530137 Tue, 01 Apr 2025 23:00:16 -0000 https://status.clerk.io/incident/530137#8587063575e318c3a8ca0d5cf9289bdfdefa9df1d42ff7204d6e65cd580488a2 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530137 Tue, 01 Apr 2025 23:00:16 -0000 https://status.clerk.io/incident/530137#8587063575e318c3a8ca0d5cf9289bdfdefa9df1d42ff7204d6e65cd580488a2 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530137 Tue, 01 Apr 2025 23:00:16 -0000 https://status.clerk.io/incident/530137#8587063575e318c3a8ca0d5cf9289bdfdefa9df1d42ff7204d6e65cd580488a2 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530137 Tue, 01 Apr 2025 23:00:16 -0000 https://status.clerk.io/incident/530137#8587063575e318c3a8ca0d5cf9289bdfdefa9df1d42ff7204d6e65cd580488a2 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530137 Tue, 01 Apr 2025 23:00:16 -0000 https://status.clerk.io/incident/530137#8587063575e318c3a8ca0d5cf9289bdfdefa9df1d42ff7204d6e65cd580488a2 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530137 Tue, 01 Apr 2025 23:00:16 -0000 https://status.clerk.io/incident/530137#8587063575e318c3a8ca0d5cf9289bdfdefa9df1d42ff7204d6e65cd580488a2 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530137 Tue, 01 Apr 2025 23:00:16 -0000 https://status.clerk.io/incident/530137#8587063575e318c3a8ca0d5cf9289bdfdefa9df1d42ff7204d6e65cd580488a2 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/incident/530137 Tue, 01 Apr 2025 23:00:16 -0000 https://status.clerk.io/incident/530137#8587063575e318c3a8ca0d5cf9289bdfdefa9df1d42ff7204d6e65cd580488a2 Our services will be partially unavailable for around 10 minutes while we upgrade our database infrastructure. We apologize for the inconvenience. We do these upgrades to keep up the best possible experience for you and your customers. https://status.clerk.io/ Wed, 26 Mar 2025 12:03:49 +0000 https://status.clerk.io/#9f089ed324bd5c18efe5b9e8f99d435ac99732a905fb124a3a3560f24688e433 docs.clerk.io recovered https://status.clerk.io/ Wed, 26 Mar 2025 11:59:46 +0000 https://status.clerk.io/#9f089ed324bd5c18efe5b9e8f99d435ac99732a905fb124a3a3560f24688e433 docs.clerk.io went down https://status.clerk.io/ Tue, 18 Mar 2025 03:28:56 +0000 https://status.clerk.io/#8fd9a6b4fbaf3fd7907832e1c412cc434b1f53157987b7a44749f374e5c23ea3 docs.clerk.io recovered https://status.clerk.io/ Tue, 18 Mar 2025 03:27:42 +0000 https://status.clerk.io/#8fd9a6b4fbaf3fd7907832e1c412cc434b1f53157987b7a44749f374e5c23ea3 docs.clerk.io went down https://status.clerk.io/ Wed, 05 Mar 2025 00:25:52 +0000 https://status.clerk.io/#125cdb55744c04a122ffc429e1c3a794b6fb502527f480dc7dd034721179b3ab docs.clerk.io recovered https://status.clerk.io/ Wed, 05 Mar 2025 00:20:34 +0000 https://status.clerk.io/#125cdb55744c04a122ffc429e1c3a794b6fb502527f480dc7dd034721179b3ab docs.clerk.io went down https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:45:00 -0000 https://status.clerk.io/incident/474789#089f99b6308ad8b1793cc1843095d52b34a58d9f81aaf5aac6a65036c9fa8dc1 Recap: At around 15:03 CET one of our database servers began timing out on new connections, leading to API requests for stores on that particular database to experience long wait times which led to system instability. The devops team was notified by automatic monitoring and by 15:10 CET all affected stores had been put into maintenance mode, stabilizing the API operations for all other customers. The issue was diagnosed as a bug in our database software, and the affected machine was patched and re-validated before being put back into production. By 15:21 CET the first batch of stores was pulled from maintenance mode and put back into full production under monitoring. By 15:32 CET the final store was back to full production. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:45:00 -0000 https://status.clerk.io/incident/474789#089f99b6308ad8b1793cc1843095d52b34a58d9f81aaf5aac6a65036c9fa8dc1 Recap: At around 15:03 CET one of our database servers began timing out on new connections, leading to API requests for stores on that particular database to experience long wait times which led to system instability. The devops team was notified by automatic monitoring and by 15:10 CET all affected stores had been put into maintenance mode, stabilizing the API operations for all other customers. The issue was diagnosed as a bug in our database software, and the affected machine was patched and re-validated before being put back into production. By 15:21 CET the first batch of stores was pulled from maintenance mode and put back into full production under monitoring. By 15:32 CET the final store was back to full production. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:45:00 -0000 https://status.clerk.io/incident/474789#089f99b6308ad8b1793cc1843095d52b34a58d9f81aaf5aac6a65036c9fa8dc1 Recap: At around 15:03 CET one of our database servers began timing out on new connections, leading to API requests for stores on that particular database to experience long wait times which led to system instability. The devops team was notified by automatic monitoring and by 15:10 CET all affected stores had been put into maintenance mode, stabilizing the API operations for all other customers. The issue was diagnosed as a bug in our database software, and the affected machine was patched and re-validated before being put back into production. By 15:21 CET the first batch of stores was pulled from maintenance mode and put back into full production under monitoring. By 15:32 CET the final store was back to full production. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:45:00 -0000 https://status.clerk.io/incident/474789#089f99b6308ad8b1793cc1843095d52b34a58d9f81aaf5aac6a65036c9fa8dc1 Recap: At around 15:03 CET one of our database servers began timing out on new connections, leading to API requests for stores on that particular database to experience long wait times which led to system instability. The devops team was notified by automatic monitoring and by 15:10 CET all affected stores had been put into maintenance mode, stabilizing the API operations for all other customers. The issue was diagnosed as a bug in our database software, and the affected machine was patched and re-validated before being put back into production. By 15:21 CET the first batch of stores was pulled from maintenance mode and put back into full production under monitoring. By 15:32 CET the final store was back to full production. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:45:00 -0000 https://status.clerk.io/incident/474789#089f99b6308ad8b1793cc1843095d52b34a58d9f81aaf5aac6a65036c9fa8dc1 Recap: At around 15:03 CET one of our database servers began timing out on new connections, leading to API requests for stores on that particular database to experience long wait times which led to system instability. The devops team was notified by automatic monitoring and by 15:10 CET all affected stores had been put into maintenance mode, stabilizing the API operations for all other customers. The issue was diagnosed as a bug in our database software, and the affected machine was patched and re-validated before being put back into production. By 15:21 CET the first batch of stores was pulled from maintenance mode and put back into full production under monitoring. By 15:32 CET the final store was back to full production. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:45:00 -0000 https://status.clerk.io/incident/474789#089f99b6308ad8b1793cc1843095d52b34a58d9f81aaf5aac6a65036c9fa8dc1 Recap: At around 15:03 CET one of our database servers began timing out on new connections, leading to API requests for stores on that particular database to experience long wait times which led to system instability. The devops team was notified by automatic monitoring and by 15:10 CET all affected stores had been put into maintenance mode, stabilizing the API operations for all other customers. The issue was diagnosed as a bug in our database software, and the affected machine was patched and re-validated before being put back into production. By 15:21 CET the first batch of stores was pulled from maintenance mode and put back into full production under monitoring. By 15:32 CET the final store was back to full production. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:45:00 -0000 https://status.clerk.io/incident/474789#089f99b6308ad8b1793cc1843095d52b34a58d9f81aaf5aac6a65036c9fa8dc1 Recap: At around 15:03 CET one of our database servers began timing out on new connections, leading to API requests for stores on that particular database to experience long wait times which led to system instability. The devops team was notified by automatic monitoring and by 15:10 CET all affected stores had been put into maintenance mode, stabilizing the API operations for all other customers. The issue was diagnosed as a bug in our database software, and the affected machine was patched and re-validated before being put back into production. By 15:21 CET the first batch of stores was pulled from maintenance mode and put back into full production under monitoring. By 15:32 CET the final store was back to full production. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:45:00 -0000 https://status.clerk.io/incident/474789#089f99b6308ad8b1793cc1843095d52b34a58d9f81aaf5aac6a65036c9fa8dc1 Recap: At around 15:03 CET one of our database servers began timing out on new connections, leading to API requests for stores on that particular database to experience long wait times which led to system instability. The devops team was notified by automatic monitoring and by 15:10 CET all affected stores had been put into maintenance mode, stabilizing the API operations for all other customers. The issue was diagnosed as a bug in our database software, and the affected machine was patched and re-validated before being put back into production. By 15:21 CET the first batch of stores was pulled from maintenance mode and put back into full production under monitoring. By 15:32 CET the final store was back to full production. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:39:00 -0000 https://status.clerk.io/incident/474789#6bc2e410d35a6c71c2658c8538cefc0c41f0511a0be804b638cd5e73c62b64b1 All functionality is back. The issue was an internal issue in one of our database servers, it was isolated and resolved without any data lose. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:39:00 -0000 https://status.clerk.io/incident/474789#6bc2e410d35a6c71c2658c8538cefc0c41f0511a0be804b638cd5e73c62b64b1 All functionality is back. The issue was an internal issue in one of our database servers, it was isolated and resolved without any data lose. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:39:00 -0000 https://status.clerk.io/incident/474789#6bc2e410d35a6c71c2658c8538cefc0c41f0511a0be804b638cd5e73c62b64b1 All functionality is back. The issue was an internal issue in one of our database servers, it was isolated and resolved without any data lose. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:39:00 -0000 https://status.clerk.io/incident/474789#6bc2e410d35a6c71c2658c8538cefc0c41f0511a0be804b638cd5e73c62b64b1 All functionality is back. The issue was an internal issue in one of our database servers, it was isolated and resolved without any data lose. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:39:00 -0000 https://status.clerk.io/incident/474789#6bc2e410d35a6c71c2658c8538cefc0c41f0511a0be804b638cd5e73c62b64b1 All functionality is back. The issue was an internal issue in one of our database servers, it was isolated and resolved without any data lose. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:39:00 -0000 https://status.clerk.io/incident/474789#6bc2e410d35a6c71c2658c8538cefc0c41f0511a0be804b638cd5e73c62b64b1 All functionality is back. The issue was an internal issue in one of our database servers, it was isolated and resolved without any data lose. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:39:00 -0000 https://status.clerk.io/incident/474789#6bc2e410d35a6c71c2658c8538cefc0c41f0511a0be804b638cd5e73c62b64b1 All functionality is back. The issue was an internal issue in one of our database servers, it was isolated and resolved without any data lose. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:39:00 -0000 https://status.clerk.io/incident/474789#6bc2e410d35a6c71c2658c8538cefc0c41f0511a0be804b638cd5e73c62b64b1 All functionality is back. The issue was an internal issue in one of our database servers, it was isolated and resolved without any data lose. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:10:00 -0000 https://status.clerk.io/incident/474789#1514cef25731b429fa0b63c00f16edc904615fe9cd8648c0ab34f407c5814600 We are currently experiencing issues with our datastore zone 2. This is now only effecting customers in datastore zone 2. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:10:00 -0000 https://status.clerk.io/incident/474789#1514cef25731b429fa0b63c00f16edc904615fe9cd8648c0ab34f407c5814600 We are currently experiencing issues with our datastore zone 2. This is now only effecting customers in datastore zone 2. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:10:00 -0000 https://status.clerk.io/incident/474789#1514cef25731b429fa0b63c00f16edc904615fe9cd8648c0ab34f407c5814600 We are currently experiencing issues with our datastore zone 2. This is now only effecting customers in datastore zone 2. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:10:00 -0000 https://status.clerk.io/incident/474789#1514cef25731b429fa0b63c00f16edc904615fe9cd8648c0ab34f407c5814600 We are currently experiencing issues with our datastore zone 2. This is now only effecting customers in datastore zone 2. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:10:00 -0000 https://status.clerk.io/incident/474789#1514cef25731b429fa0b63c00f16edc904615fe9cd8648c0ab34f407c5814600 We are currently experiencing issues with our datastore zone 2. This is now only effecting customers in datastore zone 2. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:10:00 -0000 https://status.clerk.io/incident/474789#1514cef25731b429fa0b63c00f16edc904615fe9cd8648c0ab34f407c5814600 We are currently experiencing issues with our datastore zone 2. This is now only effecting customers in datastore zone 2. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:10:00 -0000 https://status.clerk.io/incident/474789#1514cef25731b429fa0b63c00f16edc904615fe9cd8648c0ab34f407c5814600 We are currently experiencing issues with our datastore zone 2. This is now only effecting customers in datastore zone 2. https://status.clerk.io/incident/474789 Mon, 09 Dec 2024 14:10:00 -0000 https://status.clerk.io/incident/474789#1514cef25731b429fa0b63c00f16edc904615fe9cd8648c0ab34f407c5814600 We are currently experiencing issues with our datastore zone 2. This is now only effecting customers in datastore zone 2.