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, 2026 2:35PM UTC
IDENTIFIED
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, 2026 12:11PM UTC
IDENTIFIED
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 monitoring the Dynatrace Status page for further updates.
May 8, 2026 11:02AM UTC
IDENTIFIED
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 further updates.
May 8, 2026 9:27AM UTC
IDENTIFIED
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, 2026 2:13AM UTC
IDENTIFIED
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, 2026 1:01AM UTC
IDENTIFIED
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.
You’ll receive a confirmation email after submitting your email address.
status.io is used to provide this service and by subscribing to receive notifications, you are agreeing to share your contact information with status.io (status.io/privacy).
Subscribe to receive status updates in Microsoft Teams
