Decoda Health - Notice history

All systems operational

Decoda servers - Operational

100.0% uptime
May 2026 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Decoda app - Operational

100.0% uptime
May 2026 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Deepgram (Scribe Dependency) - Operational

Anthropic (AI dependency) - Operational

Mailgun (Email Dependency) - Operational

Google Cloud - Kubernetes Engine - Operational

Google Cloud - Cloud SQL - Operational

Google Cloud - Cloud Storage - Operational

Google Cloud - Pub/Sub - Operational

Google Cloud - Compute Engine - Operational

Junction (Core API) - Operational

Junction (Lab Testing) - Operational

Rainforest (Payments Dependency) - Operational

100.0% uptime
May 2026 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2026
Jun 2026
Jul 2026

OpenAI (AI Dependency) - Operational

100.0% uptime
May 2026 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2026
Jun 2026
Jul 2026

SignalWire (Messaging Dependency) - Operational

100.0% uptime
May 2026 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2026
Jun 2026
Jul 2026

DoseSpot (Prescribing Dependency) - Operational

100.0% uptime
May 2026 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2026
Jun 2026
Jul 2026

PostGrid (Mail Dependency) - Operational

100.0% uptime
May 2026 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Fullscript (Labs Dependency) - Operational

100.0% uptime
May 2026 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Notice history

View current status

Jul 2026

[Deepgram API] Elevated Batch Error Rates: 400 error code responses
ResolvedDegraded performance23 hours 7 minutes
  • Resolved
    UTC
    Resolved

    This incident has been resolved.

  • Monitoring
    UTC
    Monitoring

    A fix has been implemented and traffic has returned to normal. We are monitoring the results.

  • Investigating
    UTC
    Investigating

    We are continuing to investigate an issue. STT batch requests may have returned 5xx errors, and some STT websockets may have experienced high latency, starting at 16:03 UTC.

  • Update
    UTC
    Update

    We are continuing to monitor for any further issues.

  • Monitoring
    UTC
    Monitoring

    A fix has been implemented and we are monitoring the results.

  • Update
    UTC
    Update

    We are continuing to investigate this issue.

  • Investigating
    UTC
    Investigating

    We are currently investigating an issue where some batch requests are returning 400 errors due to remote content download errors. Retrying the request one or more times often succeeds.

Jun 2026

400 errors with PreRecorded STT ("REMOTE_CONTENT_ERROR" / "failed to return valid data") when passing a URL
ResolvedDegraded performance6 hours 12 minutes
  • Resolved
    UTC
    Resolved

    The issue was resolved at 19:47 UTC.

  • Identified
    UTC
    Identified

    Between the hours of 13:35 UTC - 19:47 UTC we noticed an increase in 400 errors returned on PreRecorded STT requests where the payload was a URL. They were transient errors, retrying the request was the recommended course of action and would typically result in a successful transcription.

May 2026

No notices reported this month

Previous

May 2026 to Jul 2026

Next