New AI Incident Response, Multi-Region Agents, and Custom-Domain Status Pages — May 2026
Monitor Features overview Vendor status Uptime & synthetic checks Certificate lifecycle Operate Incident management Live demo
By goal Replace your stack Why ServiceAlert Competitor comparisons Alternatives directory By signal Reliability hub   · Uptime rankings   · SLA compliance Outage map
Services
Check & scan SSL security grader Status checker DNS lookup Response time WHOIS lookup Calculators SLA calculator Downtime calculator Embed Status badges All tools →
Pricing
Guides Help center Uptime monitoring RUM & analytics Teams & shared monitors Developer API reference Status badges Learn Blog Outage reports FAQ Changelog
Dashboard

Dynatrace Outage History

Uptime record, past incidents, and downtime history for Dynatrace.

Checking current status...
82.4% uptime over 91 days
99.9% ✗ 99.5% ✗ 99% ✗ 95% ✗

90-Day Trend

Feb 25May 25

Monthly Uptime

Month Uptime Days Tracked Days with Issues
May 2026 40% 25 15
April 2026 96.7% 30 1
March 2026 100% 31 0
February 2026 100% 5 0

Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.

Daily Status (Last 91 Days)

Feb 24 Today
Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

May 2026
OneAgent version 1.337 may impact IBM MQ message processing for .NET applications
minor

Started: May 20, 1:44 PM

resolved
We are currently investigating an issue related to OneAgent for .NET version 1.337, which is impacting message processing in environments using IBM MQ. As a result, some downstream applications are unable to properly process incoming messages, which may lead to disruptions in normal business operations. Our team is actively working to identify and resolve the problem, and we will provide updates as more information becomes available. At the time we recommend not to update to 1.337 if yo...
May 20, 1:44 PM
Log ingestion disruption on a subset of deployments
minor

Started: May 19, 8:15 AM

investigating
We can confirm that log ingestion has been fully restored across the affected deployments. We will monitor the stability over the next couple of hours before resolving this incident. If you notice any issues with log ingestion, please raise a Support ticket and our team will assist you promptly. Thank you for your patience and understanding while we worked to resolve this issue.
May 19, 10:21 AM
investigating
We have identified the issue that is impacting log ingestion on a limited number of deployments. Remediation and impact analysis are currently in progress, we will update as new information becomes available.
May 19, 8:56 AM
investigating
We are investigating an issue where log ingestion is affected on a limited number of deployments. Early indications suggest that some log records are not being ingested as expected. The scope and impact are still being assessed. We apologize for the inconvenience and will provide updates as more information becomes available.
May 19, 8:15 AM
Anomaly detection executions are degraded due to increased response times
minor

Started: May 13, 12:45 PM

investigating
We have deployed a mitigation and are observing improvements across affected environments. Our teams will continue to closely monitor stability over the next several hours. We will provide additional updates if there are any changes. We sincerely apologize for the inconvenience and appreciate your patience.
May 13, 3:26 PM
monitoring
We have identified the root cause of the Anomaly Detection execution degradation. Mitigation work is currently in progress to restore normal execution behavior. We will continue to provide updates as we progress in remediating this issue.
May 13, 1:41 PM
monitoring
We are currently investigating an issue causing a degradation in Anomaly Detection executions. This may result in Anomaly Detectors not running as expected or being temporarily backed off. The behavior is linked to increased response times in a dependent service, and our teams are actively investigating the situation. We apologize for the inconvenience and will provide updates as more information becomes available.
May 13, 12:45 PM
Potential delay in spans, logs and user events ingestion in AWS US east region
minor

Started: May 13, 2:27 AM

investigating
We are seeing positive progress with data ingestion, and many tenants are no longer experiencing impact. However, to ensure full resolution of this issue, our team will continue monitoring the remaining affected tenants as they work through the backlog. We sincerely apologize for the inconvenience and appreciate your continued patience as we complete our remediation efforts. Please check here for updates.
May 14, 6:08 PM
monitoring
We can confirm that new and ongoing data ingestion has been restored. Our teams will continue to monitor the backlog as data processing catches up. Because this process will take some time to complete, please check back here tomorrow for an update. We apologize for the inconvenience and appreciate your patience as we continue working towards a resolution.
May 13, 7:11 PM
monitoring
Recovery actions remain in place and the platform is operating with restored real‑time data processing. New incoming data is being processed normally, while previously queued data continues to catch up. As a result, some data types may still appear with delay until the backlog is fully cleared. The situation is improving and our teams continue to monitor recovery closely. We will revert to normal status once ingest backlog processing has fully completed. Thank you for your patience.
May 13, 9:18 AM
monitoring
We continue to see positive progress following recovery actions taken earlier. The platform is actively processing previously delayed ingest, and system buffers are steadily draining. While some customers may still observe delayed real‑time data, overall processing is stabilizing as recovery continues. Our teams are actively monitoring the situation to ensure full normalization. We appreciate your patience and will provide further updates as progress continues.
May 13, 6:50 AM
monitoring
We have identified the root cause of this issue and implemented recovery actions. The platform is currently catching up on previously delayed ingest, and we expect some additional time to fully normalize real‑time observability. We apologize for the inconvenience and appreciate your patience. Please reach out to support team in case you have any further questions.
May 13, 3:26 AM
monitoring
We are currently investigating an issue causing ingestion delay in spans, logs and user events in AWS US east region. Our teams are actively analyzing the situation and working to restore normal service levels as quickly as possible. We apologize for the inconvenience and recommend monitoring this status page for further updates.
May 13, 2:27 AM
AWS operational issue may impact some US deployments
minor

Started: May 8, 1:01 AM

investigating
AWS has resolved the operational issue that was delaying data ingestion for some customers in the US‑EAST‑1 region. Normal services have resumed and we are actively monitoring performance to ensure all services are stabilized. If you experience any issues with data ingestion, please open a support ticket, and our team will be ready to assist you promptly. Thank you for your patience and understanding while we work to resolve this issue.
May 11, 3:03 AM
investigating
Data ingestion has been restored across the affected environments, and systems are operating normally. We will continue to closely monitor the situation as AWS works toward fully resolving their incident. If you continue to experience any issues with data ingestion, please open a Support ticket, and our team will be ready to assist you promptly. Thank you for your patience and understanding while we worked to mitigate this issue.
May 8, 7:05 PM
monitoring
We have identified that a limited set of metrics, logs, events, and user sessions are still experiencing ingestion issues, impacting a subset of customers. We are actively working on additional mitigation measures. We apologize for the inconvenience and recommend monitoring the Dynatrace Status page for further updates.
May 8, 2:35 PM
monitoring
Data ingestion has largely recovered and logs and metrics are ingesting normally. Some customers with high ingest volume may still observe delayed processing for spans, while other customers are seeing normal ingest across all data types. Additional recovery actions have been applied, and the remaining impact is limited to span processing as the system continues to catch up in approximately 2 hours. We are closely monitoring progress. We apologize for the inconvenience and recommend mon...
May 8, 12:11 PM
monitoring
Recovery actions have been completed and data ingestion is now progressing. The platform is currently catching up on previously delayed ingest, and as a result, real‑time observability may take additional time to fully normalize. Additional capacity adjustments are being applied to accelerate processing and support faster recovery of data visibility. We continue to closely monitor the situation. We apologize for the inconvenience and recommend monitoring the Dynatrace Status page for ...
May 8, 11:02 AM
monitoring
We are observing broad data ingestion issues that may result in missing or delayed data for customers. Intermittent API ingest requests may also return 500 errors due to elevated memory pressure on ActiveGates. The impact is currently observed in the US‑EAST‑1 region. We are actively working toward full stabilization and continue to closely monitor the situation. We apologize for the inconvenience and recommend monitoring the Dynatrace Status page for further updates.
May 8, 9:27 AM
monitoring
We've observed significant improvements following the mitigation from AWS. We are actively monitoring this incident and will update here as the situation changes.
May 8, 2:13 AM
monitoring
We've identified an issue of degradated data ingestion due to the AWS Amazon Elastic Compute Cloud (N. Virginia) operational issue in a single Availability Zone (use1-az4) in the US-EAST-1 Region. More details can be found: https://health.aws.amazon.com/health/status We are actively monitoring this incident and will update here as the situation changes.
May 8, 1:01 AM
Multiple Google Synthetic Locations are not executing tests

Started: May 7, 3:39 PM

resolved
We are investigating Synthetic locations running in the Google Cloud locations that are not currently executing tests. We will follow up here with updates as they become available.
May 7, 3:39 PM
April 2026
Real User Monitoring on Grail sessions processing in OpenPipeline are impacted

Started: Apr 21, 2:34 PM

resolved
We are investigating an issue with User Sessions processing through OpenPipeline.  The data is being ingested, but post processing is affected. We will update with more information here.
Apr 21, 2:34 PM
View live status for Dynatrace Browse all services