Skip to main content
Silent Outage

Monitoring denominated in dollars and dependencies, not pings.

Your uptime monitor is green. Your checkout has been broken for forty minutes.

Silent Outage watches the money and the providers behind it, not just the server. When revenue stops, you are paged with a dollar range for what it has cost so far and a verdict on whose fault it is.

Is it you, or is it your dependency?

Free: Available todayCron checks — your nightly backup, with a timezone and a grace time

Start free

No card, no password, no sales call. 10 free checks.

Estimated revenue lost$412–$689Verdict[PROVIDER] Likely provider

A real revenue alert, rendered by the same code that sends one. Figures are illustrative. The probe evidence is our own: 3 of the 3 checking locations this fleet names are running, and 2 have to agree before a probe reaches a verdict. The same eight fields on every alert — what broke, since when, what it cost, whose fault, what to check first — by email and by signed webhook alike.

Same outage. Two monitors.

2:23pm on a Monday. Your payment provider starts refusing card authorisations. Every page returns 200, and not one customer can pay you.

  • A commodity uptime monitor

    Watching: does the server answer?

    • HTTP 200 from every location.
    • Response time normal.
    • No incident. No page.

    You find out at 3:04pm, from a customer, in a support ticket.

  • Silent Outage

    Watching: is money still moving, and is your stack healthy?

    • Charges in the last 30 minutes: 0, against 34 ± 9 for this hour of this weekday.
    • Estimated loss so far, as a range with a confidence label.
    • Your provider posted a partial outage six minutes earlier, and our probes of their API were already failing.
    • Verdict: likely provider, likely you, or inconclusive — with the evidence it rests on.

    You are paged at 2:24pm, and the first line says it is not your deploy.

A ping check answers "is the server up" — free here, as it has been everywhere for a decade. The question worth paying for is whether you are still getting paid.

What you are actually buying

Three layers, and the order matters: the first two are the reason to pay. The wedge above is the first two doing their job.

  • Dollars

    An outage is priced, not just reported.

    A range with a confidence label, never a point — and "below detection floor" rather than a guess when the hour is too quiet to judge.

  • Dependencies

    Every incident says whether it is you or one of them.

    Likely provider, likely you, or inconclusive — with the evidence behind it.

  • Pings

    The commodity, given away.

    Free, because it is table stakes: ping URLs, start/success/fail signals, run durations and DST-safe schedules.

The stack we watch for you

The providers we watch, read from the same catalogue the checks run against — around twenty covered deeply rather than a six-thousand-logo catalogue covered shallowly. We read each status feed and probe each API ourselves every sixty seconds, and either can put a verdict on your incident.

  • OpenAI
  • Anthropic
  • Stripe
  • Vercel
  • Supabase
  • Cloudflare
  • Twilio
  • Fly.io
  • Pinecone
  • Upstash
  • Deepgram
  • Resend
  • PlanetScale
  • ElevenLabs
  • Neon
  • AWS (incl. SES)
  • Google Cloud (incl. Gemini)
  • Railway
  • Postmark

No logos and no testimonials on this page: this list is the one piece of evidence we have that is simply true.

Before you hand anyone a Stripe key

  • What can you do with my Stripe key?

    Read six things and nothing else. A read-only restricted key scoped to Charges, PaymentIntents, Checkout Sessions, Invoices, Payouts and Events; Customers and PaymentMethods stay at None, so it cannot reach card data. We measure the scopes at connect time, and store amounts, counts, currency, timestamps and event ids — never a payload.

  • How soon does revenue monitoring work?

    Immediately: what your webhook delivered is compared against Stripe’s own API, so a broken pipe is caught with no history and a stopped stream once 1 payment has arrived and your revenue is regular enough to judge. From day 7 the hour-of-week baseline is ready, and silence and volume collapse are judged against it. By day 28 each hour of your week has 4 observations, and an estimate carries high confidence rather than low.

  • What happens when you go down?

    Alerts are written to a durable queue the moment a problem is detected, so one computed while nothing can send it is not lost. A separate process with its own build and service is the only sender, and a queued page goes out when it comes back. Every attempt leaves a receipt, and an alert that runs out of them is recorded as a non-delivery rather than dropped. And a mass of checks going quiet at once is read as ours: they go unknown, and we page ourselves rather than you.

  • Am I locked in?

    The core is open source under the AGPL-3.0 and you can run it yourself: the hosted service is this same code. Instrumenting is one HTTP request per job: one line of curl, or any HTTP client, against an endpoint we document.

How it works

Four steps, your first check live in under ten minutes, and nothing to install on a server.

  1. Sign in with an emailed link

    No password to choose, store or lose. Signing up asks for an email address and no other personal detail — what we then hold about your monitoring is listed on the privacy page.

  2. Paste a crontab line, or add two lines of code

    A cron expression and a timezone become a check with its own ping URL.

  3. Connect Stripe with a read-only restricted key

    We learn your normal revenue hour by hour, then tell you when it stops.

  4. Pick your providers, and say where alerts go

    Email, or a signed outbound webhook. Never to a destination you have not confirmed.

Plans

  • Free

    Free

    A side project, or trying this before paying for it.

    10 checks

    7 days of check history

    Available today

    • Heartbeat and dead-man’s-switch checks
    • Cron checks — your nightly backup, with a timezone and a grace time
    • HTTP uptime checks, confirmed from more than one location
    • Email alerts
    • Slack alerts, with ack and resolve from chat
    • Signed outbound webhooks on triggered, acknowledged and resolved

    Coming later

    • [UNAVAILABLE] Discord alerts, with ack and resolve from chat

    Start free

  • Early access

    Indie

    $19/mo

    A solo founder at a few thousand a month, with no ops and no SRE.

    50 checks

    30 days of check history

    Everything in Free, plus:

    Available today

    • Revenue monitoring — Stripe webhook silence and payment-volume collapse
    • Business-event checks — a signup or an order that stopped arriving
    • Synthetic checkout, replayed against Stripe test mode
    • Dollar-loss estimates on revenue incidents
    • Dependency monitoring for the curated provider list
    • Verdict — likely provider, likely you, or inconclusive

    Coming later

    • [UNAVAILABLE] SMS escalation
    • [UNAVAILABLE] Voice-call escalation

    Not on sale yet: Indie cannot be bought here.

  • Early access

    Startup

    $49/mo

    A small team that has already had one silent checkout outage and wants the dollar figure.

    200 checks

    90 days of check history, 30 days of per-ping detail

    Everything in Indie, plus:

    Available today

    • Escalation that moves on to a second person when the first misses it

    Coming later

    • [UNAVAILABLE] LLM quality-drift canaries: latency, refusals, output length and rubric scores
    • [UNAVAILABLE] Alert routing decided per project rather than per account

    Not on sale yet: Startup cannot be bought here.

  • Waitlist

    Need more than this?

    Team sits above Startup and is still being built: a plan that would buy you nothing today is not one we are going to sell you, and each goes on the page when it has something on it.

    • Joining is signing up free: your account is the list, and the address you sign in with is the one we would write to.
    • Everything you set up on Free is what you keep — moving up adds layers.

    Join the list

Every limit each plan sets, in one table: Compare every plan

Where this product is today

Silent Outage is in early access. Everything else works today, and every exception is here rather than repeated beside each one.

Paid plans are priced and not open yet

Free is free and works today. The paid plans are priced and are not self-serve yet: every account starts on Free, billing opens later, and we move you across then.

Anything marked [BETA]

These work today, with the limitation named beside each.

  • [BETA] Public status pages: You can configure and preview your page now. Publishing does not put anything on the internet: a published page has no public host and no address anyone can open. Everything you configure is saved, and the page publishes itself as soon as the status host is live.
Anything marked [UNAVAILABLE]

Included on the plan that lists them, not running yet, and nothing to configure or pay for.

  • [UNAVAILABLE] Discord alerts are not switched on yet.
  • [UNAVAILABLE] SMS and voice escalation are not switched on yet.
  • [UNAVAILABLE] LLM quality-drift canaries are not switched on yet.
  • [UNAVAILABLE] Alerts go to the destinations you confirm for the account, not per project.
Silent Outage