Gladia - Notice history

All systems operational

API - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 99.98%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025

Pre-Recorded v2 - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 99.89%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025

Real-Time v1 - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 99.96%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025

Real-Time v2 - Operational

99% - uptime
Dec 2024 · 100.0%Jan 2025 · 98.57%Feb · 99.99%
Dec 2024
Jan 2025
Feb 2025

App - Operational

100% - uptime
Dec 2024 · 100.0%Jan 2025 · 100.0%Feb · 100.0%
Dec 2024
Jan 2025
Feb 2025

Notice history

Feb 2025

No notices reported this month

Jan 2025

API is unreachable via Recall.ai
  • Resolved
    Resolved

    Starting at around 15:30 UTC+1, all requests coming from Recall.ai began failing. The issue was traced to a specific edge case involving file uploads where a filename is not provided by the client, requiring our system to generate one. While most HTTP clients and browsers include a filename by default—making the issue rare—Recall.ai’s integration did not, triggering the problem.

    This behavior was caused by a recent change deployed at 15:00 UTC+1 to support JSON-formatted logs. As part of that change, the request ID, which is used to generate a filename in the absence of one, was no longer accessible. This resulted in 400 Bad Request errors for affected uploads.

    The issue was identified at 15:30 UTC+1. A fix was reviewed by 16:30 UTC+1 and deployed by 17:00 UTC+1, resolving the problem.

    We are updating our test coverage to include this specific edge case to prevent similar incidents in the future.

  • Monitoring
    Monitoring

    A fix has been deployed. Upload are working again. We are monitoring the situation.

  • Investigating
    Investigating

    Gladia API is currently unavailable via Recall.ai. We reached out to their team to find a solution.

Dec 2024

No notices reported this month

Dec 2024 to Feb 2025

Next