Incidents reported on status page for Datalab https://status.datalab.to/ https://d1lppblt9t2x15.cloudfront.net/logos/4030dcd6b07f74bfb8d1de626fb0fadd.png https://status.datalab.to/ en https://status.datalab.to/incident/846366 Tue, 10 Mar 2026 22:11:00 -0000 https://status.datalab.to/incident/846366#24f57048e8b506a674bcb6bc7b8af89df847b7b67093b94da7229db45ab75563 Fix is out and API is back to normal and stable. https://status.datalab.to/incident/846366 Tue, 10 Mar 2026 22:03:00 -0000 https://status.datalab.to/incident/846366#8f38abe97997634c396c026f8a58f35bdbb57b38cbcaa1c536d4d9dfee07d3f3 We've identified the issue and are resolving it, thank you for your patience! https://status.datalab.to/incident/846366 Tue, 10 Mar 2026 21:53:00 -0000 https://status.datalab.to/incident/846366#b7612469a6ec3c34fa24ea9c29f57abd47b90c4973268fe2d84bf22b4f0c8a9b We are currently experiencing slightly elevated response times across our API. The root cause has been identified and our team is actively working on a resolution. API requests are still being processed successfully, but may take longer than usual to complete. We will provide updates as the situation progresses. https://status.datalab.to/incident/823451 Wed, 11 Feb 2026 18:38:00 -0000 https://status.datalab.to/incident/823451#1b2f348975c8121a3c076151fb61baea90ae714180beaceb6a3baee378bf5505 The issue has been resolved. API response times are back to normal. https://status.datalab.to/incident/823451 Wed, 11 Feb 2026 18:27:00 -0000 https://status.datalab.to/incident/823451#e0425175183770e3484c8756ed8d52488bd78636abdeb2bc713958583dd4f765 Our team has rolled out the fix and is monitoring the situation. API response times are beginning to return to normal. https://status.datalab.to/incident/823451 Wed, 11 Feb 2026 18:15:00 -0000 https://status.datalab.to/incident/823451#79271c02dab41f847009b41b08776b96143bf6d055deef70fcc900d4feb4d12d Our team has implemented a fix and is running final validations before deployment. We will begin rolling out the fix shortly https://status.datalab.to/incident/823451 Wed, 11 Feb 2026 18:00:00 -0000 https://status.datalab.to/incident/823451#37691d3272b28e21bc8f1b92cfb2d75d83d833cb487ef2e5bb180e09db5a72da We are continuing to work on resolving the internal issue causing elevated API response times. https://status.datalab.to/incident/823451 Wed, 11 Feb 2026 17:44:00 -0000 https://status.datalab.to/incident/823451#a76d2703d3810eb961b8eeaedcb895c58fd3570166be144d225a250cd2d51248 We are currently experiencing slightly elevated response times across our API. The root cause has been identified and our team is actively working on a resolution. API requests are still being processed successfully, but may take longer than usual to complete. We will provide updates as the situation progresses. https://status.datalab.to/ Fri, 06 Feb 2026 13:26:04 +0000 https://status.datalab.to/#e29d9d7fb5ec4b44d4f529d6c037b96a978866a57e738f45c42358703270ac92 Website recovered https://status.datalab.to/ Fri, 06 Feb 2026 13:25:34 +0000 https://status.datalab.to/#82dc8d7ade76c378d8897ba6ffe9ad24cc610d22a1e6950defa902d73ac12a7b Datalab API recovered https://status.datalab.to/ Fri, 06 Feb 2026 13:22:41 +0000 https://status.datalab.to/#e29d9d7fb5ec4b44d4f529d6c037b96a978866a57e738f45c42358703270ac92 Website went down https://status.datalab.to/ Fri, 06 Feb 2026 13:22:34 +0000 https://status.datalab.to/#82dc8d7ade76c378d8897ba6ffe9ad24cc610d22a1e6950defa902d73ac12a7b Datalab API went down 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. 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. 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. 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. 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. 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. https://status.datalab.to/incident/533756 Mon, 24 Mar 2025 21:46:00 -0000 https://status.datalab.to/incident/533756#57d86b1900428ff75ee74ad4e544cd16670c1dfc66513fc482912af72f444da2 Incident resolved. 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. 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. 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.