Snapshot 14914
Raw (normalized text)
Scripts and page chrome removed; this is what change detection compares.
{
"pages": [
{
"end_time": "2026-09-30T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "897ql6915l7m",
"impact": "major",
"message": "Between 19:24 UTC and 22:04 UTC, a subset of customers in the US region may have experienced delayed data in queries, charts, and dashboards as well as delayed, missing or suppressed alert notifications for related data. We have investigated and resolved this service interruption and impacted services have returned to normal operations.",
"name": "Data Irregularities for US region",
"timestamp": "Sep \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e19:57\u003c/var\u003e - \u003cvar data-var='time'\u003e22:33\u003c/var\u003e UTC"
},
{
"code": "gmqr6x0n92x8",
"impact": "none",
"message": "Between 01:10 UTC and 03:33 UTC on September 25th, some customers in the US, EU, and JP regions may have experienced intermittent UI errors while navigating the New Relic UI. Data ingest and alert notifications were not impacted. We have resolved this issue and impacted services have returned to normal operations.",
"name": "New Relic UI errors",
"timestamp": "Sep \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e03:56\u003c/var\u003e - \u003cvar data-var='time'\u003e03:56\u003c/var\u003e UTC"
},
{
"code": "6292c7c1fyyr",
"impact": "none",
"message": "All in-app services have returned to normal operations. Please reach out to New Relic support for assistance with any issues.",
"name": "Salesforce Service Disruption",
"timestamp": "Sep \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e10:08\u003c/var\u003e - \u003cvar data-var='time'\u003e15:40\u003c/var\u003e UTC"
},
{
"code": "cgnttjznkqtf",
"impact": "none",
"message": "Between 23:06 UTC and 23:16 UTC, some customers in the EU region may have experienced errors when sending metric timeslice data to New Relic, issues in viewing metric timeslice data in real time, and delayed or missing alert notifications related to real time data. Impacted data may not be recoverable.",
"name": "Data Irregularities for EU Region",
"timestamp": "Sep \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e00:14\u003c/var\u003e - \u003cvar data-var='time'\u003e00:14\u003c/var\u003e UTC"
}
],
"name": "September",
"year": 2026
},
{
"incidents": [
{
"code": "7qgzmv42jp2s",
"impact": "minor",
"message": "Between 08:13 and 9:30 UTC on August 3rd, customers in the EU and US regions may have experienced an issue when trying to load the Alerts and Issues page in the New Relic UI. The issue is now resolved, and the impacted services have returned to normal service. Please close and re-open the Alerts page to resolve the issue.",
"name": "Issues loading Alerts and Activity page",
"timestamp": "Aug \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e09:58\u003c/var\u003e - \u003cvar data-var='time'\u003e10:15\u003c/var\u003e UTC"
}
],
"name": "August",
"year": 2026
},
{
"incidents": [
{
"code": "c1zg3xk8wcc6",
"impact": "none",
"message": "Between 15:00 UTC on July 14th and 10:00 UTC on July 17th, we experienced an issue where some customers experienced authorization issues when attempting to create, read or update E2M (Events-2-Metrics) rules in the US, EU and JP regions. This was due to a recent change we have made to our authorization endpoints. These endpoints now require S2S authentication which has caused requests to our E2M (Events-2-Metrics) to fail. Our teams have rolled back these changes until a permanent fix can be put in place. The issue is now resolved, and the impacted services have returned to normal service.",
"name": "E2M (Events-2-Metrics) authorization issues",
"timestamp": "Jul \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e10:21\u003c/var\u003e - \u003cvar data-var='time'\u003e10:21\u003c/var\u003e UTC"
},
{
"code": "7xj7zxwdvlhy",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Scheduled Maintenance for the US \u0026 EU Regions - July 11th and July 18th, 2026",
"timestamp": "Jul \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e04:00\u003c/var\u003e - \u003cvar data-var='time'\u003e06:00\u003c/var\u003e UTC"
},
{
"code": "xhp2sg7sv3xl",
"impact": "none",
"message": "Between 07:20 and 08:12 UTC on July 6th, we experienced an issue where some customers in the EU region may have experienced a delay of entity relationships appearing and refreshing in the New Relic platform. The issue is now resolved and the impacted services have returned to normal service.",
"name": "Delay of Entity Relationship Data",
"timestamp": "Jul \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e08:23\u003c/var\u003e - \u003cvar data-var='time'\u003e08:23\u003c/var\u003e UTC"
}
],
"name": "July",
"year": 2026
}
],
"start_time": "2026-07-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2026-06-30T23:59:59Z",
"months": [
{
"incidents": [],
"name": "June",
"year": 2026
},
{
"incidents": [
{
"code": "pnfchwtft08w",
"impact": "none",
"message": "Between 10:30 UTC and 13:32 UTC on May 16th, some customers in the US and EU regions may have experienced delayed data in queries, charts, and dashboards as well as delayed, missing, or false alert notifications for impacted data related to a service interruption involving a 3rd party cloud provider. The cloud provider resolved the service interruption and impacted services have returned to normal operations.",
"name": "Alerts and Data Irregularities - US and EU region",
"timestamp": "May \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e16:25\u003c/var\u003e - \u003cvar data-var='time'\u003e16:25\u003c/var\u003e UTC"
},
{
"code": "qyqpdvncpw9t",
"impact": "major",
"message": "Between 22:30 UTC on May 14th and 01:00 UTC on May 15th, 2026, some customers in the US region may have experienced issues loading different pages in the New Relic UI. Some customers may have also experienced delayed data in queries, charts, and dashboards. Data ingest and alerts were not impacted.\n\nWe resolved this issue and the above services have returned to normal operation.",
"name": "UI and Data Irregularities - US Region",
"timestamp": "May \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e00:06\u003c/var\u003e - \u003cvar data-var='time'\u003e01:45\u003c/var\u003e UTC"
}
],
"name": "May",
"year": 2026
},
{
"incidents": [
{
"code": "mgly7jkjkmkr",
"impact": "minor",
"message": "Between 10:30 AM and 2:40 PM UTC on April 13th, some customers may have experienced an issue to query live edge data and some customers may have noticed stopped synthetic monitors in the US region. The issue is now resolved and impacted services have returned to normal operations.",
"name": "Issue when querying live edge data in the US region",
"timestamp": "Apr \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e12:44\u003c/var\u003e - \u003cvar data-var='time'\u003e15:17\u003c/var\u003e UTC"
},
{
"code": "01vtjt5d5kz8",
"impact": "minor",
"message": "Between 02:34 UTC and 16:40 UTC on April 9th, 2026, some customers in the US region may have experienced delayed Synthetics Checks execution data in queries with Synthetics Job Manager. Impacted data may not be recoverable. We have investigated and resolved this service interruption and impacted services have returned to normal operations.",
"name": "Synthetics Manager",
"timestamp": "Apr \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e09:51\u003c/var\u003e - \u003cvar data-var='time'\u003e20:46\u003c/var\u003e UTC"
},
{
"code": "mxmcjztyvrzv",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed and all relevant New Relic endpoints have been transitioned to the DigiCert Global Root G2 certificate.\n\nFor further details, see https://support.newrelic.com/s/hubtopic/aAXPh000000HVSPOA4/action-required-root-certificate-update-on-april-1-2026.",
"name": "[Scheduled] Endpoint Root Certificate Update - April 9th at 00:00 UTC",
"timestamp": "Apr \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e - \u003cvar data-var='time'\u003e01:52\u003c/var\u003e UTC"
}
],
"name": "April",
"year": 2026
}
],
"start_time": "2026-04-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2026-03-31T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "jzz7vx05jtjp",
"impact": "none",
"message": "Between 2026-03-24 05:22:07 UTC and 2026-03-24 08:21:09 UTC on March Tuesday, some customers in the US/EU region may have experienced discrepancies in the NrComputeUsage and NRCompute usage values\n\nWe have investigated and resolved a service interruption and impacted services have returned to normal operations.",
"name": "NrComputeUsage is 0 for ScannedEvents",
"timestamp": "Mar \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e05:22\u003c/var\u003e - \u003cvar data-var='time'\u003e10:31\u003c/var\u003e UTC"
},
{
"code": "5cfsmy4fwlcv",
"impact": "minor",
"message": "We have resolved this service interruption and impacted services have returned to normal operation. Between 15:10 UTC and 16:08 UTC, some customers in the US region with Azure integrations may have experiencde 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. Impacted data may not be recoverable.",
"name": "Data Irregularities - US Region",
"timestamp": "Mar \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e15:52\u003c/var\u003e - \u003cvar data-var='time'\u003e16:10\u003c/var\u003e UTC"
},
{
"code": "330xs44zw7df",
"impact": "maintenance",
"message": "We have concluded our proactive testing window. Please see our post for more details: https://support.newrelic.com/s/hubtopic/aAXPh000000HVSPOA4/action-required-root-certificate-update-on-april-1-2026",
"name": "[Scheduled] Proactive Testing Window for Upcoming Root Certificate Update - March 12th at 00:00 UTC",
"timestamp": "Mar \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e00:28\u003c/var\u003e - \u003cvar data-var='time'\u003e02:21\u003c/var\u003e UTC"
},
{
"code": "y742xjh1g2vh",
"impact": "major",
"message": "We resolved this service interruption and impacted services have returned to normal operation. Between 00:11 UTC and 02:45 UTC on March 3rd, 2026, some customers may have experienced delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for impacted data.",
"name": "Data Irregularities",
"timestamp": "Mar \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e00:19\u003c/var\u003e - \u003cvar data-var='time'\u003e02:59\u003c/var\u003e UTC"
},
{
"code": "hvrk72hwhbhp",
"impact": "minor",
"message": "Between 06:56 UTC and 08:44 UTC on March 02nd some customers in the US or EU region may have experienced Delay in executing synthetics monitors .We have investigated and resolved this service interruption and impacted services have returned to normal operations",
"name": "Delay in executing synthetics monitors",
"timestamp": "Mar \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e07:06\u003c/var\u003e - \u003cvar data-var='time'\u003e09:42\u003c/var\u003e UTC"
}
],
"name": "March",
"year": 2026
},
{
"incidents": [
{
"code": "qx3b7dtlzcly",
"impact": "none",
"message": "Between 09:20 UTC and 09:44 UTC on Wed Feb 18 2026, some customers in the USEU region may have experienced delayed data in queries, charts, and dashboards. We have investigated and resolved this service interruption and impacted services have returned to normal operations.",
"name": "Charts not showing on Dashboards",
"timestamp": "Feb \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e10:06\u003c/var\u003e - \u003cvar data-var='time'\u003e10:06\u003c/var\u003e UTC"
},
{
"code": "c0s5dkn1xrqb",
"impact": "minor",
"message": "Between 15:15 UTC and 16:30 UTC some customers may have experienced an issue with Distributed Tracing.",
"name": "Distributed Tracing Errors for US and EU Regions",
"timestamp": "Feb \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e16:20\u003c/var\u003e - \u003cvar data-var='time'\u003e17:22\u003c/var\u003e UTC"
}
],
"name": "February",
"year": 2026
},
{
"incidents": [
{
"code": "j2tqjs711y1w",
"impact": "minor",
"message": "We have investigated and resolved this service interruption and impacted services have returned to normal operations. Between 19:58 UTC on January 21st, and 00:34 UTC on January 22nd, 2026, a subset of customers in the US region may have experienced issues with alert behavior including delayed alert notifications.",
"name": "Alert Irregularities - US",
"timestamp": "Jan \u003cvar data-var='date'\u003e21\u003c/var\u003e, \u003cvar data-var='time'\u003e22:23\u003c/var\u003e - Jan \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e00:46\u003c/var\u003e UTC"
},
{
"code": "841wj7g90mdb",
"impact": "major",
"message": "Our teams have resolved two concurrent service interruptions affecting data ingestion and query services.\n\nOn January 12th, 2026, a subset of customers in the US and EU regions may have experienced latency or timeouts when querying data in New Relic. Teams implemented a fix, restoring affected query performance at 17:29 UTC.\n\nSeparately, a subset of customers in the US and EU regions may have experienced errors when sending data to New Relic. This interruption could have resulted in potential data drops for data sent during this timeframe, depending on client-side retry settings, and may have generated false alert notifications regarding host reporting status. This interruption appears related to a disruption with a New Relic third-party edge service provider. To remediate, our teams have shifted traffic to an alternate cloud provider and have seen recovery of impacted services.",
"name": "Data and UI Irregularities - US and EU regions",
"timestamp": "Jan \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e15:21\u003c/var\u003e - \u003cvar data-var='time'\u003e18:10\u003c/var\u003e UTC"
}
],
"name": "January",
"year": 2026
}
],
"start_time": "2026-01-01T00:00:00Z",
"time_zone": "UTC"
},
{
"end_time": "2025-12-31T23:59:59Z",
"months": [
{
"incidents": [
{
"code": "f8ld20hltt3w",
"impact": "major",
"message": "Between 20:30:20 UTC on December 18th and 01:57:55 UTC on December 19th, some customers in the US region may have experienced false alerts and false loss of signal alert notifications.\nWe have investigated and resolved this service interruption and impacted services have returned to normal operations.",
"name": "Alert Irregularities in the US Region",
"timestamp": "Dec \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e23:30\u003c/var\u003e - Dec \u003cvar data-var='date'\u003e19\u003c/var\u003e, \u003cvar data-var='time'\u003e02:21\u003c/var\u003e UTC"
}
],
"name": "December",
"year": 2025
},
{
"incidents": [
{
"code": "0l6104s8lb6x",
"impact": "minor",
"message": "Between 11:15 UTC and 12:40 UTC on November 19, some customers in the EU region may have experienced difficulties in data ingest. We have investigated and resolved this service interruption and impacted services have returned to normal operations",
"name": "Data Irregularities - EU Region",
"timestamp": "Nov \u003cvar data-var='date'\u003e19\u003c/var\u003e, \u003cvar data-var='time'\u003e11:48\u003c/var\u003e - \u003cvar data-var='time'\u003e12:52\u003c/var\u003e UTC"
},
{
"code": "2qnyjzzld58m",
"impact": "none",
"message": "Between 11:46 UTC and 15:48 UTC on November 18th, 2025, some customers in the EU region may have experienced issues loading New Relic UI. The service interruption was investigated and resolved with our cloud provider and impacted services have returned to normal operations.",
"name": "UI Irregularities in EU Region",
"timestamp": "Nov \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e12:34\u003c/var\u003e - \u003cvar data-var='time'\u003e20:19\u003c/var\u003e UTC"
}
],
"name": "November",
"year": 2025
},
{
"incidents": [
{
"code": "pxp00j5cv6sv",
"impact": "minor",
"message": "Affected New Relic services have returned to normal operations following the resolution of the cloud provider network interruption. Our teams preliminary investigation indicates that New Relic ingest systems continued to function as expected throughout the interruption; however, data availability may differ depending on the configuration of each customer environment and their dependency on affected cloud provider services.",
"name": "Data Irregularities - US and EU region",
"timestamp": "Oct \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e08:40\u003c/var\u003e - \u003cvar data-var='time'\u003e21:33\u003c/var\u003e UTC"
},
{
"code": "s64hy0pgl3w3",
"impact": "major",
"message": "Between 13:21 UTC and 19:09 UTC, a subset of customers in the US region may have experienced delayed browser monitoring data for queries, charts, and dashboards as well as delayed or missing alert notifications for related data when alerts were not suppressed. We have resolved this interruption and services have returned to normal operations.",
"name": "Data Irregularities - US Region",
"timestamp": "Oct \u003cvar data-var='date'\u003e10\u003c/var\u003e, \u003cvar data-var='time'\u003e16:00\u003c/var\u003e - \u003cvar data-var='time'\u003e20:12\u003c/var\u003e UTC"
},
{
"code": "82k8d8y2m926",
"impact": "minor",
"message": "Between 16:20 UTC and 17:28 UTC on Tuesday, October 7th, 2025, some customers in the US region may have experienced delays in data appearing within the New Relic UI. Alert notifications may have also been delayed as a result. We have investigated and resolved this service interruption and impacted services have returned to normal operations.",
"name": "Data Irregularities - US Region",
"timestamp": "Oct \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e17:04\u003c/var\u003e - \u003cvar data-var='time'\u003e18:48\u003c/var\u003e UTC"
}
],
"name": "October",
"year": 2025
}
],
"start_time": "2025-10-01T00:00:00Z",
"time_zone": "UTC"
}
]
}