Investigating - Degraded performance in realtime SaaS - USA
Realtime SaaS - US had degraded performance. Speechmatics reports that the incident is resolved. It lasted 62 minutes.
State
Resolved
Started
Lasted
1 h 2 min
Worst impact
Degraded
Timeline
3 updatesIdentified
15 min 25%
Monitoring
47 min 75%
Updates
Times in UTCAs posted by Speechmatics
This incident has been resolved.
Monitoring: We have rolled back the change affecting real-time transcription in our US region. New sessions are now being served by the previous version, and we are monitoring as existing sessions complete. We will provide a further update within 30 minutes.
We have identified an issue causing degraded performance for real-time transcription sessions in our US region. We are applying a mitigation now and will provide an update within 30 minutes.
Affected components
1Speechmatics in the last 90 days
Full historyIncidents in 90 days
4
Days with an incident
4
Median duration
1 h 31 min
This incident
32% shorter than the median
Other Speechmatics incidents
All incidents
Speechmatics·Degraded performance and errors for Batch transcription in US2
Speechmatics Batch transcription in the US2 region had degraded performance and errors. Batch SaaS US2 job submission and retrieval failed or timed out, and jobs ran slow. Speechmatics resolved the incident after 2 hours.

Speechmatics·RT SaaS USA - SSL connection errors
This incident has been resolved.

Speechmatics·RT SaaS - Users experiencing 4003 errors
This incident has been resolved.
Follow Speechmatics
Your coding agent knows when Speechmatics is down, and tells you when a failure is theirs, not yours. You can also get Speechmatics incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "speechmatics" and tell me if Speechmatics has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=speechmatics/feed subscribe https://outages.live/feed.xml?providers=speechmaticsFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane