Status, opens your public status page in a new tab
Demo

You're inside Northwind Digital, a fictional agency. Open anything, change anything: the data is made up and nothing you do here is saved.

Start free

Checkout API is down

Open

Kestrel Coffee Roasters · Kestrel Coffee · Checkout

503HTTP 503 Service Unavailable (upstream payment gateway)

Down for
41m 00s
Started
12:58 · 18 Aug 2026
Right now
Still failing
Failed checks
42 in a row

Wands crossedSomething is down

What happened, and what we did about it

  1. A check failed

    12:58 · 41 min ago

    Checkout API answered HTTP 503.

    Checkout API went down. Alerts sent to Slack and 2 members.

  2. Incident opened automatically

    12:58 · 41 min ago

    The monitor went from up to down, so this opened itself. Nobody filed it, and nobody has to remember to close it.

  3. Slack notified

    12:58 · 41 min ago

    Alert delivered.

  4. 2 members emailed

    12:58 · 41 min ago

    Alert delivered.

  5. Still watching

    now

    We check every 1 minute. The first check that passes closes this incident, sends the recovery notice, and clears the status page. There is nothing for you to acknowledge.

Where to look first

The service answered and said it is unavailable.

  1. Check whether this is your own maintenance mode or a feature flag before treating it as a fault. A deliberate 503 looks identical to a broken one from out here.

  2. The recorded error names the failing part: "HTTP 503 Service Unavailable (upstream payment gateway)". Start there rather than at the edge.

  3. Check capacity: connection pools and worker queues report as 503 once they are full.

These come from the error this check recorded, not from knowing your system. Treat them as where to look, not as what is wrong.

Your status page

Nobody needs to update it. Your public status page reads this incident live, so anyone watching already sees the outage. It clears itself the moment a check passes.

The monitor
NameCheckout API
Typehttp
Targethttps://api.kestrelcoffee.com/v2/checkout
Checkedevery 1 minute
Last checkjust now

This page is what a client sees when they ask what happened.

The failing status code, the error the check recorded, every alert that went out with its delivery status, and where to look first, derived from this failure rather than a generic checklist. Recorded as it happened rather than reconstructed afterwards.

Start monitoring free10 monitors free · no card