Datacake - Notice history

GraphQL API - Operational

100% - uptime
Nov 2025 · 100.0%Dec · 99.96%Jan 2026 · 100.0%
Nov 2025
Dec 2025
Jan 2026

Web Application - Operational

100% - uptime
Nov 2025 · 100.0%Dec · 100.0%Jan 2026 · 100.0%
Nov 2025
Dec 2025
Jan 2026

MQTT Server - Operational

100% - uptime
Nov 2025 · 100.0%Dec · 100.0%Jan 2026 · 100.0%
Nov 2025
Dec 2025
Jan 2026

White Label - Operational

100% - uptime
Nov 2025 · 100.0%Dec · 100.0%Jan 2026 · 100.0%
Nov 2025
Dec 2025
Jan 2026

Reports - Operational

100% - uptime
Nov 2025 · 100.0%Dec · 100.0%Jan 2026 · 100.0%
Nov 2025
Dec 2025
Jan 2026

Outgoing Webhooks - Operational

100% - uptime
Nov 2025 · 100.0%Dec · 100.0%Jan 2026 · 100.0%
Nov 2025
Dec 2025
Jan 2026

Notice history

Jan 2026

No notices reported this month

Dec 2025

Performance degradation
  • Postmortem
    Postmortem

    On December 8, several of our services experienced a brief period of instability due to an issue originating from our database provider. The incident began at 11:42 UTC and services recovered by 11:51 UTC.

    What happened
    Our vendor identified the root cause as a failure in their backend node replacement service. This failure caused delays in deploying new nodes, which led to performance issues and affected tasks related to DNS updates, including node replacements.
    The impact was limited to databases whose nodes had recently been replaced or newly created, for example after forking or scheduled maintenance.

    Resolution
    The vendor has identified and fixed the underlying issue in their node replacement service. Once the affected database recovered, all Datacake services returned to normal operation and have remained stable since.

    Next steps
    We are continuing to work with the vendor to ensure the issue is fully understood and that safeguards are in place to prevent a recurrence.

  • Resolved
    Resolved

    All systems continue to be stable, so we are marking this incident as resolved. Our database vendor has acknowledged the issue as originating on their end and is continuing to investigate the root cause.

  • Monitoring
    Monitoring

    We’ve identified the root cause as an issue with one of our database providers. The affected database has recovered, and all services are fully back online.

    While we continue to monitor the situation, we’re working closely with the vendor to understand what happened and to prevent future occurrences. We excuse any inconvenience caused and appreciate your patience.

  • Investigating
    Investigating

    We are investigating increased latencies with the API.

Nov 2025 to Jan 2026

Next