CheckUpstream measured Datadog at 100.000% availability across 2829 independent checks (global · api). 31 incidents were recorded in the past 12 months; the most recent resolved 25 days ago after 49 minutes. Status signals are polled from Datadog's official Atlassian Statuspage status page, alongside independent probes and community reports. Datadog publishes 1 product-level SLA uptime commitment (up to 99.8%), and service credits must be claimed within 0 days of a breach.
90 days measured availability how this is computed
100.000%
global · api · n=2829 · p95 574ms (30d)
Share of our own checks against Datadog endpoints that returned Datadog's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 18 incidents · 88 of 90 days with none posted · 1h of declared impact
Fewer incidents in the last 30 days than 34% of 232 tracked services.
Share of each window with no impact declared by Datadog
7d
100.000%
30d
99.951%
90d
99.954%
180d
99.391%
1y
99.700%
Downtime like this can be refundable
If you're a paying Datadog customer, outages in these windows may count against Datadog's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Datadog entitlement →Does Datadog actually matter to you?
A Datadog outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 18 incidents Datadog published and resolved in the last 90 days, measured between their own start and resolution times. It describes how long Datadog takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 6, 18:51 UTC · resolved in 48m · Resolved
Aug 6, 18:51 UTC · resolved in 9m · Resolved
Jul 30, 07:44 UTC · resolved in 5m · Resolved
Jul 30, 07:44 UTC
1signal across 1 source
Synthetic probes 1
All of these are CheckUpstream's own probes. Nobody else has reported Datadog in this window, so nothing here is corroboration.
Live Datadog status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/datadog)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Datadog is currently Operational. CheckUpstream tracks Datadog in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Datadog's last resolved incident started 25 days ago and lasted 48 minutes (degraded performance).
Looking for the live "is Datadog down" view? See the Datadog Live status page.
Jul 29, 15:42 UTC · resolved in 8m · Resolved
Jun 30, 17:51 UTC · resolved in 2h 53m · Resolved
Jun 30, 10:35 UTC · resolved in 45m · Resolved
Jun 25, 23:23 UTC · resolved in 17m · Resolved
Jun 22, 21:27 UTC · resolved in 1h 17m · Resolved
Jun 18, 16:13 UTC · resolved in 27m · Resolved
Jun 16, 17:42 UTC · resolved in 58m · Resolved
Jun 12, 17:12 UTC · resolved in 2h 32m · Resolved
Jun 8, 11:05 UTC · resolved in 1h 56m · Resolved
May 16, 02:17 UTC · resolved in 1h 28m · Resolved
May 14, 18:24 UTC · resolved in 1h 25m · Resolved
Datadog's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Datadog endpoints. It is the share of checks that returned the expected response, not a figure taken from Datadog's status page.
Sign up to CheckUpstream and add Datadog to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Datadog's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.