Speechmatics reported "RT SaaS USA - SSL connection errors" on its status page at 2026-09-10 20:33 UTC.

Speechmatics lists these components: Realtime SaaS - US.

When did the incident start and end?

It started at 2026-09-10 20:33 UTC and ended at 2026-09-10 22:37 UTC. It lasted 2 h 4 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-10 20:33 UTC

RT SaaS USA - SSL connection errors

ResolvedOfficial update

This incident has been resolved.

The latest update from Speechmatics.

State

Resolved

Started

52 d ago

2026-09-10 20:33 UTC

Lasted

2 h 4 min

until 2026-09-10 22:37 UTC

Worst impact

Partial outage

Timeline

4 updates

20:3321:0421:3522:0622:37

Partial outageUpdate postedTimes in UTC

Identified

1 h 44 min 84%

Monitoring

20 min 16%

Updates

Times in UTC

As posted by Speechmatics

Resolved2026-09-10 22:37 UTC

This incident has been resolved.

Monitoring2026-09-10 22:17 UTC

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

Identified2026-09-10 21:33 UTC

We are currently rolling out a fix and expected to complete in less than 30 minutes.

Identified2026-09-10 20:33 UTC

We have identified an issue affecting a subset of customers attempting to open RT sessions, resulting in secure connection (SSL/TLS) errors. Our team is actively working on a fix and we will provide a further update as soon as it is deployed.

Affected components

Realtime SaaS - US

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

1.5× 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 - Users experiencing 4003 errors

This incident has been resolved.

Resolvedresolved 58 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