We started checking Svix on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Svix reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Svix's own status page declared. Below it, any public chatter we saw about Svix and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Svix's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Svix in the last 24 hours, which is not evidence that nothing is wrong.
Svix's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Svix's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Svix next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
446
US-West
100.00%
342
Europe
100.00%
313
Asia-Pacific
100.00%
189
Their declared record
Svix's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Elevated latency in EU regionMinor incident
Oct 16, 2026, 4:45 PM UTC to Oct 16, 2026, 6:20 PM UTC (1h 35m)resolved
their latest update (Oct 16, 2026, 6:20 PM UTC): This incident is resolved
Elevated error rate in US regionMinor incident
Sep 3, 2026, 7:41 PM UTC to Sep 3, 2026, 10:31 PM UTC (2h 50m)resolved
their latest update (Sep 3, 2026, 10:31 PM UTC): This incident is resolved
[Analytics] Delayed message listing in dashboard, portal, and list-message APIsMinor incident
Aug 12, 2026, 6:20 PM UTC to Aug 12, 2026, 7:36 PM UTC (1h 16m)resolved
their latest update (Aug 12, 2026, 7:36 PM UTC): This incident has been resolved
Dashboard logins failingPartial outage
Jul 30, 2026, 8:44 PM UTC to Jul 30, 2026, 8:59 PM UTC (14 min)resolved
their latest update (Jul 30, 2026, 8:59 PM UTC): This incident has been resolved
Elevated latency in US regionAll systems operational
Jun 22, 2026, 8:45 PM UTC to Jun 22, 2026, 8:45 PM UTC (0 min)resolved
their latest update (Jun 22, 2026, 8:45 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 pe…
[EU] elevated latency and errors for a small fraction of API requestsMinor incident
Jun 12, 2026, 11:30 PM UTC to Jun 12, 2026, 11:30 PM UTC (0 min)resolved
their latest update (Jun 12, 2026, 11:30 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.
[EU] Elevated response times and error rates affecting some customers.Partial outage
Jun 3, 2026, 12:00 AM UTC to Jun 3, 2026, 12:00 AM UTC (0 min)resolved
their latest update (Jun 3, 2026, 12:00 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, 00:38 - 00:48, 03:27 - 03:29, 5:34 - 5:36 UTC.
This happened due to a significant spike in traffic …
[usw2] very small fraction of API errors (UNAFFECTED: delivery and create-message, only supporting API affected)Minor incident
Mar 24, 2026, 7:11 PM UTC to Mar 24, 2026, 7:27 PM UTC (15 min)resolved
their latest update (Mar 24, 2026, 7: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.
USW2: increased errors in the region due to AWS connectivity issuesPartial outage
Mar 12, 2026, 12:57 AM UTC to Mar 12, 2026, 12:57 AM UTC (0 min)resolved
their latest update (Mar 12, 2026, 12:57 AM UTC): The issue resolved once the AWS issues resolved.
[US only] Large messages (>300kb) experienced delayed delivery in the US region.Partial outage
Dec 4, 2025, 8:00 PM UTC to Dec 4, 2025, 8:00 PM UTC (0 min)resolved
their latest update (Dec 4, 2025, 8:00 PM UTC): This was automatically resolved, no action needed.
Showing the 10 most recent of 40 incidents Svix has declared in the history we hold.
These entries are Svix's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Svix's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.