Snapshot 287531

Document
Registry listing
URL
https://status.soniox.com/history.rss
Fetched
HTTP status
200
Content type
text/xml
Fetch mode
api
Size
16770 bytes
SHA-256 (raw)
fb0d19cd06ef9faa28e2dae845e8835b32614fbc0c9e696403e130304568064b
SHA-256 (normalized text)
b47a948c1e80858b838ac4d722d5e52afbbae550c2ff46599343c2e5287429a8

Raw (normalized text)

Scripts and page chrome removed; this is what change detection compares.

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
<title>Soniox API Status Status - Incident history</title>
<link>https://status.soniox.com</link>
<description>Soniox API Status</description>
<pubDate>Mon, 16 Nov 2026 09:22:00 +0000</pubDate>
<item>
<title>Brief disruption to real-time APIs in the EU region</title>
<description>
Type: Incident
Duration: 5 minutes
Affected Components: TTS Real-time, STT Real-time
Nov 16, 09:27:00 GMT+0 - Resolved - On November 16, 2026, between 09:22 and 09:27 UTC, a network fault at our cloud provider briefly affected real-time speech-to-text and text-to-speech in the EU region.
For under 5 minutes, some connections failed or were disconnected. Retried connections mostly succeeded, and service recovered fully at 09:27 UTC.
The async API, REST API and Console were not affected. We are working with the provider to confirm the cause and prevent a repeat. Nov 16, 09:22:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 5 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>09:27:00</var> GMT+0</small><br><strong>Resolved</strong> -
On November 16, 2026, between 09:22 and 09:27 UTC, a network fault at our cloud provider briefly affected real-time speech-to-text and text-to-speech in the EU region.
For under 5 minutes, some connections failed or were disconnected. Retried connections mostly succeeded, and service recovered fully at 09:27 UTC.
The async API, REST API and Console were not affected. We are working with the provider to confirm the cause and prevent a repeat..</p>
<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>09:22:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Mon, 16 Nov 2026 09:22:00 +0000</pubDate>
<link>https://status.soniox.com/incident/cmwj6d87k0hzl1nqzrgdr0eis</link>
<guid>https://status.soniox.com/incident/cmwj6d87k0hzl1nqzrgdr0eis</guid>
</item>
<item>
<title>Real-time STT and TTS connection errors in the US region</title>
<description>
Type: Incident
Duration: 3 minutes
Affected Components: STT Real-time, TTS Real-time
Nov 13, 08:36:00 GMT+0 - Resolved - On November 13, 2026, between 08:33 and 08:36 UTC, unexpected server failure at our cloud provider briefly affected real-time speech-to-text and text-to-speech in the US region.
For under 3 minutes, a small share of connections failed or were disconnected. Reconnecting clients were served normally.
The async API, REST API and Console were not affected. We are working with the provider to remove failed servers from service faster. Nov 13, 08:33:00 GMT+0 - Investigating - A hardware failure was detected in our infrastructure.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 3 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>08:36:00</var> GMT+0</small><br><strong>Resolved</strong> -
On November 13, 2026, between 08:33 and 08:36 UTC, unexpected server failure at our cloud provider briefly affected real-time speech-to-text and text-to-speech in the US region.
For under 3 minutes, a small share of connections failed or were disconnected. Reconnecting clients were served normally.
The async API, REST API and Console were not affected. We are working with the provider to remove failed servers from service faster..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>08:33:00</var> GMT+0</small><br><strong>Investigating</strong> -
A hardware failure was detected in our infrastructure..</p>
]]>
</content:encoded>
<pubDate>Fri, 13 Nov 2026 08:33:00 +0000</pubDate>
<link>https://status.soniox.com/incident/cmwev4uvq0gg01bmmzqyc7mfh</link>
<guid>https://status.soniox.com/incident/cmwev4uvq0gg01bmmzqyc7mfh</guid>
</item>
<item>
<title>STT Real-time overloaded in Japan region</title>
<description>
Type: Incident
Duration: 12 hours and 45 minutes
Affected Components: STT Real-time
Sep 8, 01:50:00 GMT+0 - Resolved - The overload has been resolved. All operations are back to normal. Sep 8, 01:05:00 GMT+0 - Identified - Our service is currently overloaded in the Japan region. As a result, some customers may receive 503 errors.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 12 hours and 45 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>01:50:00</var> GMT+0</small><br><strong>Resolved</strong> -
The overload has been resolved. All operations are back to normal..</p>
<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>01:05:00</var> GMT+0</small><br><strong>Identified</strong> -
Our service is currently overloaded in the Japan region. As a result, some customers may receive 503 errors..</p>
]]>
</content:encoded>
<pubDate>Tue, 8 Sep 2026 01:05:00 +0000</pubDate>
<link>https://status.soniox.com/incident/cmtsdz6z0068d1bnuiu6de5uu</link>
<guid>https://status.soniox.com/incident/cmtsdz6z0068d1bnuiu6de5uu</guid>
</item>
<item>
<title>Users failing to start sessions in EU deployment</title>
<description>
Type: Incident
Duration: 10 minutes
Affected Components: STT Real-time
Aug 25, 13:04:43 GMT+0 - Resolved - Between 12:50 and 13:03 UTC on August 25, new WebSocket connections to [stt-rt.eu.soniox.com](http://stt-rt.eu.soniox.com) failed to establish. Existing connections were unaffected throughout.
While enabling Cloudflare load balancing, traffic was routed through a hostname not covered by our Cloudflare certificate, causing TLS handshakes for new connections to fail. We rolled back the change and connections recovered.
Cloudflare&#039;s Universal SSL does not cover multi-level subdomains (unknowingly). We&#039;re manually provisioning certificate coverage for these hostnames before re-attempting the rollout. Aug 25, 12:55:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 10 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>13:04:43</var> GMT+0</small><br><strong>Resolved</strong> -
Between 12:50 and 13:03 UTC on August 25, new WebSocket connections to [stt-rt.eu.soniox.com](http://stt-rt.eu.soniox.com) failed to establish. Existing connections were unaffected throughout.
While enabling Cloudflare load balancing, traffic was routed through a hostname not covered by our Cloudflare certificate, causing TLS handshakes for new connections to fail. We rolled back the change and connections recovered.
Cloudflare&#039;s Universal SSL does not cover multi-level subdomains (unknowingly). We&#039;re manually provisioning certificate coverage for these hostnames before re-attempting the rollout..</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>12:55:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Tue, 25 Aug 2026 12:55:00 +0000</pubDate>
<link>https://status.soniox.com/incident/cmt8obhs602u00sp2tpxi5nyw</link>
<guid>https://status.soniox.com/incident/cmt8obhs602u00sp2tpxi5nyw</guid>
</item>
<item>
<title>Some users are experiencing failures with API key creation</title>
<description>
Type: Incident
Duration: 1 hour and 10 minutes
Affected Components: Console
Aug 24, 12:20:15 GMT+0 - Resolved - This incident has been resolved. Aug 24, 11:10:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 hour and 10 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>12:20:15</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>11:10:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Mon, 24 Aug 2026 11:10:00 +0000</pubDate>
<link>https://status.soniox.com/incident/cmt777fg91snu0zmejsrv0qbo</link>
<guid>https://status.soniox.com/incident/cmt777fg91snu0zmejsrv0qbo</guid>
</item>
<item>
<title>Login failing in console and mobile app</title>
<description>
Type: Incident
Duration: 53 minutes
Affected Components: Console
Jul 17, 13:22:31 GMT+0 - Resolved - This incident has been resolved. Jul 17, 12:30:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 53 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>13:22:31</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Fri, 17 Jul 2026 12:30:00 +0000</pubDate>
<link>https://status.soniox.com/incident/cmroy4cd10bcc0rlknfh84r9a</link>
<guid>https://status.soniox.com/incident/cmroy4cd10bcc0rlknfh84r9a</guid>
</item>
<item>
<title>Japan STT RT V5 degraded</title>
<description>
Type: Incident
Duration: 3 hours and 52 minutes
Affected Components: STT Real-time
Jun 30, 05:52:08 GMT+0 - Resolved - This incident has been resolved.
We experienced a service disruption that affected STT RT v5 availability in Japan region. During this period, some users may have experienced failures when starting streams and increased latency while using the service.
The issue was caused by an infrastructure capacity problem that impacted our ability to provision sufficient resources. We have resolved the issue and are taking steps to improve the reliability of our systems to prevent similar incidents in the future. Jun 29, 23:00:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 3 hours and 52 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>05:52:08</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved.
We experienced a service disruption that affected STT RT v5 availability in Japan region. During this period, some users may have experienced failures when starting streams and increased latency while using the service.
The issue was caused by an infrastructure capacity problem that impacted our ability to provision sufficient resources. We have resolved the issue and are taking steps to improve the reliability of our systems to prevent similar incidents in the future..</p>
<p><small>Jun <var data-var='date'> 29</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Mon, 29 Jun 2026 23:00:00 +0000</pubDate>
<link>https://status.soniox.com/incident/cmr07ix8s04j40rrrrr0j9ntc</link>
<guid>https://status.soniox.com/incident/cmr07ix8s04j40rrrrr0j9ntc</guid>
</item>
<item>
<title>Console sign-in issues</title>
<description>
Type: Incident
Duration: 50 minutes
Affected Components: Console
Jun 13, 21:10:00 GMT+0 - Resolved - This incident has been resolved. Jun 13, 20:20:00 GMT+0 - Investigating - Issue prevented users from successfully signing in or signing up on the Soniox Console.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 50 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>21:10:00</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>20:20:00</var> GMT+0</small><br><strong>Investigating</strong> -
Issue prevented users from successfully signing in or signing up on the Soniox Console..</p>
]]>
</content:encoded>
<pubDate>Sat, 13 Jun 2026 20:20:00 +0000</pubDate>
<link>https://status.soniox.com/incident/cmqdj64la0d68np6215dmzb1d</link>
<guid>https://status.soniox.com/incident/cmqdj64la0d68np6215dmzb1d</guid>
</item>
<item>
<title>US TTS outage</title>
<description>
Type: Incident
Duration: 1 hour and 27 minutes
Affected Components: TTS Real-time
Jun 4, 11:15:20 GMT+0 - Resolved - This incident has been resolved. Jun 4, 09:48:21 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 1 hour and 27 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>11:15:20</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>09:48:21</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Thu, 4 Jun 2026 09:48:21 +0000</pubDate>
<link>https://status.soniox.com/incident/cmpzbbml802wcqgpb2qy5bqjl</link>
<guid>https://status.soniox.com/incident/cmpzbbml802wcqgpb2qy5bqjl</guid>
</item>
<item>
<title>Increased latency in STT Real-time API in EU region</title>
<description>
Type: Incident
Duration: 21 minutes
Affected Components: STT Real-time
May 6, 13:58:08 GMT+0 - Resolved - This incident has been resolved. May 6, 13:36:54 GMT+0 - Investigating - Occasional increased latency when starting streams
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 21 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>13:58:08</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>13:36:54</var> GMT+0</small><br><strong>Investigating</strong> -
Occasional increased latency when starting streams.</p>
]]>
</content:encoded>
<pubDate>Wed, 6 May 2026 13:36:54 +0000</pubDate>
<link>https://status.soniox.com/incident/cmou3ptql0071hb1isgktqawz</link>
<guid>https://status.soniox.com/incident/cmou3ptql0071hb1isgktqawz</guid>
</item>
<item>
<title>Increased latency in STT Real-time API in EU region</title>
<description>
Type: Incident
Duration: 5 minutes
Affected Components: STT Real-time
May 6, 13:00:00 GMT+0 - Resolved - This incident has been resolved. May 6, 12:55:00 GMT+0 - Investigating - We are currently investigating this incident.
</description>
<content:encoded>
<![CDATA[<p><strong>Type:</strong> Incident</p>
<p><strong>Duration:</strong> 5 minutes</p>
<p><strong>Affected Components:</strong> </p>
<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Resolved</strong> -
This incident has been resolved..</p>
<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>12:55:00</var> GMT+0</small><br><strong>Investigating</strong> -
We are currently investigating this incident..</p>
]]>
</content:encoded>
<pubDate>Wed, 6 May 2026 12:55:00 +0000</pubDate>
<link>https://status.soniox.com/incident/cmou2mr89001sozl1xh3ph2un</link>
<guid>https://status.soniox.com/incident/cmou2mr89001sozl1xh3ph2un</guid>
</item>
</channel>
</rss>