Incident History
Sep 30, 2026
5 days ago
Short disruption of HTTP API and web app
Major OutageResolved · September 30, 8:20 AM GMT+2 (after less than a minute)
On September 30, 2026, between 08:20 and 08:26 CEST (06:20 to 06:26 UTC), requests to our HTTP API and the web app were delayed or failed with timeouts and HTTP 503 errors.
The cause was a network storage system that stopped responding, which blocked request processing on our application servers. Service was restored at 08:26 CEST.
Requests that failed during this period were not processed and need to be sent again. Messages that had already been accepted were sent. For a small number of them, the final delivery report could not be processed, so their status may still show as transmitted.
We have changed our configuration so that an outage of this storage system can no longer affect the API as a whole.
We apologize for the inconvenience.
Sep 10, 2026
25 days ago
Resolved · September 10, 2:15 PM GMT+2 (after less than a minute)
We are currently experiencing a temporary disruption affecting text-to-speech processing. As a result, some requests may currently fail or experience delays.
Our technical team is investigating the issue and working to restore full service as quickly as possible.
We apologize for the inconvenience and will provide an update as soon as the service has been fully restored.
Current status: Service restored. We are continuing to monitor the system to ensure stable operation.
Sep 2, 2026
1 month ago
Resolved · September 2, 6:56 AM GMT+2 (after 25 minutes)
Status changed: partial outage → operational
Investigating · September 2, 6:31 AM GMT+2
Status changed: operational → partial outage
Sep 2, 2026
1 month ago
Resolved · September 2, 3:28 AM GMT+2 (after 1h 23m)
Status changed: partial outage → operational
Investigating · September 2, 2:04 AM GMT+2
Status changed: operational → partial outage
Sep 2, 2026
1 month ago
Resolved · September 2, 12:55 AM GMT+2 (after 15 minutes)
Status changed: partial outage → operational
Investigating · September 2, 12:40 AM GMT+2
Status changed: operational → partial outage
Sep 2, 2026
1 month ago
Resolved · September 2, 12:34 AM GMT+2 (after 29 minutes)
Status changed: partial outage → operational
Investigating · September 2, 12:05 AM GMT+2
Status changed: operational → partial outage
Aug 31, 2026
1 month ago
Resolved · August 31, 10:36 AM GMT+2 (after 11 minutes)
Status changed: degraded performance → operational
Investigating · August 31, 10:24 AM GMT+2
Status changed: operational → degraded performance
Aug 20, 2026
1 month ago
Resolved · August 20, 3:36 PM GMT+2 (after 1h 12m)
Status changed: partial outage → operational
Investigating · August 20, 2:24 PM GMT+2
Status changed: operational → partial outage
Aug 18, 2026
1 month ago
Resolved · August 18, 4:27 PM GMT+2 (after 3h 1m)
Status changed: partial outage → operational
Investigating · August 18, 1:26 PM GMT+2
Status changed: operational → partial outage
Aug 15, 2026
1 month ago
Resolved · August 16, 1:02 AM GMT+2 (after 1h 36m)
Status changed: partial outage → operational
Investigating · August 15, 11:25 PM GMT+2
Status changed: operational → partial outage
Aug 3, 2026
2 months ago
Resolved · August 3, 4:06 AM GMT+2 (after 9 minutes)
Status changed: major outage → operational
Investigating · August 3, 3:56 AM GMT+2
Status changed: operational → major outage
Jul 23, 2026
2 months ago
Resolved · July 24, 11:51 AM GMT+2 (after 15h 13m)
Status changed: degraded performance → operational
Investigating · July 23, 8:38 PM GMT+2
Status changed: operational → degraded performance
Jul 22, 2026
2 months ago
Resolved · July 22, 4:31 PM GMT+2 (after 56 minutes)
Status changed: degraded performance → operational
Investigating · July 22, 3:34 PM GMT+2
Status changed: operational → degraded performance
Jul 22, 2026
2 months ago
Resolved · July 22, 2:56 PM GMT+2 (after 21 minutes)
Status changed: degraded performance → operational
Investigating · July 22, 2:34 PM GMT+2
Status changed: operational → degraded performance
Jul 20, 2026
2 months ago
Resolved · July 20, 6:07 PM GMT+2 (after 3h 44m)
Status changed: major outage → operational
Investigating · July 20, 2:23 PM GMT+2
Status changed: operational → major outage
Jul 20, 2026
2 months ago
Resolved · July 20, 1:03 PM GMT+2 (after 21 minutes)
Status changed: major outage → operational
Investigating · July 20, 12:41 PM GMT+2
Status changed: operational → major outage
Jul 17, 2026
2 months ago
Resolved · July 17, 10:56 AM GMT+2 (after 8 minutes)
Status changed: major outage → operational
Investigating · July 17, 10:47 AM GMT+2
Status changed: operational → major outage
Jul 14, 2026
2 months ago
Resolved · July 14, 4:12 AM GMT+2 (after 11 minutes)
Status changed: partial outage → operational
Investigating · July 14, 4:01 AM GMT+2
Status changed: operational → partial outage
Jul 14, 2026
2 months ago
Resolved · July 14, 3:41 AM GMT+2 (after 26 minutes)
Status changed: partial outage → operational
Investigating · July 14, 3:14 AM GMT+2
Status changed: operational → partial outage
Jul 8, 2026
2 months ago
Resolved · July 8, 5:37 AM GMT+2 (after 2h 7m)
Status changed: partial outage → operational
Investigating · July 8, 3:29 AM GMT+2
Status changed: operational → partial outage