Incidents reported on status page for Secoda https://status.secoda.co/ https://d1lppblt9t2x15.cloudfront.net/logos/067b2266abfa5aa6d895aa09480e4235.png https://status.secoda.co/ en https://status.secoda.co/ Tue, 26 Aug 2025 16:32:48 +0000 https://status.secoda.co/#b5e51c3b043b9e9fd69ca353b53970fb40aec11a1197131e2b3e8b2c1e125e2c Secoda AI went down https://status.secoda.co/ Tue, 19 Aug 2025 04:28:21 +0000 https://status.secoda.co/#e52592f7d302f75d560d0e7a6462912820d552dcc286078812c3a0d9a21c13ff US API recovered https://status.secoda.co/ Tue, 19 Aug 2025 04:26:28 +0000 https://status.secoda.co/#e52592f7d302f75d560d0e7a6462912820d552dcc286078812c3a0d9a21c13ff US API went down https://status.secoda.co/ Thu, 31 Jul 2025 01:46:33 +0000 https://status.secoda.co/#ba81fe7c269f8a4766e1022765384cb3808c6590a9effbb9317183f5a55498c6 APAC API recovered https://status.secoda.co/ Thu, 31 Jul 2025 01:45:44 +0000 https://status.secoda.co/#1360c5598b4b7e187bc9ef12b317f629e3e051b95fd63ce353c57c6bc0fa7acf US API recovered https://status.secoda.co/ Thu, 31 Jul 2025 01:44:39 +0000 https://status.secoda.co/#ba81fe7c269f8a4766e1022765384cb3808c6590a9effbb9317183f5a55498c6 APAC API went down https://status.secoda.co/ Thu, 31 Jul 2025 01:44:13 +0000 https://status.secoda.co/#1360c5598b4b7e187bc9ef12b317f629e3e051b95fd63ce353c57c6bc0fa7acf US API went down https://status.secoda.co/ Tue, 08 Jul 2025 15:41:00 +0000 https://status.secoda.co/#27eb1a4afefe84bdf6627376c1bfdaa19c7f88ad67bba5624eaa66aa1dbe1f04 US API recovered https://status.secoda.co/ Tue, 08 Jul 2025 15:39:32 +0000 https://status.secoda.co/#27eb1a4afefe84bdf6627376c1bfdaa19c7f88ad67bba5624eaa66aa1dbe1f04 US API went down https://status.secoda.co/incident/539526 Thu, 03 Apr 2025 21:17:00 -0000 https://status.secoda.co/incident/539526#aba7ed550f6089cc04cab76edfb5d4fd449d06e3380562b431481f9d6209aeef We've successfully reverted the problematic change and normal functionality is restored. https://status.secoda.co/incident/539526 Thu, 03 Apr 2025 21:17:00 -0000 https://status.secoda.co/incident/539526#aba7ed550f6089cc04cab76edfb5d4fd449d06e3380562b431481f9d6209aeef We've successfully reverted the problematic change and normal functionality is restored. https://status.secoda.co/incident/539526 Thu, 03 Apr 2025 21:17:00 -0000 https://status.secoda.co/incident/539526#aba7ed550f6089cc04cab76edfb5d4fd449d06e3380562b431481f9d6209aeef We've successfully reverted the problematic change and normal functionality is restored. https://status.secoda.co/incident/539526 Thu, 03 Apr 2025 21:02:00 -0000 https://status.secoda.co/incident/539526#0ad55c85cfd38516804eb0fb190e1819ffff265e07c9902abbc3cce34820c963 Users are unable to access Secoda at the moment. Our team is actively investigating and working on a fix. We'll provide updates as soon as we have more information. https://status.secoda.co/incident/539526 Thu, 03 Apr 2025 21:02:00 -0000 https://status.secoda.co/incident/539526#0ad55c85cfd38516804eb0fb190e1819ffff265e07c9902abbc3cce34820c963 Users are unable to access Secoda at the moment. Our team is actively investigating and working on a fix. We'll provide updates as soon as we have more information. https://status.secoda.co/incident/539526 Thu, 03 Apr 2025 21:02:00 -0000 https://status.secoda.co/incident/539526#0ad55c85cfd38516804eb0fb190e1819ffff265e07c9902abbc3cce34820c963 Users are unable to access Secoda at the moment. Our team is actively investigating and working on a fix. We'll provide updates as soon as we have more information.