Vendor record
Svix
Checked
Front door check counts and Svix’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Svix endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- api.svix.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Svix product, region or your app worked.
How we count front door checksSvix says
Incident posts from Svix’s status page, with its titles, impact levels and times. They say what Svix chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
1
incidents Svix posted, last 30 days
Most recent records · all dates
Elevated latency in EU region
MinorSvix’s postStarted, per Svix
Latest status Svix postedMonitoring. No resolution posted.
Elevated error rate in US region
MinorSvix’s postStarted, per Svix
Closed in our record(2h 58m)
[Analytics] Delayed message listing in dashboard, portal, and list-message APIs
MinorSvix’s postStarted, per Svix
Closed in our record(1h 30m)
Dashboard logins failing
MajorSvix’s postStarted, per Svix
Closed in our record(16m)
[usw2] very small fraction of API errors (UNAFFECTED: delivery and create-message, only supporting API affected)
MinorSvix’s postStarted, per Svix
Closed in our record(16m)
Your code, your dependencies
See which of your code paths call Svix
Connect GitHub or GitLab to find where your public or private repository uses Svix. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Svix status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Svix currently down?
Svix's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Svix last have an outage?
The most recent closed incident record began 42 days ago and spans 2h 58m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Svix?
No. CheckUpstream checks Svix’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Svix in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Svix?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.