Skip to content

Outage tracker

Datadog: the full evidence record

The last 24 hours in detail, 48 days of measured availability, a 12-month summary, our own incident log, Datadog's declared record, and how the two compare.

← Back to Datadog's live status

We started measuring Datadog on August 20, 2026, which is 48 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me the next time we see Datadog go down

Measured by our own probes from ten regions, not Datadog's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Datadog's own status page declared. Below it, any public chatter we saw about Datadog and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Datadog's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Datadog in the last 24 hours, which is not evidence that nothing is wrong.
Datadog's status pageNo incident declared in the last 24 hours.

Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is Datadog's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Datadog next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East99.98%6601
US-West100.00%6591
Europe100.00%6524
Asia-Pacific100.00%6279
US-Central100.00%2398
Canada99.96%2398
UK100.00%2395
Southeast Asia100.00%2365
Australia99.96%2362
South America99.96%2386

Monthly summary

Tracking Datadog since Aug 20, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 20, 2026100%00 min
Sep 2026100%00 min
Oct 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for Datadog: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Datadog's own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for Datadog in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: Datadog's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

No outages detected for Datadog since we started measuring it on August 20, 2026. We show nothing from before that date.

Their declared record

Datadog's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.

Delayed RUM sessionsAll systems operational
Oct 2, 2026, 12:46 PM UTC to Oct 2, 2026, 3:03 PM UTC (2h 17m)resolved
their latest update (Oct 2, 2026, 3:03 PM UTC): This incident has been resolved.
Delayed EventsMinor incident
Sep 30, 2026, 6:02 PM UTC to Sep 30, 2026, 6:51 PM UTC (48 min)resolved
their latest update (Sep 30, 2026, 6:51 PM UTC): The issue is now resolved.
Users are unable to acknowledge, escalate, or resolve On-Call PagesMinor incident
Sep 25, 2026, 3:11 PM UTC to Sep 25, 2026, 3:38 PM UTC (27 min)resolved
their latest update (Sep 25, 2026, 3:38 PM UTC): The issue is now resolved.
Delayed Monitors NotificationsMinor incident
Sep 21, 2026, 9:44 AM UTC to Sep 21, 2026, 10:30 AM UTC (46 min)resolved
their latest update (Sep 21, 2026, 10:30 AM UTC): The issue is now resolved.
Delayed events triggered by emailsMinor incident
Sep 20, 2026, 5:17 AM UTC to Sep 20, 2026, 6:53 AM UTC (1h 36m)resolved
their latest update (Sep 20, 2026, 6:53 AM UTC): The issue is now resolved. All events from emails are being timely processed and we went through the backfill.
Delayed CICD Optimization, Code Coverage, Code Security, and DORA dataMinor incident
Sep 3, 2026, 5:20 PM UTC to Sep 3, 2026, 11:01 PM UTC (5h 41m)resolved
their latest update (Sep 3, 2026, 11:01 PM UTC): The issue is now resolved.
Delayed DBM Monitor EvaluationMinor incident
Sep 2, 2026, 1:07 AM UTC to Sep 2, 2026, 1:24 AM UTC (17 min)resolved
their latest update (Sep 2, 2026, 1:24 AM UTC): The issue is now resolved.
Delayed Processes dataMinor incident
Aug 6, 2026, 6:51 PM UTC to Aug 6, 2026, 7:37 PM UTC (46 min)resolved
their latest update (Aug 6, 2026, 7:37 PM UTC): This incident has been resolved.
Delayed Evaluation of Service Check monitorsMinor incident
Jul 30, 2026, 7:44 AM UTC to Jul 30, 2026, 8:27 AM UTC (43 min)resolved
their latest update (Jul 30, 2026, 8:27 AM UTC): This incident has been resolved.
Real user monitoring, distribution and custom processes metrics delayedMinor incident
Jul 29, 2026, 3:41 PM UTC to Jul 29, 2026, 5:28 PM UTC (1h 46m)resolved
their latest update (Jul 29, 2026, 5:28 PM UTC): This incident has been resolved.

Showing the 10 most recent of 57 incidents Datadog has declared in the history we hold.

These entries are Datadog's own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

The scorecard

How Datadog's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.

We started recording Datadog's own status page on August 20, 2026, 46 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.

We have not measured an outage for Datadog since we started recording their status page, so there is nothing to compare. That is a short measurement window, not a track record.

Datadog decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If Datadog believes a figure here is wrong, we publish corrections as prominently as the original.

Full detail on what a probe does and does not prove is in the methodology page.