Service Status Webhooks

Statuspage.io → Alert24: Mirror Dependency Status Automatically

Sync third-party Statuspage.io status pages (AWS, GitHub, Stripe) into Alert24 automatically. Uses Alert24's built-in status page scraper or a custom webhook.

Many services you depend on — AWS, GitHub, Stripe, Twilio — publish their status on Statuspage.io pages. Alert24 can scrape these pages and reflect their status in your own services and status page. When AWS has an outage, your Alert24 dashboard can show it automatically, without you manually posting an update.

Option A: Alert24's built-in status page scraper (recommended)

Alert24 has a native status page scraper check type that monitors Statuspage.io and similar pages directly.

  1. Go to Monitoring → Add check → Status Page
  2. Enter the URL of the Statuspage.io page (e.g., https://status.stripe.com)
  3. Select which components to monitor (e.g., "Stripe API")
  4. Link to an Alert24 service (e.g., your "Payments" service)
  5. Enable Auto-create incidents and Auto-resolve incidents
  6. Set your check interval and save

Alert24 polls the Statuspage.io JSON API and maps component status to your service status automatically.

Option B: Statuspage.io outbound webhook → Alert24

Some Statuspage.io pages offer subscriber webhooks. If the service you're monitoring has them enabled:

  1. In Alert24: Create a webhook receiver (Settings → Webhook Receivers) linked to the service you want to update. Set status field path to component.status and map:

    operational → operational
    degraded → degraded_performance, partial_outage
    down → major_outage
    
  2. In Statuspage.io (subscriber page): Subscribe to webhook notifications for the third-party status page (if they support it) and point the webhook URL to your Alert24 receiver.

Statuspage.io JSON API (manual polling)

You can also poll the Statuspage.io API yourself and forward to Alert24:

#!/bin/bash
# poll-statuspage.sh — run every 5 minutes from cron

STATUSPAGE_API="https://status.stripe.com/api/v2/components.json"
ALERT24_WEBHOOK="https://app.alert24.net/api/webhooks/incoming/YOUR_TOKEN"

# Get the API component status
COMPONENT_STATUS=$(curl -s "$STATUSPAGE_API" | \
  jq -r '.components[] | select(.name == "API") | .status')

curl -s -X POST "$ALERT24_WEBHOOK" \
  -H "Content-Type: application/json" \
  -d "{\"component_status\": \"$COMPONENT_STATUS\", \"source\": \"statuspage\"}"

Map in your Alert24 webhook receiver:

operational → operational
degraded → degraded_performance, partial_outage
down → major_outage

Tips

  • Option A is strongly preferred — Alert24's native scraper handles auth, polling frequency, JSON parsing, and status mapping automatically. Only use Option B or the manual polling script if you need a Statuspage.io provider that isn't in Alert24's provider catalog.
  • Provider catalog: Alert24 already has pre-built scrapers for AWS, GitHub, Stripe, Cloudflare, and dozens more. Check Monitoring → Add check → Status Page to see the full list before building a custom integration.
  • Incident correlation: When a third-party status page shows a major outage, Alert24 can automatically open an incident on your account. This helps your team quickly identify whether a user-reported issue is caused by a dependency rather than your own code.