Is Dynatrace Down?

No — Dynatrace is up

Reachable from all 8 checked regions

Average response time: 156ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://dynatrace.status.io/

Dynatrace uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

189ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 68 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

68-day clean streak

Sep 14 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ewr

121ms

DNS 105ms TCP 1ms TLS 3ms TTFB 117ms

fra

81ms

DNS 58ms TCP 1ms TLS 4ms TTFB 78ms

gru

72ms

DNS 56ms TCP 1ms TLS 4ms TTFB 68ms

iad

173ms

DNS 156ms TCP 2ms TLS 5ms TTFB 168ms

jnb

402ms

DNS 390ms TCP 0ms TLS 5ms TTFB 399ms

lax

80ms

DNS 60ms TCP 2ms TLS 7ms TTFB 74ms

lhr

135ms

DNS 116ms TCP 2ms TLS 4ms TTFB 129ms

nrt

187ms

DNS 171ms TCP 2ms TLS 4ms TTFB 182ms

What Dynatrace does

Dynatrace is an observability platform that monitors applications, infrastructure and user experience for large enterprises, combining tracing, logs, metrics and automated root cause analysis. Customer environments run as tenants on AWS, Azure or Google Cloud in one of three geographic areas, and Dynatrace Managed is a self-hosted alternative. Teams depend on it to find out that something else has broken.

What an outage looks like

Dashboards fail to load or show gaps where data should be, and alerting goes quiet, which is easy to mistake for a healthy estate. Synthetic monitors may skip executions and leave holes in availability charts. Because tenants are pinned to a cloud provider and region, colleagues on another environment see normal data throughout. The support portal, community and account management can fail independently.

What to do about it

Check status.dynatrace.com, which breaks the product into Process, Retain, Analyze and Automate capabilities for each of AWS, Azure and Google Cloud across the Americas, EMEA and Asia-Pacific, so you can find your own environment instead of reading a global banner. Scheduled maintenance is published separately. Treat gaps in monitoring data as unverified rather than as evidence that nothing went wrong underneath them.

Is it down for everyone, or just you?

If this page says Dynatrace is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Dynatrace outage FAQ

Is Dynatrace down, or just my environment?

Almost certainly just some environments. Dynatrace pins each tenant to a cloud provider and a geographic area, and its status page reports every combination of Process, Retain, Analyze and Automate against AWS, Azure and Google Cloud in the Americas, EMEA and Asia-Pacific. Find the row matching your environment before escalating, because colleagues on a different provider or region will see nothing wrong at all.

Do I lose monitoring data during a Dynatrace incident?

It depends which capability is affected, which is exactly why they are reported separately. Retain covers stored data and Process covers ingest, so an incident can interrupt collection, querying, or both. Where synthetic executions are skipped, the result is a gap rather than a recorded failure. Do not read a flat, empty chart as proof that the monitored system was healthy.

Will alerts still fire while Dynatrace is degraded?

Not reliably, and that is the risk worth planning for in advance. If ingest or analysis is affected, problems in your own systems can go unannounced, and silence looks identical to everything working. During an incident, fall back on whatever secondary signal you have: the application's own logs, a second monitoring tool, or manual checks on the services that matter most.

Does Dynatrace Managed appear on the same status page?

It is listed, but it is a different arrangement. Dynatrace Managed sits among the ecosystem services alongside the support portal, community, documentation search and account management, while the SaaS capabilities are broken out by cloud provider and region. A self-hosted deployment ultimately runs on your own infrastructure, so your cluster's health is not something the vendor page can report.

How we measure this

We request Dynatrace's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Dynatrace publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Dynatrace goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required