Svix Outage History
Svix is up right nowPingoru has recorded 40 incidents for Svix: 11 in the last 12 months and 4 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 3 | 30 of 720 (4%) |
| July 2026 | 1 | 0 of 744 (0%) |
| August 2026 | 1 | 1 of 744 (0%) |
| September 2026 | 1 | 3 of 720 (0%) |
| October 2026 | 1 | 2 of 516 (0%) |
Incidents, newest first
Minor October 16, 2026 Elevated latency in EU region 1h 34m API
Started Oct 16, 2026, 04:45 PM UTC· resolved Oct 16, 2026, 06:20 PM UTC
- investigating Oct 16, 2026, 04:45 PM UTC
Some customers in the EU region are experiencing elevated latency and very infrequent errors creating messages. Svix engineers are investigating.
- monitoring Oct 16, 2026, 05:11 PM UTC
A fix has been implemented and engineers are monitoring
- resolved Oct 16, 2026, 06:20 PM UTC
This incident is resolved
Minor September 3, 2026 Elevated error rate in US region 2h 49m API
Started Sep 03, 2026, 07:41 PM UTC· resolved Sep 03, 2026, 10:31 PM UTC
- investigating Sep 03, 2026, 07:41 PM UTC
Engineers are investigating a small number of errors and timeouts in the US region affecting some message APIs
- investigating Sep 03, 2026, 08:08 PM UTC
Engineers are continuing to investigate the issue. A vanishingly small number of create-message requests (fewer than 90) are affected. Some customers may see data population delays in the list-message endpoints.
- identified Sep 03, 2026, 09:40 PM UTC
Engineers have identified the problem and applied a fix; queues are catching up
- resolved Sep 03, 2026, 10:31 PM UTC
This incident is resolved
Minor August 12, 2026 [Analytics] Delayed message listing in dashboard, portal, and list-message APIs 1h 16m API, Application Portal, Dashboard
Started Aug 12, 2026, 06:20 PM UTC· resolved Aug 12, 2026, 07:36 PM UTC
- investigating Aug 12, 2026, 06:20 PM UTC
Some customers in the US region are seeing a delay in created messages being visible in the list-message APIs, the app-portal, and the dashboard. Messages are still being delivered normally. Svix engineers are investigating.
- identified Aug 12, 2026, 06:46 PM UTC
Engineers have identified the source of the issue and are working on mitigation. Message delivery continues to be working normally.
- resolved Aug 12, 2026, 07:36 PM UTC
This incident has been resolved
Major July 30, 2026 Dashboard logins failing 14m Dashboard
Started Jul 30, 2026, 08:44 PM UTC· resolved Jul 30, 2026, 08:59 PM UTC
- investigating Jul 30, 2026, 08:44 PM UTC
Some customers are unable to log in to the dashboard and may receive a "Something went wrong" error; engineers are investigating
- identified Jul 30, 2026, 08:47 PM UTC
Svix engineers have identified the problem and are deploying a remediation
- monitoring Jul 30, 2026, 08:54 PM UTC
Dashboard logins should be working now; engineers will continue to monitor
- resolved Jul 30, 2026, 08:59 PM UTC
This incident has been resolved
Notice June 22, 2026 Elevated latency in US region 48m
Started Jun 22, 2026, 07:45 PM UTC· resolved Jun 22, 2026, 08:33 PM UTC
- resolved Jul 17, 2026, 09:00 PM UTC
Svix experienced elevated latency and a small number of errors in the US region between 19:45Z and 20:33Z due to a configuration change that enabled an experimental idempotency flow for an unexpectedly-large number of users. Approximately 12 requests saw 5XX errors during this period, and several thousand requests took longer than expected. This incident has been fully remediated.
Minor June 12, 2026 [EU] elevated latency and errors for a small fraction of API requests –
Started Jun 12, 2026, 11:30 PM UTC· resolved Jun 12, 2026, 11:30 PM UTC
- resolved Jun 13, 2026, 09:53 PM UTC
A small fraction of API requests get errors and increased latency has been occurring occasionally in the EU region over the last 24hrs. Retries (including automatic retries by the SDK) should avoid the issue.
Major June 3, 2026 [EU] Elevated response times and error rates affecting some customers. 1d 5h
Started Jun 03, 2026, 12:00 AM UTC· resolved Jun 04, 2026, 05:36 AM UTC
- resolved Jun 03, 2026, 02:04 AM UTC
We experienced an issue where some customer in the EU region experienced elevated response times and error rates. The time frames when this occurred: 23:44 - 23:46, 00:05 - 00:13, and 00:38 to 00:48 UTC. This happened due to a significant spike in traffic (161x traffic the minute before), and the system not scaling fast enough to catch up. This affected customers routed to the same nodes that experienced this load.
Minor March 24, 2026 [usw2] very small fraction of API errors (UNAFFECTED: delivery and create-message, only supporting API affected) 15m API
Started Mar 24, 2026, 07:11 PM UTC· resolved Mar 24, 2026, 07:27 PM UTC
- identified Mar 24, 2026, 07:11 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Mar 24, 2026, 07:27 PM UTC
It's been solved ~10mins ago, and the resolution has been confirmed. There have been a ~10 errors a minute (tiny fraction of the Svix API calls) and none affecting delivery or message ingestion.
Major March 12, 2026 USW2: increased errors in the region due to AWS connectivity issues –
Started Mar 12, 2026, 12:57 AM UTC· resolved Mar 12, 2026, 12:57 AM UTC
- resolved Mar 12, 2026, 01:23 AM UTC
The issue resolved once the AWS issues resolved.
Major December 4, 2025 [US only] Large messages (>300kb) experienced delayed delivery in the US region. –
Started Dec 04, 2025, 08:00 PM UTC· resolved Dec 04, 2025, 08:00 PM UTC
- resolved Dec 06, 2025, 02:43 AM UTC
This was automatically resolved, no action needed.
Notice November 24, 2025 US region: create message API failures [ephemeral, resolved] –
Started Nov 24, 2025, 09:30 PM UTC· resolved Nov 24, 2025, 09:30 PM UTC
- resolved Nov 24, 2025, 09:41 PM UTC
Load balancing misconfiguration caused ~90% of "create message" API calls to fail in the US region. The configuration was immediately reverted which returned to full functionality. Affected time: 2025-11-24 at ~21:23:00 UTC Svix SDKs have retries baked in and would in most cases transparently recover.
Notice October 20, 2025 [INFORMATIONAL] Svix is *NOT* affected by the AWS outage. –
Started Oct 20, 2025, 05:00 PM UTC· resolved Oct 20, 2025, 05:00 PM UTC
- resolved Oct 20, 2025, 05:27 PM UTC
We've been asked multiple times today, so just sharing that Svix is *NOT* affected by the AWS outage.
Minor September 12, 2025 Delayed delivery for some throttled messages (when endpoint throttling is configured) - normal delivery unaffected. –
Started Sep 12, 2025, 09:09 PM UTC· resolved Sep 12, 2025, 09:09 PM UTC
- resolved Sep 12, 2025, 09:09 PM UTC
Due to a race condition in the throttling code, some message may have been throttled for a much longer time than they were supposed to. The issue has been fixed and everything should be back in order. No action needed.
Major August 1, 2025 Delayed message delivery in US region 23m API
Started Aug 01, 2025, 09:12 PM UTC· resolved Aug 01, 2025, 09:36 PM UTC
- investigating Aug 01, 2025, 09:12 PM UTC
We are currently investigating this issue.
- monitoring Aug 01, 2025, 09:24 PM UTC
Issue has been identified and fixed. Monitoring.
- resolved Aug 01, 2025, 09:36 PM UTC
This was indeed resolved earlier.
Minor July 17, 2025 Increased latency in get/list message API calls (delivery unaffected) –
Started Jul 17, 2025, 11:30 PM UTC· resolved Jul 17, 2025, 11:30 PM UTC
- resolved Jul 17, 2025, 11:53 PM UTC
We had a temporary increase in request latency for API calls reading from the message analytics db. Delivery was unaffected.
Major July 17, 2025 [resolved] delayed delivery for some throttled messages (when endpoint throttling is configured) - normal delivery unaffected. –
Started Jul 17, 2025, 11:00 PM UTC· resolved Jul 17, 2025, 11:00 PM UTC
- resolved Jul 18, 2025, 01:29 AM UTC
Due to a race condition in the throttling code, some message may have been throttled for a much longer time than they were supposed to. The issue has been fixed and everything should be back in order. No action needed.
Notice July 3, 2025 [US] Delay in Log Display for Webhook Events (delivery unaffected) –
Started Jul 03, 2025, 10:00 PM UTC· resolved Jul 03, 2025, 10:00 PM UTC
- resolved Jul 04, 2025, 04:08 AM UTC
Messages are taking longer than usual to show in the log display. The delivery itself is unaffected.
Minor January 27, 2025 [EU] Some message querying APIs are experiencing higher latency (message delivery and other API calls are unaffected) 3m API
Started Jan 27, 2025, 12:30 AM UTC· resolved Jan 27, 2025, 12:33 AM UTC
- investigating Jan 27, 2025, 12:30 AM UTC
We are currently investigating this issue.
- investigating Jan 27, 2025, 12:30 AM UTC
We are continuing to investigate this issue.
- identified Jan 27, 2025, 12:30 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jan 27, 2025, 12:33 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 27, 2025, 12:33 AM UTC
This incident has been resolved.
Notice January 19, 2025 EU: some requests were timing out due to increased latency. –
Started Jan 19, 2025, 01:15 PM UTC· resolved Jan 19, 2025, 01:15 PM UTC
- resolved Jan 20, 2025, 01:52 AM UTC
Sorry also for not updating the status page before, it looked ephemeral when it first surfaced. The issue was one API node that was having networking issues and was failing to connect to the rest of the systems and was timing out while at it. Only requests routed to this API node were affected, so retries would succeed. It's now been resolved.
Minor December 16, 2024 Some rate-limited messages were significantly delayed –
Started Dec 16, 2024, 05:00 AM UTC· resolved Dec 16, 2024, 05:00 AM UTC
- resolved Dec 31, 2024, 08:00 PM UTC
We have experienced an issue that caused some messages on the platform to be significantly delayed before delivery. Only a small fraction of our customers and an even smaller fraction of messages are affected. There is NO ACTION REQUIRED on your end; the issue is already resolved. Before I go into further details I want to apologize to those that are affected by this. We know you rely on us for reliable webhook delivery, and we don't take this responsibility lightly. We take extensive measures in order to prevent issues from ever happening, though unfortunately this was caused by a rare race condition, which is why both our manual reviews and testing as well as automated testing didn't catch it. Additionally, since rate-limited (throttled) messages are delayed (by definition) they are excluded from our usual delivery latency metrics and alerting (as they should be delayed). So we weren't alerted either. What is rate-limiting (throttling)? While Svix can handle however many messages you send us, your customers' endpoints may not be able to. In order to avoid overloading your customer endpoints, they can define a maximum delivery rate. If they are sent more messages a second than they can handle, Svix will buffer the requests and send it to them at the rate they set. You can read more about it in the rate-limiting (throttling) docs. We recently made a few improvements to the rate-limiting mechanism, and the issue was related to that. Because the issue was related to rate-limiting it only affected endpoints that had rate-limiting enabled (either by you or your customers). In addition to requiring rate-limiting to be set and enabled, it was only triggered when rate limiting was actually hit (e.g. if you had a rate limit of 100 and 50 messages were sent, there was no rate-limiting so the bug couldn't trigger), and when there was backpressure on the rate-limit (so going above the limit was sustained). In addition to that, it also required AWS SQS to suffer from increased latency (happens on occasion). The race condition that was triggered there, made it so that some messages were not immediately scheduled for an additional trigger (after the throttling ends) which was what was causing the delayed invocation. The issue was first introduced when the new rate-limiting mechanism was rolled to production. Following a testing period in staging, we decided it was ready for production use. We then enabled it for 0.1% of the traffic on the 20th of November, ramping up all the way to 10% of the traffic on the 16th of December. We deployed a fix for the core issue on the 16th of December. The fix was for a benign symptom that was caused by the same core issue. At that stage, however, it was not clear messages rate-limiting could cause delays to such an extent so we didn't proactively search for affected messages. This is why alerting affected customers was delayed. We are very proud of our reliability track record, and we know we fell short of it in this scenario. As mentioned above, we have many measures in place to help us prevent issues like these from ever happening, though in this case they were insufficient due to the rare scenario required to trigger this race condition. All of this doesn't change the fact that your service was adversely affected by this, and I'm extremely sorry about that. Please let me know if you have any questions or if there's anything else I can help you with. – Tom