Looking for an update now? Check the current status, or follow Dynatrace for future changes.
Building verified history20 of 24 verified daily observations collected. A percentage will appear after the minimum coverage threshold is met.
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Recorded Daily Status (Last 54 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.
Legacy Incident Archive
25 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
May 2026
Anomaly detection executions are degraded due to increased response times
minorSource not attested
Last archived state: investigating
View archived record details
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.
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.
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.
Potential delay in spans, logs and user events ingestion in AWS US east region
minorSource not attested
Last archived state: investigating
View archived record details
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.
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.
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.
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.
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.
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.
AWS operational issue may impact some US deployments
minorSource not attested
Last archived state: investigating
View archived record details
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.
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.
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.
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...
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 ...
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.
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.
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.
Multiple Google Synthetic Locations are not executing tests
Source not attested
Last archived state: resolved
View archived record details
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.
April 2026
Real User Monitoring on Grail sessions processing in OpenPipeline are impacted
Source not attested
Last archived state: resolved
View archived record details
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.
