Is Datacake down?
Last checked 4m agoNo incidents right now.
Datacake is operational right now. Last checked 4m ago; the most recent incident resolved 52d ago.
Real-time Datacake status, recent outages, and incident history — pulled directly from Datacake's official status page at https://datacake-status.com every 5 minutes. Pingoru tracks 11 Datacake services and has captured 2 incidents in the last 90 days (99.70% uptime). Get email, Slack, Discord, or webhook alerts the moment Datacake reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- GraphQL APIMQTT ServerOutgoing Webhooks
Timeline · 4 updates
- investigating · Jul 25, 2026, 09:21 AM UTC
Our system is experiencing processing delays. No data has been lost, and the system should be caught up shortly.
- identified · Jul 25, 2026, 10:35 AM UTC
We have identified the cause of the delays and implemented corrective measures. The fix has improved processing, but the existing queue backlog is still being cleared. Delays in data ingestion therefore continue at this time.
- monitoring · Jul 25, 2026, 01:11 PM UTC
We have identified and resolved the root cause of the delays. An internal metrics exporter was placing additional load on the processing queue. We have implemented optimizations and are already seeing a significant performance improvement. The remaining backlog is still being processed, and we will provide another update once the queue has fully cleared. No data has been lost.
- resolved · Jul 25, 2026, 01:51 PM UTC
The processing queue has now fully cleared, and all system metrics look healthy. No data was lost during the incident. We apologize for the inconvenience and will publish a detailed technical postmortem soon.
Latest: The processing queue has now fully cleared, and all system metrics look healthy. No data was lost during the incident. We apologize for the inconvenience and will publish a detaile…
-
-
Timeline · 1 update
- resolved · Jul 25, 2026, 09:21 AM UTC
Type: Incident Duration: 4 hours and 31 minutes Affected Components: MQTT Server, GraphQL API, Outgoing Webhooks Jul 25, 09:21:07 GMT+0 - Investigating - Our system is experiencing processing delays. No data has been lost, and the system should be caught up shortly. Jul 25, 10:35:36 GMT+0 - Identified - We have identified the cause of the delays and implemented corrective measures. The fix has improved processing, but the existing queue backlog is still being cleared. Delays in data ingestion therefore continue at this time. Jul 25, 13:11:08 GMT+0 - Monitoring - We have identified and resolved the root cause of the delays. An internal metrics exporter was placing additional load on the processing queue. We have implemented optimizations and are already seeing a significant performance improvement. The remaining backlog is still being processed, and we will provide another update once the queue has fully cleared. No data has been lost. Jul 25, 13:51:45 GMT+0 - Resolved - The processing queue has now fully cleared, and all system metrics look healthy. No data was lost during the incident. We apologize for the inconvenience and will publish a detailed technical postmortem soon.
Latest: Type: Incident Duration: 4 hours and 31 minutes Affected Components: MQTT Server, GraphQL API, Outgoing Webhooks Jul 25, 09:21:07 GMT+0 - Investigating - Our system is experiencing…
-
- Data processing delays ResolvedStarted Jul 25, 2026, 09:21 AM UTC · Resolved Jul 25, 2026, 01:51 PM UTC · 4h 30m
- Data processing delays ResolvedStarted Jul 25, 2026, 09:21 AM UTC · Resolved Jul 25, 2026, 09:21 AM UTC · —