RT SaaS USA - Session concurrency values maintenance
Scheduled maintenance: RT SaaS USA - session concurrency values When: 4th November 2026 08:00 UTC to 6th November 2026 08:00 UTC The usage value in the Info message (type: concurrent_session_usage) sent by the Realtime (RT) SaaS API may show a number lower than your true concurrency during this maintenance window. This is while we migrate the infrastructure that tracks concurrent session usage for the RT SaaS API. What this means for you: - Your quota limits and the number of concurrent sessions you can open are unchanged - Your quota headroom is unaffected, so you will not unexpectedly receive quota errors - There will be no disruption to general RT SaaS service or availability. This will only affect session concurrency values from the API. - No action is required on your end Reported usage will be accurate again after the maintenance window.
The latest update from Speechmatics.
State
Scheduled
Starts
in 2 d
2026-11-04 08:00 UTC
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Speechmatics
Scheduled maintenance: RT SaaS USA - session concurrency values When: 4th November 2026 08:00 UTC to 6th November 2026 08:00 UTC The usage value in the Info message (type: concurrent_session_usage) sent by the Realtime (RT) SaaS API may show a number lower than your true concurrency during this maintenance window. This is while we migrate the infrastructure that tracks concurrent session usage for the RT SaaS API. What this means for you: - Your quota limits and the number of concurrent sessions you can open are unchanged - Your quota headroom is unaffected, so you will not unexpectedly receive quota errors - There will be no disruption to general RT SaaS service or availability. This will only affect session concurrency values from the API. - No action is required on your end Reported usage will be accurate again after the maintenance window.
Affected components
1Speechmatics in the last 90 days
Full historyIncidents in 90 days
2
Days with an incident
2
Median duration
1 h 21 min
This incident
Not comparable
Other Speechmatics incidents
All incidentsFollow 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.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.
https://outages.cc/feed.xml?providers=speechmatics/feed subscribe https://outages.cc/feed.xml?providers=speechmaticsFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane