Status Health Check Dashboard

loading…
What this dashboard shows & how to use it

Heroku

App health from Datadog logs/metrics: HTTP 4XX/5XX error volume, overall success rate, and top error paths/services β€” plus a Domains β†’ Heroku Apps lookup (via Heroku's own API, not Datadog) to find which app any domain belongs to. Click a domain row for its app/team/region/stack and a link to both URLs.

Cloudflare

Edge traffic and security from Datadog: requests, unique visitors, response time, cache hit rate, and threats by domain, country, and status code. Threats Over Time shows which countries made up a spike on hover; the other toplists open a quick rank/share popup.

UptimeRobot

External synthetic checks β€” whether each monitored URL is actually reachable from outside, independent of Datadog. Click a monitor for its uptime history and recent checks.

GitHub

Open PR and commit activity across the org β€” which repos/authors have the most open work, and the oldest PRs still waiting. Click a PR row for its description, labels, and comments; the by-repo/by-author charts link out to a filtered GitHub search.

App Availability

A live embed of the team's Confluence page β€” deployment status per app, straight from the source doc.

  • Hover any chart line for exact values at that point in time (drag on a phone).
  • β€Ί marks a row that opens a detail card right here; β†— marks one that opens another site instead (GitHub, mostly).
  • Look back (below) reruns the Heroku/Cloudflare charts over a different window, from 1h up to 1mo.
  • Search under a Heroku/Cloudflare chart to add a domain or service that isn't shown by default.
  • Domains β†’ Heroku Apps (Heroku tab, below the charts) is a separate search β€” instantly filters the full domain list, not tied to a chart or time window.
Look back:
Data pulled from the same queries as the Heroku Dashboard in Datadog, charted here directly.

Domains β†’ Heroku Apps

Data pulled from the same queries as the Cloudflare - Overview (GH) dashboard in Datadog, charted here directly.
Pulled from UptimeRobot's API on its own background loop β€” refreshed roughly every 5–10 minutes (fetching all ~945 monitors takes anywhere from under a minute to several minutes, depending on UptimeRobot's own response latency). β€”

Monitors

Pulled from GitHub's Search API, refreshed every 5 minutes alongside the summary panels above β€” not on the fast per-chart loop, to stay well under GitHub's search rate limit. β€”
Release team activity β€” the second merge (intermediate branch β†’ main/master/production/prod) is the actual release, and the team opens and merges that PR themselves.

Awaiting Release Review from Release Team

Released Today

Recent Releases by Release Team

Releases by Repo
Open PRs by Repo
Open PRs by Author
Commits by Repo
Commits by Author

Oldest Open PRs

Embedded from Confluence, refreshed every 5 minutes.