All Systems Operational

Locations

Signin.dynatrace.com




Operational

Account.dynatrace.com




Operational

Cluster 1 in US East Virginia




Operational

Cluster 2 in US West Oregon




Operational

Cluster 3 in US East Virginia




Operational

Cluster 4 in EU West Ireland




Operational

Cluster 5 in APAC Southeast Sydney




Operational

Cluster 6 in US East Virginia




Operational

Cluster 7 in EU West Ireland




Operational

Cluster 8 in US East Virginia




Operational

Cluster 9 in EU West Ireland




Operational

Cluster 10 in US East Virginia




Operational

Cluster 11 in US East Virginia




Operational

Cluster 12 in APAC Southeast Sydney




Operational

Cluster 13 in EU West Ireland




Operational

Cluster 14 in US East Virginia




Operational

Cluster 15 in US East Virginia




Operational

Cluster 16 in US West Oregon




Operational

Cluster 17 in US East Virginia




Operational

Cluster 18 in US West Oregon




Operational

Cluster 19 in EU West Ireland




Operational

Cluster 20 in EU West Ireland




Operational

Cluster 21 in US East Virginia




Operational

Cluster 22 in US East Virginia




Operational

Cluster 23 in EU West Ireland




Operational

Cluster 24 in US West Oregon




Operational

Cluster 25 in US East Virginia




Operational

Cluster 26 in US East Virginia




Operational

Cluster 27 in APAC Southeast Sydney




Operational

Cluster 28 in US East Virginia




Operational

Dynatrace Synthetic Locations




Operational

Dynatrace Synthetic Back-End




Operational

Dynatrace Mission Control




Operational

Search.dynatrace.com




Operational

Website: dynatrace.com




Operational

Support.dynatrace.com




Operational

Help.dynatrace.com




Operational

Answers.dynatrace.com




Operational

External Services

AWS EC2

AWS S3

History (Last 7 days)

Incident Status

Operational


Components

Cluster 1 in US East Virginia, Cluster 2 in US West Oregon, Cluster 3 in US East Virginia, Cluster 4 in EU West Ireland, Cluster 5 in APAC Southeast Sydney, Cluster 6 in US East Virginia, Cluster 7 in EU West Ireland, Cluster 8 in US East Virginia, Cluster 9 in EU West Ireland, Cluster 10 in US East Virginia, Cluster 11 in US East Virginia, Cluster 12 in APAC Southeast Sydney, Cluster 13 in EU West Ireland, Cluster 14 in US East Virginia, Cluster 15 in US East Virginia, Cluster 16 in US West Oregon, Cluster 17 in US East Virginia, Cluster 18 in US West Oregon, Cluster 19 in EU West Ireland, Cluster 20 in EU West Ireland, Cluster 21 in US East Virginia, Cluster 22 in US East Virginia, Cluster 23 in EU West Ireland, Cluster 24 in US West Oregon, Cluster 25 in US East Virginia, Cluster 26 in US East Virginia, Cluster 27 in APAC Southeast Sydney, Cluster 28 in US East Virginia


Locations

US East - Virginia, US West - Oregon, EU West - Ireland, APAC Southeast - Sydney




December 13, 2018 1:25PM UTC
[Resolved] Incident Resolved

December 13, 2018 1:12PM UTC
[Monitoring] Fix was shipped to all Clusters. Monitoring situation

December 13, 2018 12:44PM UTC
[Identified] Fix is verified, roll out has started to all Clusters

December 13, 2018 10:56AM UTC
[Identified] The issue has been identified and a resolution is currently being implemented. The remediation steps will be rolled out during the next few hours to all affected clusters.

December 13, 2018 8:07AM UTC
[Identified] We have identified the cause of the issue and are currently investigating the impact.

December 13, 2018 7:00AM UTC
[Investigating] The Auto Tagging issue is still under investigation. We suggest as a temporary workaround to disable the auto-tagging rules until the issue can be resolved. Please note that this may affect alerting rules, thus special care need to be taken as alerting may not work effectively.

December 13, 2018 3:54AM UTC
[Investigating] Issue is still under investigation, additional updates will be provided as soon as possible. Potential impact is incorrect alert routing for alert profiles based on tags.

December 13, 2018 2:53AM UTC
[Investigating] Immediate workaround is to disable tagging rules.

December 13, 2018 2:51AM UTC
[Investigating] Auto-tagging rule issues have been identified, currently under investigation. Entities may have improper tags applied. Potential impact may be false alerting for those rules based off tags.