ResolvedMinorStytch
Increase in 500 errors
An update to our DB caused around 1.5 minutes of increased 500's in our API. Apologies for the interruption.
Outage alerts
CheckedGet Slack alerts when Stytch goes down
Email alerts are free for up to 5 providers — Slack, Teams, Discord, and webhook delivery come with paid plans. Every alert is driven by Stytch's official status feed, checked about every 10 minutes around the clock.
How to get Stytch outage alerts
- Create your free account. Sign in with GitHub, Google, or an emailed link on the account page — no password, no card.
- Add Stytch to your alerts. The 60-second onboarding asks which providers you rely on; pick Stytch and free email alerts are live immediately (up to 5 providers).
- Want it in Slack or Discord? Paid plans add those channels plus raw webhooks: create a subscription, paste your webhook URL, and press Send test to prove the wiring in seconds. The alert setup guide walks through creating the webhook URL in each app.
Why it matters
Recent Stytch incident activity
Stytch recorded 100% uptime across 1 monitored day in the last 90 days. The official feed logged 5 incident entries in that window — exactly the changes subscribers hear about first.
ResolvedMinorStytch
Increase in 5XX errors
A network connectivity degradation in one of the regions where our infrastructure is hosted disrupted traffic, resulting in some timeouts. Steps will be taken to mitigate this in the future.
What triggers Stytch alerts
New incident
A fresh incident appeared on the official feed and started within the last 24 hours — historical backfills never alert.
Incident update
An open incident moved through its lifecycle (investigating → identified → monitoring …).
Incident resolved
An incident was resolved upstream, or disappeared from the provider's active feed.
Status change
The provider's overall status flipped (e.g. Operational → Partial outage).
Every delivery is claimed exactly once per event, retried once on failure, and recorded — overlapping check runs can never double-notify you. Alerts are driven by Stytch's official status source: the official Stytch status page remains the authoritative reference.
Prefer to pull instead of push?
Everything on this page is also machine-readable, free, and account-less: subscribe to the Stytch RSS feed, poll the JSON API, or embed the live Stytch status badge in a README or dashboard.
FAQ
Stytch alert questions
Short answers to what alert subscribers ask most.
How fast will I know when Stytch goes down?
OutageDeck checks Stytch's official status feed about every 10 minutes, around the clock. The first check that sees a new incident or a status change fires your alert immediately, so email, Slack, Teams, Discord, and webhook subscribers typically know within minutes of the official feed changing.
Are Stytch outage alerts free?
Yes — every account includes free email alerts for up to 5 providers, no card required. Paid plans add Slack, Teams, Discord, and webhook delivery, more subscriptions, and higher API quotas.
Which Stytch events trigger an alert?
New incidents on the official feed (when they started within the last 24 hours), incident lifecycle changes, resolutions, and provider-level status changes. A subscription can watch just Stytch, and on a paid plan your whole stack or individual Stytch services.
Can I follow Stytch status without an account?
Yes. The Stytch RSS feed, the public JSON API, and the embeddable status badge are free with no sign-up — alerts exist so changes get pushed to you instead of you re-checking a page.
Outage alerts
Ready to stop refreshing status pages?
Free email alerts for up to 5 providers — no card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.