New Relic 장애 기록

1. 2026년 8월 3일 AM 9:58 UTCinvestigating

   우리는 EU 및 미국 지역의 일부 고객이 경고 및 활동 페이지를 볼 때 지연 또는 오류를 경험할 수 있는 문제를 조사하고 있습니다.

2. 2026년 8월 3일 AM 10:15 UTCresolved

   8월 3일 오전 8시 13분과 오전 9시 30분 사이에 EU 및 미국 지역의 고객들은 새로운 리플 UI의 Alerts 및 Issues 페이지를 로드하려고 시도할 때 문제가 발생할 수 있습니다. 문제는 이제 해결되고 충격적 인 서비스는 정상 서비스로 돌아 왔습니다. 문제를 해결하기 위해 Alerts 페이지를 닫고 다시 엽니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 17일 AM 10:21 UTCresolved

   7월 14일 오후 15:00 UTC와 7월 17일 오전 10:00 UTC 사이, 우리는 미국, EU 및 JP 지역의 E2M (Events-2-Metrics) 규칙을 만들거나 읽거나 업데이트 할 때 일부 고객이 인증 문제가있는 문제를 경험했습니다. 이것은 최근 변화로 인해 우리는 우리의 허가 엔드 포인트로 만들었습니다. 이 엔드포인트는 이제 S2S 인증을 필요로 합니다. E2M (Events-2-Metrics)에 대한 요청이 실패합니다. 우리의 팀은 영원한 고침이 장소에 둘 수 있을 때까지 이 변화를 다시 구출했습니다. 문제는 이제 해결되고 충격적 인 서비스는 정상 서비스로 돌아 왔습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 6일 AM 8:23 UTCresolved

   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.

1. 2026년 5월 18일 PM 4:25 UTCresolved

   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.

1. 2026년 5월 15일 AM 12:06 UTCinvestigating

   We are investigating an interruption where some customers in the US region may be experiencing issues loading the different pages in the New Relic UI. Some customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. If you are experiencing issues and unable to access In-App support, please reach out to our Support team through this form: https://support.newrelic.com/s/contact-new-relic-support-form.

2. 2026년 5월 15일 AM 12:42 UTCinvestigating

   We continue investigating an interruption where some customers in the US region may be experiencing issues loading the different pages in the New Relic UI. Some customers in the US region may be experiencing delayed data in queries, charts, and dashboards. After further review, Alerts were not impacted. If you are experiencing issues and unable to access In-App support, please reach out to our Support team through this form: https://support.newrelic.com/s/contact-new-relic-support-form.

3. 2026년 5월 15일 AM 1:16 UTCmonitoring

   We are seeing recovery for impacted services, and continue monitoring New Relic systems for full recovery. Some customers in the US region may have experienced issues loading different pages in the New Relic UI. Some customers in the US region may have also experienced delayed data in queries, charts, and dashboards. Data ingest and alerts were not impacted.

4. 2026년 5월 15일 AM 1:45 UTCresolved

   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. We resolved this issue and the above services have returned to normal operation.

1. 2026년 4월 13일 PM 12:55 UTCinvestigating

   We are investigating an issue where some customers may be unable to query live edge data in the US region. Data ingest and alert notifications are not impacted by this interruption.

2. 2026년 4월 13일 PM 1:58 UTCinvestigating

   We are continuing to investigate an issue where some customers may be unable to query live edge data and some customers may notice stopped synthetic monitors in the US region. Technical teams are actively engaged and are exploring mitigation steps to address the issue. Data ingest and alert notifications are not impacted by this interruption.

3. 2026년 4월 13일 PM 2:41 UTCinvestigating

   We are still investigating an issue where some customers may be unable to query live edge data and some customers may notice stopped synthetic monitors in the US region. We continue to work on the issue and understand root cause. We will continue to provide updates as we have more information to share, or by 3:30 PM UTC.

4. 2026년 4월 13일 PM 3:17 UTCresolved

   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.

1. 2026년 4월 9일 AM 9:51 UTCinvestigating

   Some customers in the US region may be experiencing delayed Synthetics Checks execution data in queries with Synthetics Job Manager.

2. 2026년 4월 9일 PM 12:28 UTCidentified

   We have identified the issue and working on a solution

3. 2026년 4월 9일 PM 2:05 UTCmonitoring

   Our team has now issued a fix and are monitoring the issue.

4. 2026년 4월 9일 PM 4:48 UTCmonitoring

   Between 02:34 UTC and 16:45 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.

5. 2026년 4월 9일 PM 8:46 UTCresolved

   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.

1. 2026년 3월 24일 AM 5:22 UTCinvestigating

   Some customers in the US and EU regions may experience discrepancies in NRComputeusage and NRConsumption usage values

2. 2026년 3월 24일 AM 6:02 UTCinvestigating

   We are continuing to investigate an issue where some customers in the US and EU regions may experience discrepancies in NRComputeusage and NRConsumption usage values

3. 2026년 3월 24일 AM 10:31 UTCresolved

   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 We have investigated and resolved a service interruption and impacted services have returned to normal operations.

1. 2026년 3월 20일 PM 3:53 UTCinvestigating

   We are investigating a service interruption where some customers in the US region with Azure integrations may experience 5xx 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.

2. 2026년 3월 20일 PM 3:59 UTCinvestigating

   We are seeing recovery for Azure integrations at this time. Some customers in the US region with Azure integrations 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. Impacted data may not be recoverable.

3. 2026년 3월 20일 PM 4:10 UTCresolved

   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.

1. 2026년 3월 3일 AM 12:21 UTCinvestigating

   Some customers in the US and EU regions may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data.

2. 2026년 3월 3일 AM 12:36 UTCinvestigating

   We are continuing to investigate an issue where some customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data.

3. 2026년 3월 3일 AM 1:02 UTCinvestigating

   We are still investigating the an issue where some customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We have been seeing signs of recovery, and will continue to provide updates until services are restored to normal operations.

4. 2026년 3월 3일 AM 2:28 UTCmonitoring

   We continue to see signs of recovery as we monitor impacted services. Some customers in the US region may be experiencing delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We will continue to provide updates until services return to normal operations.

5. 2026년 3월 3일 AM 2:59 UTCresolved

   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.

1. 2026년 3월 2일 AM 7:06 UTCinvestigating

   Some customers in the US and EU region may experience delay in executing synthetics monitors

2. 2026년 3월 2일 AM 7:35 UTCinvestigating

   We have engaged our Cloud provider to assist with further investigation and are evaluating additional mitigation efforts.

3. 2026년 3월 2일 AM 9:42 UTCresolved

   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

1. 2026년 2월 18일 AM 10:06 UTCresolved

   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.

1. 2026년 2월 5일 PM 4:20 UTCinvestigating

   We are currently investigating an issue causing errors with Distributed Tracing

2. 2026년 2월 5일 PM 4:40 UTCmonitoring

   Our Team has now issued a fix and are monitoring the issue.

3. 2026년 2월 5일 PM 5:22 UTCresolved

   Between 15:15 UTC and 16:30 UTC some customers may have experienced an issue with Distributed Tracing.

1. 2026년 1월 21일 PM 10:23 UTCinvestigating

   We are investigating an issue with alert behavior. Some customers in the US region may experience delayed or missing alert notifications related to real-time data.

2. 2026년 1월 21일 PM 10:53 UTCinvestigating

   We are continuing to investigate an issue with alerts irregularities where a subset of customers in the US region may experience delayed or missing alert notifications for real-time data.

3. 2026년 1월 22일 AM 12:00 UTCidentified

   We have implemented a fix and are starting to see recovery for impacted services. A subset of customers in the US region may experience delayed or missing alert notifications for real-time data.

4. 2026년 1월 22일 AM 12:46 UTCresolved

   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.

1. 2026년 1월 12일 PM 3:21 UTCinvestigating

   We are currently investing an issue causing timeouts/query lag in NRDB

2. 2026년 1월 12일 PM 3:22 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 1월 12일 PM 3:53 UTCinvestigating

   We have engaged our additional teams to assist with further investigation and are evaluating additional mitigation efforts.

4. 2026년 1월 12일 PM 5:36 UTCidentified

   Some customers in the US and 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. We are seeing recovery from mitigating actions and will continue to provide updates until services have been restored to normal operation.

5. 2026년 1월 12일 PM 6:10 UTCresolved

   Our teams have resolved two concurrent service interruptions affecting data ingestion and query services. On 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. Separately, 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.

1. 2025년 12월 18일 PM 11:30 UTCinvestigating

   We are investigating a potential service interruption that may impact some customers. Please continue to monitor this page for updates.

2. 2025년 12월 18일 PM 11:52 UTCinvestigating

   Some customers in the US and EU region may experience false loss of signal alert notifications.

3. 2025년 12월 19일 AM 1:00 UTCinvestigating

   We are continuing to investigate this issue.

4. 2025년 12월 19일 AM 1:56 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 2025년 12월 19일 AM 2:21 UTCresolved

   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. We have investigated and resolved this service interruption and impacted services have returned to normal operations.

1. 2025년 11월 19일 AM 11:48 UTCinvestigating

   We are investigating an issue with data ingest

2. 2025년 11월 19일 PM 12:16 UTCidentified

   We have engaged our Product Management Team to assist with further investigation and are evaluating additional mitigation efforts.

3. 2025년 11월 19일 PM 12:34 UTCmonitoring

   Some customers in the EU region have reported recovery of data ingest.

4. 2025년 11월 19일 PM 12:52 UTCresolved

   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

1. 2025년 11월 18일 PM 12:34 UTCinvestigating

   Some customers in the EU region may experience difficulty logging into New Relic accounts. If you are experiencing issues and unable to access In-App support, please reach out to our Support team through this form: https:support.newrelic.comscontact-new-relic-support-form.

2. 2025년 11월 18일 PM 2:15 UTCidentified

   We have engaged our cloud provider to assist with further investigation and are evaluating additional mitigation efforts. Some customers in the EU region may continue experience difficulty with the New Relic UI. If you are experiencing issues and unable to access In-App support, please reach out to our Support team through this form: https:support.newrelic.comscontact-new-relic-support-form.

3. 2025년 11월 18일 PM 3:23 UTCmonitoring

   We have put in place mitigations for an issue with a Cloud Provider which has been causing UI issues for customers in the EU region. We will continue to monitor the situation while our Cloud Provider is working on a fix. If you continue to experience issues and are unable to access In-App support, please reach out to our Support team through this form: https:support.newrelic.comscontact-new-relic-support-form.

4. 2025년 11월 18일 PM 8:19 UTCresolved

   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.

1. 2025년 10월 20일 AM 8:45 UTCidentified

   Some customers in the US and EU region may experience errors when sending data to New Relic using cloud or synthetics, issues in viewing data in real time, and delayed or missing data in synthetics and cloud.

2. 2025년 10월 20일 AM 9:14 UTCidentified

   Some customers in the US and EU region may experience errors when sending data to New Relic using cloud or synthetics, issues in viewing data in real time, delays in Entity events appearing in customer account

3. 2025년 10월 20일 AM 11:56 UTCmonitoring

   We have engaged our Cloud provider to assist with further investigation and have implemented additional mitigation efforts. Which should lead to full recovery in synthetics and some recovery in Cloud. However some customers may still experience some delays in entity events appearing.

4. 2025년 10월 20일 PM 12:13 UTCmonitoring

   We have engaged our Cloud provider to assist with further investigation and have implemented additional mitigation efforts. Which has lead to full recovery in synthetics and some recovery in Cloud. However some customers may still experience some delays in entity events appearing.

5. 2025년 10월 20일 PM 5:54 UTCmonitoring

   We have been able to confirm an ongoing network interruption with our cloud provider. As a result, some customers in the US and EU regions may experience intermittent irregularities for some features including synthetics, infinite tracing, cloud integrations, mobile symbolication and crash events, and entity relationships. We will provide our next update at 20:00 UTC or upon significant change.

6. 2025년 10월 20일 PM 7:57 UTCmonitoring

   We are seeing signs of recovery for impacted services as our cloud provider continues to resolve the ongoing network interruption. We will continue to monitor the situation and provide updates as more information is available.

7. 2025년 10월 20일 PM 9:33 UTCresolved

   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.

1. 2025년 10월 10일 PM 4:00 UTCinvestigating

   We are continuing to investigate this issue.

2. 2025년 10월 10일 PM 4:01 UTCinvestigating

   A subset of customers in the US region may experience delayed Browser Monitoring data for queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We are starting to see recovery, and will provide our next update when our services have returned to normal operation. To prevent our customers from receiving a high volume of false positive alert notifications, we have temporarily suppressed notifications for affected data.

3. 2025년 10월 10일 PM 4:43 UTCidentified

   We have identified an issue impacting browser data in the US region. A subset of US customers may be experiencing delayed Browser Monitoring data for queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We continue to see recovery, and will provide an update when our services have returned to normal operation. To prevent our customers from receiving a high volume of false positive alert notifications, we have temporarily suppressed notifications for affected data.

4. 2025년 10월 10일 PM 5:02 UTCidentified

   We are continuing to work on a fix for this issue.

5. 2025년 10월 10일 PM 5:03 UTCidentified

   We have identified an issue impacting browser data in the US region. A subset of US customers may be experiencing delayed Browser Monitoring data for queries, charts, and dashboards. We continue to see recovery and alerts were unsuppressed. We will continue to provide updates until our services have returned to normal operation.

6. 2025년 10월 10일 PM 5:56 UTCidentified

   We are continuing to investigate an issue impacting browser data and have applied alert suppression to prevent our customers from receiving a high volume of false positive alert notifications for affected data. A subset of US customers may be experiencing delayed Browser Monitoring data for queries, charts, and dashboards as well as delayed or missing alert notifications for related data. We will provide an update when our services have returned to normal operation.

7. 2025년 10월 10일 PM 6:46 UTCidentified

   We are continuing to mitigate an issue impacting browser data and have recently unsuppressed alerts due to our current recovering state. A subset of US customers may be experiencing delayed Browser Monitoring data for queries, charts, and dashboards. We will continue to provide updates until our services have returned to normal operation.

8. 2025년 10월 10일 PM 8:12 UTCresolved

   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.