← Back to New Relic History
major✓ Resolved

Data Irregularities in the EU Region

New Relic•
Status
resolved
Duration
45m
Updates
6
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
Between 18:28 UTC and 18:58 UTC Tuesday March 18, 2025, some customers in the EU region may have experienced errors when sending data to New Relic, issues in viewing data in real time, and delayed or missing alert notifications related to real time data. We have investigated and resolved this service interruption and impacted services have returned to normal operations.
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are investigating an issue with data ingest for various data types. Some customers in the EU region may experience errors when sending data to New Relic, issues in viewing data in real time, and delayed or missing alert notifications related to real time data.
monitoring
We are investigating an issue with data ingest for various data types. Some customers in the EU region may experience errors when sending data to New Relic, issues in viewing data in real time, and delayed or missing alert notifications related to real time data.
investigating
We are investigating an issue with data ingest for various data types. Some customers in the EU region may experience errors when sending data to New Relic, issues in viewing data in real time, and delayed or missing alert notifications related to real time data.

📊 TECHNICAL DETAILS

Internal ID
524e7651-2350-4e75-9716-2362c474a415
External ID
739dq850pym1
🕐 Started
🔄 Last Updated
✓ Resolved
MAJOR
Impact Level
45m
Total Duration
6
Status Updates
Affected Components
APM Agent : EuropeBrowser Agent : EuropeEvent API : EuropeIncident Intelligence API : EuropeInfrastructure Agent : EuropeLog API : EuropeMetric API : EuropeMobile Agent : EuropeOTLP API : EuropeTrace API : EuropeSynthetics : Europe
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed