Incidents | Datalab Incidents reported on status page for Datalab https://status.datalab.to/ https://d1lppblt9t2x15.cloudfront.net/logos/4030dcd6b07f74bfb8d1de626fb0fadd.png Incidents | Datalab https://status.datalab.to/ en Website recovered https://status.datalab.to/ Fri, 05 Dec 2025 09:12:13 +0000 https://status.datalab.to/#6fca1922d279f5bf7f5377531ee617eb323b7d5d4fcef4923fe99a0bff588be7 Website recovered Datalab API recovered https://status.datalab.to/ Fri, 05 Dec 2025 09:11:58 +0000 https://status.datalab.to/#ce2a12869e7483591495c0bd128bd0d818593e5aa983be41e6b1d7463e61c704 Datalab API recovered Website went down https://status.datalab.to/ Fri, 05 Dec 2025 08:52:52 +0000 https://status.datalab.to/#6fca1922d279f5bf7f5377531ee617eb323b7d5d4fcef4923fe99a0bff588be7 Website went down Datalab API went down https://status.datalab.to/ Fri, 05 Dec 2025 08:52:26 +0000 https://status.datalab.to/#ce2a12869e7483591495c0bd128bd0d818593e5aa983be41e6b1d7463e61c704 Datalab API went down Intermittent 404 https://status.datalab.to/incident/758743 Wed, 05 Nov 2025 20:53:00 -0000 https://status.datalab.to/incident/758743#0e7204740ce80e28ef7bade168463766786715c4b7dc983732c724e47e00806a Intermittent 404s have been resolved. Intermittent 404 https://status.datalab.to/incident/758743 Wed, 05 Nov 2025 20:30:00 -0000 https://status.datalab.to/incident/758743#76b5d4dc2d477b0d5539efc08a2ba80217f04f67b597ca4beebc1023e6d8bde3 We had an issue with an upstream provider that resulted in intermittent 404 errors. API Degradation Due To Ongoing AWS Incident https://status.datalab.to/incident/747490 Mon, 20 Oct 2025 18:03:00 -0000 https://status.datalab.to/incident/747490#97a82dd1dc97dd26948d72e9d9e41318b13f715e45e17637324d365b95ddc878 Datalab's API has stabilized after mitigations we have put in place. The AWS incident is ongoing. We are actively monitoring the situation in case it triggers issues with our API again. API Degradation Due To Ongoing AWS Incident https://status.datalab.to/incident/747490 Mon, 20 Oct 2025 16:00:00 -0000 https://status.datalab.to/incident/747490#2bbf41d95860b494dd33887b3ac9d200a607bfd3ab3a60cf231d2b50548cbe52 Our API is currently degraded and seeing high failure rates due to ongoing AWS issues affecting our upstream providers, Modal and Render. Today's AWS incident is ongoing: https://health.aws.amazon.com/health/status. API Downtime Due To Global AWS Outage https://status.datalab.to/incident/747435 Mon, 20 Oct 2025 09:15:00 -0000 https://status.datalab.to/incident/747435#f62046256cad0453c61892a49bf0d5345481b48394dc3854125fdffb70547022 Our systems have been stable and fully operational since AWS stabilized at 5:15 AM EDT. API Downtime Due To Global AWS Outage https://status.datalab.to/incident/747435 Mon, 20 Oct 2025 07:45:00 -0000 https://status.datalab.to/incident/747435#6e26650f2757d1427d7d3d797ea629a4c0fc442ab73212f0787e18f5910f7d2e A global AWS outage is impacting our ability to deliver parse results to customers via API. Intermittent 500 errors https://status.datalab.to/incident/533756 Mon, 24 Mar 2025 21:46:00 -0000 https://status.datalab.to/incident/533756#57d86b1900428ff75ee74ad4e544cd16670c1dfc66513fc482912af72f444da2 Incident resolved. Intermittent 500 errors https://status.datalab.to/incident/533756 Mon, 24 Mar 2025 20:28:00 -0000 https://status.datalab.to/incident/533756#a52b5d77868f4b5828c841166151db90e3bbca1c6729b44831e8637498644781 There are intermittent 500 errors when using the API, specifically when retrieving results. We're working to fix this currently. Intermittent 500 errors https://status.datalab.to/incident/403628 Thu, 25 Jul 2024 15:52:00 -0000 https://status.datalab.to/incident/403628#c3dfe8413df0c0eb85b6fa515d5bbd0b9fcdb0192cd6a10696c4f281b6d319e1 The database connectivity issue has been resolved. Intermittent 500 errors https://status.datalab.to/incident/403628 Thu, 25 Jul 2024 05:00:00 -0000 https://status.datalab.to/incident/403628#9c405267e6fe512a5c51f2c791cf83f64ed0044991097504f65fd0f637b051d4 Due to a database connectivity issue, there were intermittent 500 errors. This did not result in alarms, since it happened at a lower level of the stack. The issue has been resolved, and auto-restart and monitors have been setup.