Skip to main content
down.guideby Sazabi
Svix

Svix status history

12 incidents over the last year, newest first; 100.00% uptime (90 days), 99.99% uptime (12 months). History from before down.guide started reading the page is imported from Svix's own archive.

Month

2026-10

1 incident

  1. SvixDegraded
    Elevated latency in EU region
    lasted 1h 35mAPIeu
Month

2026-09

1 incident

  1. SvixDegraded
    Elevated error rate in US region
    lasted 2h 50mAPIus
Month

2026-08

1 incident

  1. SvixDegraded
    [Analytics] Delayed message listing in dashboard, portal, and list-message APIs
    lasted 1h 16mAPI, Application Portal, Dashboardus
Month

2026-07

2 incidents

  1. SvixPartial outage
    Dashboard logins failing
    lasted 14mDashboard
  2. SvixDegraded
    Elevated latency in US region
    lasted 0mus
Month

2026-06

2 incidents

  1. SvixDegraded
    [EU] elevated latency and errors for a small fraction of API requests
    lasted 0meu
  2. SvixPartial outage
    [EU] Elevated response times and error rates affecting some customers.
    lasted 0meu
Month

2026-03

2 incidents

  1. SvixDegraded
    [usw2] very small fraction of API errors (UNAFFECTED: delivery and create-message, only supporting API affected)
    lasted 15mAPI
  2. SvixPartial outage
    USW2: increased errors in the region due to AWS connectivity issues
    lasted 0m
Month

2025-12

1 incident

  1. SvixPartial outage
    [US only] Large messages (>300kb) experienced delayed delivery in the US region.
    lasted 0mus
Month

2025-11

1 incident

  1. SvixDegraded
    US region: create message API failures [ephemeral, resolved]
    lasted 0mus
Month

2025-10

1 incident

  1. SvixDegraded
    [INFORMATIONAL] Svix is *NOT* affected by the AWS outage.
    lasted 0m