Skip to content

Outage tracker / Datadog

Is Datadog down?

I'm having a problem

Vendor reports no incidentWhat Datadog reports

Datadog reports no incident on its status page.

As of the last successful poll, 2026-10-22 21:50 UTC.

Datadog's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 2 minutes ago

Our checks of Datadog pass from all 10 regions we check.

As of Oct 22, 2026, 9:50 PM UTC, RealUptime's checks of Datadog passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 22, 2026, 9:50 PM UTC
US-East601 msChecks passing
US-West1049 msChecks passing
Europe630 msChecks passing
Asia-Pacific2322 msChecks passing
US-Central398 msChecks passing
Canada544 msChecks passing
UK795 msChecks passing
Southeast Asia2203 msChecks passing
Australia1192 msChecks passing
South America993 msChecks passing
their status pagetheir claim, not our reading

Datadog reports: All systems operational (“All Systems Operational”)

from Datadog's own status page, checked Oct 22, 2026, 9:22 PM UTC
Datadog's own status page shows no incident, and our checks of Datadog pass right now.

Datadog's own component breakdown, as they publish it

  • APMOperational
  • App BuilderOperational
  • Application Security ManagementOperational
  • Application Vulnerability ManagementOperational
  • Audit TrailOperational
  • Bits AIOperational
  • CI VisibilityOperational
  • Cloud Cost ManagementOperational
  • Cloud Network MonitoringOperational
  • Cloud Security ManagementOperational
  • Cloud SIEMOperational
  • Code CoverageOperational
  • Code SecurityOperational
  • Container RegistryOperational
  • Continuous ProfilerOperational
  • Database MonitoringOperational
  • Data Jobs MonitoringOperational
  • Data Streams MonitoringOperational
  • Error TrackingOperational
  • Event ManagementOperational
  • Incident ResponseOperational
  • LLM ObservabilityOperational
  • Log ManagementOperational
  • Metrics and Infra MonitoringOperational
  • Mobile ApplicationOperational
  • MonitorsOperational
  • NDMOperational
  • Observability PipelinesOperational
  • Package RepositoriesOperational
  • Product AnalyticsOperational
  • RUMOperational
  • Sensitive Data ScannerOperational
  • ServerlessOperational
  • SyntheticsOperational
  • Test OptimizationOperational
  • Universal Service MonitoringOperational
  • Web ApplicationOperational
  • Workflow AutomationOperational
  • Workload ProtectionOperational
  • www.datadoghq.comOperational

These are Datadog's components, named and scored by Datadog. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Datadog's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Datadog response time, by region

US-East
1.1sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 498ms2026-09-24 UTC: p95 531ms2026-09-25 UTC: p95 618ms2026-09-26 UTC: p95 534ms2026-09-27 UTC: p95 533ms2026-09-28 UTC: p95 502ms2026-09-29 UTC: p95 621ms2026-09-30 UTC: p95 562ms2026-10-01 UTC: p95 484ms2026-10-02 UTC: p95 728ms2026-10-03 UTC: p95 746ms2026-10-04 UTC: p95 695ms2026-10-05 UTC: p95 624ms2026-10-06 UTC: p95 689ms2026-10-07 UTC: p95 688ms2026-10-08 UTC: p95 681ms2026-10-09 UTC: p95 661ms2026-10-10 UTC: p95 631ms2026-10-11 UTC: p95 662ms2026-10-12 UTC: p95 662ms2026-10-13 UTC: p95 687ms2026-10-14 UTC: p95 621ms2026-10-15 UTC: p95 672ms2026-10-16 UTC: p95 692ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.1s
Sep 23Oct 7Oct 22
US-West
1.5sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 623ms2026-09-24 UTC: p95 544ms2026-09-25 UTC: p95 677ms2026-09-26 UTC: p95 721ms2026-09-27 UTC: p95 638ms2026-09-28 UTC: p95 706ms2026-09-29 UTC: p95 548ms2026-09-30 UTC: p95 553ms2026-10-01 UTC: p95 603ms2026-10-02 UTC: p95 614ms2026-10-03 UTC: p95 701ms2026-10-04 UTC: p95 683ms2026-10-05 UTC: p95 726ms2026-10-06 UTC: p95 685ms2026-10-07 UTC: p95 682ms2026-10-08 UTC: p95 636ms2026-10-09 UTC: p95 711ms2026-10-10 UTC: p95 649ms2026-10-11 UTC: p95 760ms2026-10-12 UTC: p95 639ms2026-10-13 UTC: p95 746ms2026-10-14 UTC: p95 713ms2026-10-15 UTC: p95 782ms2026-10-16 UTC: p95 742ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.5s
Sep 23Oct 7Oct 22
Europe
949msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 607ms2026-09-24 UTC: p95 576ms2026-09-25 UTC: p95 924ms2026-09-26 UTC: p95 905ms2026-09-27 UTC: p95 852ms2026-09-28 UTC: p95 831ms2026-09-29 UTC: p95 577ms2026-09-30 UTC: p95 588ms2026-10-01 UTC: p95 629ms2026-10-02 UTC: p95 578ms2026-10-03 UTC: p95 684ms2026-10-04 UTC: p95 589ms2026-10-05 UTC: p95 574ms2026-10-06 UTC: p95 598ms2026-10-07 UTC: p95 702ms2026-10-08 UTC: p95 724ms2026-10-09 UTC: p95 634ms2026-10-10 UTC: p95 693ms2026-10-11 UTC: p95 660ms2026-10-12 UTC: p95 684ms2026-10-13 UTC: p95 622ms2026-10-14 UTC: p95 621ms2026-10-15 UTC: p95 592ms2026-10-16 UTC: p95 623ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 949ms
Sep 23Oct 7Oct 22
Asia-Pacific
2.3sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.5s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 2.4s2026-10-22 UTC: p95 2.3s
Sep 23Oct 7Oct 22
US-Central
536msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 393ms2026-09-24 UTC: p95 413ms2026-09-25 UTC: p95 366ms2026-09-26 UTC: p95 443ms2026-09-27 UTC: p95 532ms2026-09-28 UTC: p95 522ms2026-09-29 UTC: p95 491ms2026-09-30 UTC: p95 455ms2026-10-01 UTC: p95 303ms2026-10-02 UTC: p95 313ms2026-10-03 UTC: p95 397ms2026-10-04 UTC: p95 444ms2026-10-05 UTC: p95 431ms2026-10-06 UTC: p95 463ms2026-10-07 UTC: p95 375ms2026-10-08 UTC: p95 391ms2026-10-09 UTC: p95 402ms2026-10-10 UTC: p95 299ms2026-10-11 UTC: p95 373ms2026-10-12 UTC: p95 412ms2026-10-13 UTC: p95 412ms2026-10-14 UTC: p95 456ms2026-10-15 UTC: p95 429ms2026-10-16 UTC: p95 486ms2026-10-17 UTC: p95 532ms2026-10-18 UTC: p95 537ms2026-10-19 UTC: p95 483ms2026-10-20 UTC: p95 614ms2026-10-21 UTC: p95 616ms2026-10-22 UTC: p95 536ms
Sep 23Oct 7Oct 22
Canada
653msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 618ms2026-09-24 UTC: p95 657ms2026-09-25 UTC: p95 690ms2026-09-26 UTC: p95 691ms2026-09-27 UTC: p95 702ms2026-09-28 UTC: p95 711ms2026-09-29 UTC: p95 692ms2026-09-30 UTC: p95 744ms2026-10-01 UTC: p95 592ms2026-10-02 UTC: p95 674ms2026-10-03 UTC: p95 788ms2026-10-04 UTC: p95 717ms2026-10-05 UTC: p95 638ms2026-10-06 UTC: p95 650ms2026-10-07 UTC: p95 540ms2026-10-08 UTC: p95 581ms2026-10-09 UTC: p95 609ms2026-10-10 UTC: p95 554ms2026-10-11 UTC: p95 513ms2026-10-12 UTC: p95 560ms2026-10-13 UTC: p95 511ms2026-10-14 UTC: p95 633ms2026-10-15 UTC: p95 613ms2026-10-16 UTC: p95 680ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 653ms
Sep 23Oct 7Oct 22
UK
1.0sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 478ms2026-09-24 UTC: p95 503ms2026-09-25 UTC: p95 447ms2026-09-26 UTC: p95 502ms2026-09-27 UTC: p95 463ms2026-09-28 UTC: p95 450ms2026-09-29 UTC: p95 491ms2026-09-30 UTC: p95 474ms2026-10-01 UTC: p95 441ms2026-10-02 UTC: p95 521ms2026-10-03 UTC: p95 459ms2026-10-04 UTC: p95 426ms2026-10-05 UTC: p95 402ms2026-10-06 UTC: p95 561ms2026-10-07 UTC: p95 543ms2026-10-08 UTC: p95 531ms2026-10-09 UTC: p95 533ms2026-10-10 UTC: p95 593ms2026-10-11 UTC: p95 582ms2026-10-12 UTC: p95 612ms2026-10-13 UTC: p95 547ms2026-10-14 UTC: p95 453ms2026-10-15 UTC: p95 456ms2026-10-16 UTC: p95 414ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.0s
Sep 23Oct 7Oct 22
Southeast Asia
2.4sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 3.0s2026-09-24 UTC: p95 2.6s2026-09-25 UTC: p95 2.2s2026-09-26 UTC: p95 2.1s2026-09-27 UTC: p95 2.0s2026-09-28 UTC: p95 2.2s2026-09-29 UTC: p95 2.1s2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 1.8s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.8s2026-10-05 UTC: p95 1.9s2026-10-06 UTC: p95 1.8s2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 1.8s2026-10-11 UTC: p95 2.0s2026-10-12 UTC: p95 1.9s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.9s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 2.4s2026-10-22 UTC: p95 2.4s
Sep 23Oct 7Oct 22
Australia
1.8sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.8s
Sep 23Oct 7Oct 22
South America
3.0sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 988ms2026-09-24 UTC: p95 898ms2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.6s2026-10-21 UTC: p95 2.6s2026-10-22 UTC: p95 3.0s
Sep 23Oct 7Oct 22

Check your own site while you wait on Datadog

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Datadog. It cannot diagnose Datadog's own systems.

What we measured, function by function

Datadog answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Datadog reports an incident on its status page, and again when it reports it resolved.

Get an email when Datadog reports an incident

Email me when Datadog reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Datadog's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 601msstatus code: 403checked: Oct 22, 2026, 9:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Datadog normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1049msstatus code: 403checked: Oct 22, 2026, 9:47 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Datadog normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 398msstatus code: 403checked: Oct 22, 2026, 9:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Datadog normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 544msstatus code: 403checked: Oct 22, 2026, 9:36 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Datadog normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 993msstatus code: 403checked: Oct 22, 2026, 9:33 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Datadog normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 630msstatus code: 403checked: Oct 22, 2026, 9:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Datadog normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 795msstatus code: 403checked: Oct 22, 2026, 9:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Datadog normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2322msstatus code: 403checked: Oct 22, 2026, 9:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Datadog normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 2203msstatus code: 403checked: Oct 22, 2026, 9:39 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Datadog normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1192msstatus code: 403checked: Oct 22, 2026, 9:43 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Datadog normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Datadog, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Datadog yet, which is not evidence that nothing is wrong.

Recent probe events

Delayed RUM sessions, 2h 17mdeclared on their status page2026-10-02
Delayed Events, 48mdeclared on their status page2026-09-30
Users are unable to acknowledge, escalate, or resolve On-Call Pages, 27mdeclared on their status page2026-09-25
Delayed Monitors Notifications, 46mdeclared on their status page2026-09-21
Delayed events triggered by emails, 1h 36mdeclared on their status page2026-09-20
Delayed CICD Optimization, Code Coverage, Code Security, and DORA data, 5h 41mdeclared on their status page2026-09-03
Delayed DBM Monitor Evaluation, 17mdeclared on their status page2026-09-02
Delayed Processes data, 46mdeclared on their status page2026-08-06

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Datadog since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Datadog covering any window you pick, with our check readings and Datadog's own claim at the time, side by side.

Full check history for Datadog: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Datadog uptime by RealUptime's checksLive, from this page's own readings.
[![Datadog uptime by RealUptime's checks](https://realuptime.io/outages/datadog/badge.svg?days=30)](https://realuptime.io/outages/datadog)
<a href="https://realuptime.io/outages/datadog"><img src="https://realuptime.io/outages/datadog/badge.svg?days=30" alt="Datadog uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Datadog down?", https://realuptime.io/outages/datadog. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional: live API
https://api.datadoghq.com/api/v1/validate
secondary
https://status.datadoghq.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.datadoghq.com

RealUptime is not affiliated with Datadog; the name identifies what we checked, and nothing here speaks for Datadog's own team. We send a single web request to Datadog from 10 regions on our own schedule and time the response. We do not see inside Datadog's systems, do not use an account or real transaction, and are not the same signal Datadog's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Datadog is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.