Talk to sales

Outages ping. You pong.

Status pages and incident management for software teams. Declare an incident once, and every affected status page and feed shows your update.

Book a demo See the live demo
AcmeSubscribe
Partial outageAll systems operational1 of 3 components is affected. Details are below.All 3 components are working normally.
Updated just now
Elevated errors on the Payments APIInvestigating
  • Payments API

Some card payments are failing. We’re investigating and will post an update within 30 minutes.

Investigating14:04 UTC

Payments APIPartial outageOperational
30 days ago99.95% uptimeToday
CheckoutOperational
30 days ago100.00% uptimeToday
DashboardOperational
30 days ago99.99% uptimeToday

Keep score in public.

One status page per product, at yourproduct.agentpong.com or on your own domain, in your logo and colours. Live component status, 90 days of history and every incident you’ve handled. Readers who won’t visit get an Atom feed, JSON, an iCal calendar of maintenance and a widget for your own app.

Live demo status pageAll systems operational
6/6components operational
0open incidents
0maintenance windows scheduled
  • GitHubOperational
  • npm registryOperational
  • PyPIOperational
  • DNS over HTTPSOperational
  • Stripe API edgeOperational
  • WikipediaOperational

Read from the demo page’s public status.json. Its health checks run every minute.

Acmeacme.comSubscribe
All systems operationalAll 5 components are working normally.
Updated 12 seconds ago
Upcoming maintenance
Database upgrade for CheckoutScheduled

Sun 18 Oct, 02:00 – 02:30 UTC Starts in 5 days

  • Checkout
ComponentsOperationalDegradedPartial outageMajor outageMaintenance
API3
Payments APIOperational
90 days ago30 days ago99.95% uptimeToday
CheckoutOperational
90 days ago30 days ago100.00% uptimeToday
WebhooksOperational
90 days ago30 days ago99.99% uptimeToday
Apps2

Every incident is a rally.

Declare an incident once, even when it touches several products. Each update reaches every affected status page at the same moment, and when it’s over the timeline stays public, with the postmortem on the same page.

  1. The outage 14:02

    Health checks on the Payments API fail. The re-check 15 seconds later fails too, so it counts.

    You 14:04
  2. The outage 14:19

    A database failover in one region leaves payments there timing out.

    You 14:21
    IdentifiedOn both pages

    A database failover in one region is causing timeouts. We’re moving traffic to healthy regions.

  3. The outage 14:38

    Error rates fall back to normal. The health checks pass again.

    You 14:49
    ResolvedOn both pages

    Payments are processing normally. We’ll publish a postmortem on this page.

Resolved in 47 minutes. Postmortem published.

Three updates, two status pages, one timeline. The postmortem appears on the incident’s public page as soon as you publish it.

Works with the monitoring you already have.

Agent Pong doesn’t page anyone. Keep the tool that alerts your team, such as Checkly, a CI job or a cron script, and let it drive your status pages through the REST API.

Built-in health checks fill in the rest: HTTP checks every minute, re-checked 15 seconds after a failure before it counts, and heartbeats for your cron jobs. They set component status and the 90-day bars, and can open and resolve incidents for you.

Check an endpoint the way our health checks do

One GET request, the same one a health check sends. Nothing is stored.

Declare an incident from your monitoringPOST /api/v1/incidents
curl https://agentpong.com/api/v1/incidents \
  -H "Authorization: Bearer $AGENTPONG_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Elevated errors on the Payments API",
    "body": "Some card payments are failing. We are investigating.",
    "components": [
      { "component_id": "cmpPay7Rk2Qa", "impact": "partial_outage" },
      { "component_id": "cmpChk3Lw9Te", "impact": "degraded" }
    ]
  }'
  • POST/incidents/:id/updates Post an update
  • POST/incidents/:id/resolve Resolve
  • PATCH/components/:id Set a status
  • GET/pages/:slug Live page state

Team API keys, JSON in and out. Read the API docs

Your serve.

Bring one of your products to a demo. We’ll set up its status page with you and walk through an incident from first update to postmortem.

Book a demo See the live demo