Speechmatics reported "RT SaaS - Users experiencing 4003 errors" on its status page at 2026-09-04 20:52 UTC.

Speechmatics lists these components: Realtime SaaS - US, Realtime SaaS - EU.

When did the incident start and end?

It started at 2026-09-04 20:52 UTC and ended at 2026-09-04 21:29 UTC. It lasted 38 min.

How do I get alerts for Speechmatics?

Subscribe to the Speechmatics live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Speechmatics. outages.live reads it every few minutes and keeps every update.

SpeechmaticsIncident · 2026-09-04 20:52 UTC

RT SaaS - Users experiencing 4003 errors

ResolvedOfficial update

This incident has been resolved.

The latest update from Speechmatics.

State

Resolved

Started

58 d ago

2026-09-04 20:52 UTC

Lasted

38 min

until 2026-09-04 21:29 UTC

Worst impact

Major outage

Timeline

4 updates

20:5221:0121:1121:2021:29

Major outageUpdate postedTimes in UTC

Investigating

2 min 6%

Identified

4 min 10%

Monitoring

32 min 84%

Updates

Times in UTC

As posted by Speechmatics

Resolved2026-09-04 21:29 UTC

This incident has been resolved.

Monitoring2026-09-04 20:58 UTC

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

Identified2026-09-04 20:54 UTC

The issue has been identified and a fix is being implemented.

Investigating2026-09-04 20:52 UTC

We’re currently experiencing a partial outage in our RT SaaS region EU and USA and the users experiencing 4003 error. Our team is currently working to restore normal performance levels. We apologise for any inconvenience.

Affected components

Realtime SaaS - USRealtime SaaS - EU

Speechmatics in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 21 min

This incident

53% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

2 h 4 min

median 1 h 21 min

90 days agoToday

Other Speechmatics incidents

All incidents

Speechmatics·RT SaaS USA - SSL connection errors

This incident has been resolved.

Resolvedresolved 52 d ago

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.

Prompt

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.cc/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.

RSS

https://outages.cc/feed.xml?providers=speechmatics

Slack

/feed subscribe https://outages.cc/feed.xml?providers=speechmatics

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane