Dynatrace incident

Log ingestion disruption on a subset of deployments

Major Resolved View vendor source →

Dynatrace experienced a major incident on May 19, 2026 affecting Dynatrace Product and Dynatrace Product (Process-AWS-americas) and 1 more component, lasting 5h 43m. The incident has been resolved; the full update timeline is below.

Started
May 19, 2026, 08:15 AM UTC
Resolved
May 19, 2026, 01:58 PM UTC
Duration
5h 43m
Detected by Pingoru
May 19, 2026, 08:15 AM UTC

Affected components

Dynatrace ProductDynatrace Product (Process-AWS-americas)Dynatrace Product (Process-AWS-emea)Dynatrace Product (Process-AWS-asia-pacific)

Update timeline

  1. investigating May 19, 2026, 08:15 AM UTC

    We are investigating an issue where log ingestion is affected on a limited number of clusters. 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.

  2. identified May 19, 2026, 08:56 AM UTC

    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.

  3. monitoring May 19, 2026, 10:21 AM UTC

    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.