Dynatrace uptime
From vendor reports Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours.
64.53%free of major or critical incidents, last 30 days
64.02%free of major or critical incidents, last 90 days*
58.54%free of any incident, last 90 days
20incidents started, last 90 days
* Our archive of Dynatrace’s status page starts , so the window is shorter.
Last 90 days, by UTC day
Aug 7 (UTC day): before our archive of this status page startsAug 8 (UTC day): before our archive of this status page startsAug 9 (UTC day): before our archive of this status page startsAug 10 (UTC day): before our archive of this status page startsAug 11 (UTC day): before our archive of this status page startsAug 12 (UTC day): before our archive of this status page startsAug 13 (UTC day): before our archive of this status page startsAug 14 (UTC day): before our archive of this status page startsAug 15 (UTC day): before our archive of this status page startsAug 16 (UTC day): before our archive of this status page startsAug 17 (UTC day): before our archive of this status page startsAug 18 (UTC day): before our archive of this status page startsAug 19 (UTC day): before our archive of this status page startsAug 20 (UTC day): 2 h 50 min with a major or critical incident open, 2 h 50 min with any incident open, 1 incident startedAug 21 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 22 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 23 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 24 (UTC day): 9 h 54 min with a major or critical incident open, 9 h 54 min with any incident openAug 25 (UTC day): no vendor-reported incident openAug 26 (UTC day): no vendor-reported incident openAug 27 (UTC day): 5 h 42 min with a major or critical incident open, 5 h 42 min with any incident open, 1 incident startedAug 28 (UTC day): 24 h with a major or critical incident open, 24 h with any incident open, 1 incident startedAug 29 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 30 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 31 (UTC day): 8 h 50 min with a major or critical incident open, 8 h 50 min with any incident openSep 1 (UTC day): 12 h 6 min with a major or critical incident open, 12 h 6 min with any incident open, 1 incident startedSep 2 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openSep 3 (UTC day): 14 h 10 min with a major or critical incident open, 14 h 10 min with any incident openSep 4 (UTC day): no vendor-reported incident openSep 5 (UTC day): no vendor-reported incident openSep 6 (UTC day): no vendor-reported incident openSep 7 (UTC day): no vendor-reported incident openSep 8 (UTC day): no vendor-reported incident openSep 9 (UTC day): no vendor-reported incident openSep 10 (UTC day): 3 h 29 min with a major or critical incident open, 3 h 29 min with any incident open, 1 incident startedSep 11 (UTC day): no vendor-reported incident openSep 12 (UTC day): no vendor-reported incident openSep 13 (UTC day): no vendor-reported incident openSep 14 (UTC day): 3 h 5 min with a major or critical incident open, 3 h 5 min with any incident open, 1 incident startedSep 15 (UTC day): no vendor-reported incident openSep 16 (UTC day): 12 h 1 min with a major or critical incident open, 12 h 1 min with any incident open, 2 incidents startedSep 17 (UTC day): no vendor-reported incident openSep 18 (UTC day): no vendor-reported incident openSep 19 (UTC day): no vendor-reported incident openSep 20 (UTC day): no vendor-reported incident openSep 21 (UTC day): no vendor-reported incident openSep 22 (UTC day): no vendor-reported incident openSep 23 (UTC day): 0 min with a major or critical incident open, 1 h 37 min with any incident open, 1 incident startedSep 24 (UTC day): no vendor-reported incident openSep 25 (UTC day): 2 h 3 min with a major or critical incident open, 2 h 3 min with any incident open, 1 incident startedSep 26 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openSep 27 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openSep 28 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openSep 29 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openSep 30 (UTC day): 24 h with a major or critical incident open, 24 h with any incident open, 2 incidents startedOct 1 (UTC day): 24 h with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 2 (UTC day): 7 h 3 min with a major or critical incident open, 7 h 3 min with any incident openOct 3 (UTC day): no vendor-reported incident openOct 4 (UTC day): no vendor-reported incident openOct 5 (UTC day): no vendor-reported incident openOct 6 (UTC day): no vendor-reported incident openOct 7 (UTC day): 9 h 6 min with a major or critical incident open, 9 h 6 min with any incident open, 1 incident startedOct 8 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openOct 9 (UTC day): 7 h 17 min with a major or critical incident open, 13 h 35 min with any incident open, 1 incident startedOct 10 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 11 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openOct 12 (UTC day): 0 min with a major or critical incident open, 14 h 26 min with any incident openOct 13 (UTC day): no vendor-reported incident openOct 14 (UTC day): 6 h 22 min with a major or critical incident open, 6 h 22 min with any incident open, 1 incident startedOct 15 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openOct 16 (UTC day): 24 h with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 17 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openOct 18 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openOct 19 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openOct 20 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openOct 21 (UTC day): 20 h 15 min with a major or critical incident open, 20 h 15 min with any incident openOct 22 (UTC day): no vendor-reported incident openOct 23 (UTC day): no vendor-reported incident openOct 24 (UTC day): no vendor-reported incident openOct 25 (UTC day): no vendor-reported incident openOct 26 (UTC day): no vendor-reported incident openOct 27 (UTC day): 0 min with a major or critical incident open, 9 h 20 min with any incident open, 1 incident startedOct 28 (UTC day): 7 h 48 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 29 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openOct 30 (UTC day): 12 h 34 min with a major or critical incident open, 12 h 34 min with any incident openOct 31 (UTC day): 0 min with a major or critical incident open, 2 h 54 min with any incident open, 1 incident startedNov 1 (UTC day): no vendor-reported incident openNov 2 (UTC day): no vendor-reported incident openNov 3 (UTC day): no vendor-reported incident openNov 4 (UTC day): no vendor-reported incident open
Aug 7today
no incident minor incident minor, 6 h+ major/critical major/critical, 6 h+ before archive
Last 7 days, by hour
now
Numbers
| Window | Free of major/critical | Free of any incident | Outage time | Incident time | Incidents |
|---|---|---|---|---|---|
| Last 30 days | 64.53% | 51.03% | 10.6 days | 14.7 days | 7 |
| Last 90 days* | 64.02% | 58.54% | 27.0 days | 31.1 days | 20 |
This is what Dynatrace itself reported, so it can miss outages the vendor never posted and overstate ones where an incident was left open. Regional or single-component incidents count the same as global ones. Recomputed .
See the incidents: Dynatrace status history · last 90 days · Dynatrace status page (opens in new tab) · Markdown