Incidents reported on status page for Datasaur https://status.datasaur.ai/ https://d1lppblt9t2x15.cloudfront.net/logos/a05c13a5e40f53007e2263940feb405b.png https://status.datasaur.ai/ en https://status.datasaur.ai/ Wed, 13 Aug 2025 03:24:30 +0000 https://status.datasaur.ai/#2336e312e8942da7c6d4e54c787d1383f7a7f064152028d6aad060d29e978ee9 App Backend recovered https://status.datasaur.ai/ Wed, 13 Aug 2025 03:15:44 +0000 https://status.datasaur.ai/#2336e312e8942da7c6d4e54c787d1383f7a7f064152028d6aad060d29e978ee9 App Backend went down https://status.datasaur.ai/ Thu, 07 Aug 2025 20:48:24 +0000 https://status.datasaur.ai/#9915dc960bf5190fc472abc4d5b06d2829c54fc43dfb12c874b28d86a26fd997 App Backend recovered https://status.datasaur.ai/ Thu, 07 Aug 2025 20:42:26 +0000 https://status.datasaur.ai/#9915dc960bf5190fc472abc4d5b06d2829c54fc43dfb12c874b28d86a26fd997 App Backend went down https://status.datasaur.ai/ Fri, 18 Jul 2025 16:43:03 +0000 https://status.datasaur.ai/#b2dd21a3d778824d9874a7570dfd8f3a2b0b0b0fabdad8a1b6b8d3e0cee44859 App Backend recovered https://status.datasaur.ai/ Fri, 18 Jul 2025 16:37:21 +0000 https://status.datasaur.ai/#b2dd21a3d778824d9874a7570dfd8f3a2b0b0b0fabdad8a1b6b8d3e0cee44859 App Backend went down https://status.datasaur.ai/ Wed, 02 Jul 2025 06:02:46 +0000 https://status.datasaur.ai/#51b4920f8dbf01bd86491863d358e21605a0abd276e81ab0b52fabe5464dad72 App Backend recovered https://status.datasaur.ai/ Wed, 02 Jul 2025 05:56:53 +0000 https://status.datasaur.ai/#51b4920f8dbf01bd86491863d358e21605a0abd276e81ab0b52fabe5464dad72 App Backend went down https://status.datasaur.ai/ Tue, 01 Jul 2025 12:47:16 +0000 https://status.datasaur.ai/#0df62556f47276e15a4219dcff562216567a272d60ec6cd0df07cedb42360bd6 App Backend recovered https://status.datasaur.ai/ Tue, 01 Jul 2025 12:26:13 +0000 https://status.datasaur.ai/#0df62556f47276e15a4219dcff562216567a272d60ec6cd0df07cedb42360bd6 App Backend went down https://status.datasaur.ai/ Sat, 28 Jun 2025 00:48:35 +0000 https://status.datasaur.ai/#c74de6849a37b3bcbd77a67bd8f1d5101801f664d7ae27d5a0835383c97b2d67 App Backend recovered https://status.datasaur.ai/ Sat, 28 Jun 2025 00:45:53 +0000 https://status.datasaur.ai/#c74de6849a37b3bcbd77a67bd8f1d5101801f664d7ae27d5a0835383c97b2d67 App Backend went down https://status.datasaur.ai/ Wed, 18 Jun 2025 00:01:29 +0000 https://status.datasaur.ai/#9628ca296797e8904a859d061262cd42ddf1e409205d91760bbe6b8ebc84ff99 App Backend recovered https://status.datasaur.ai/ Tue, 17 Jun 2025 23:52:47 +0000 https://status.datasaur.ai/#9628ca296797e8904a859d061262cd42ddf1e409205d91760bbe6b8ebc84ff99 App Backend went down https://status.datasaur.ai/ Tue, 17 Jun 2025 23:37:30 +0000 https://status.datasaur.ai/#006b6f4e848f024f3ac9cb6dbf09cbd56b2aaff2389d46cb437005080836f623 App Backend recovered https://status.datasaur.ai/ Tue, 17 Jun 2025 23:28:56 +0000 https://status.datasaur.ai/#006b6f4e848f024f3ac9cb6dbf09cbd56b2aaff2389d46cb437005080836f623 App Backend went down https://status.datasaur.ai/ Fri, 13 Jun 2025 18:13:57 +0000 https://status.datasaur.ai/#8f5ae537cd6cabbe23d6e010f8a394995185e13ac168fe7a5a74f1aef74f7498 App Backend recovered https://status.datasaur.ai/ Fri, 13 Jun 2025 18:08:10 +0000 https://status.datasaur.ai/#8f5ae537cd6cabbe23d6e010f8a394995185e13ac168fe7a5a74f1aef74f7498 App Backend went down https://status.datasaur.ai/ Wed, 21 May 2025 17:40:26 +0000 https://status.datasaur.ai/#70b902e77f31a1af511bbad5646970fdab8ec606c15ec8465ebb9c4f43328fa2 App Backend recovered https://status.datasaur.ai/ Wed, 21 May 2025 17:28:46 +0000 https://status.datasaur.ai/#70b902e77f31a1af511bbad5646970fdab8ec606c15ec8465ebb9c4f43328fa2 App Backend went down https://status.datasaur.ai/ Fri, 16 May 2025 01:25:27 +0000 https://status.datasaur.ai/#aa00a00b522deade356ea503977d55843d70675231f21eec1ef54e28c8f6b1d0 App Backend recovered https://status.datasaur.ai/ Fri, 16 May 2025 01:22:35 +0000 https://status.datasaur.ai/#aa00a00b522deade356ea503977d55843d70675231f21eec1ef54e28c8f6b1d0 App Backend went down https://status.datasaur.ai/ Thu, 08 May 2025 18:36:48 +0000 https://status.datasaur.ai/#3e40da234a9e3bd5f0944d0ad1342328fe9de4d84418d324a8542b47d4518848 App Backend recovered https://status.datasaur.ai/ Thu, 08 May 2025 18:33:53 +0000 https://status.datasaur.ai/#3e40da234a9e3bd5f0944d0ad1342328fe9de4d84418d324a8542b47d4518848 App Backend went down https://status.datasaur.ai/ Thu, 20 Mar 2025 03:18:20 +0000 https://status.datasaur.ai/#6f6bd16fe2c6a456189622a0b39c2a13ecbb48e0a31426fc4a703e0aa4cfd66e App Backend recovered https://status.datasaur.ai/ Thu, 20 Mar 2025 03:01:06 +0000 https://status.datasaur.ai/#6f6bd16fe2c6a456189622a0b39c2a13ecbb48e0a31426fc4a703e0aa4cfd66e App Backend went down https://status.datasaur.ai/ Wed, 19 Mar 2025 16:16:06 +0000 https://status.datasaur.ai/#5cd30893ec4e8695a3237c2786896b18b249d221cf5582f60ea8c1d26597aae4 App Backend recovered https://status.datasaur.ai/ Wed, 19 Mar 2025 16:03:47 +0000 https://status.datasaur.ai/#5cd30893ec4e8695a3237c2786896b18b249d221cf5582f60ea8c1d26597aae4 App Backend went down https://status.datasaur.ai/incident/452537 Tue, 29 Oct 2024 11:06:00 -0000 https://status.datasaur.ai/incident/452537#1ffd122bc3e3899100097903aa4356e8b64195d46c6a499caf7710af76cf20d0 The app backend health check was down due to a series of 503 and 502 errors, indicating temporary unavailability of the service. The issue affected multiple regions including Australia, North America, and Asia. After approximately 18 minutes, the monitors recovered automatically across all regions, and the incident was resolved without further escalations. We experienced a failed regular rolling app deployments, especially on our queue system, caused by a missing secret key and an accidental service restart. We have restored the secret key and the queue service. https://status.datasaur.ai/incident/334084 Fri, 01 Mar 2024 05:02:00 -0000 https://status.datasaur.ai/incident/334084#75a23a8f9880f5253fba3cdb6ae890bd5285332a068db030e785d253303dce81 On February 29, 2024, from 20:35-20:43 PT, Datasaur’s backend was unavailable and consequently logged out all users. We investigated and resolved the issue and the service is now operational. We apologize for any inconvenience caused.