All Systems Operational
About This Site
Welcome to the New Relic status page. To configure notifications for service incidents, click Subscribe to Updates. For past incident information, see the Incident History.
Data Ingest : US
Operational
APM Agent : US
Operational
Browser Agent : US
Operational
Event API : US
Operational
Incident Intelligence API : US
Operational
Infrastructure Agent : US
Operational
Log API : US
Operational
Metric API : US
Operational
Mobile Agent : US
Operational
OTLP API : US
Operational
Trace API : US
Operational
Synthetics : US
Operational
Alert Notifications : US
Operational
APM : US
Operational
Browser : US
Operational
Infrastructure : US
Operational
Logs : US
Operational
Mobile : US
Operational
NRQL : US
Operational
Serverless : US
Operational
Synthetics : US
Operational
UI : US
Operational
Alerts : US
Operational
APM : US
Operational
Auto-Telemetry with Pixie : US
Operational
AWS Lambda Integration : US
Operational
Browser : US
Operational
Dashboards : US
Operational
Incident Intelligence : US
Operational
Infrastructure : US
Operational
Infrastructure Integrations : US
Operational
Logs : US
Operational
Lookout : US
Operational
Mobile : US
Operational
Open Instrumentation : US
Operational
Proactive Detection : US
Operational
Serverless : US
Operational
Synthetics : US
Operational
Data Ingest : Europe
Operational
APM Agent : Europe
Operational
Browser Agent : Europe
Operational
Event API : Europe
Operational
Incident Intelligence API : Europe
Operational
Infrastructure Agent : Europe
Operational
Log API : Europe
Operational
Metric API : Europe
Operational
Mobile Agent : Europe
Operational
OTLP API : Europe
Operational
Trace API : Europe
Operational
Synthetics : Europe
Operational
Alert Notifications : Europe
Operational
APM : Europe
Operational
Browser : Europe
Operational
Infrastructure : Europe
Operational
Logs : Europe
Operational
Mobile : Europe
Operational
NRQL : Europe
Operational
Serverless : Europe
Operational
Synthetics : Europe
Operational
UI : Europe
Operational
Alerts : Europe
Operational
APM : Europe
Operational
Auto-Telemetry with Pixie : Europe
Operational
AWS Lambda Integration : Europe
Operational
Browser : Europe
Operational
Dashboards : Europe
Operational
Incident Intelligence : Europe
Operational
Infrastructure : Europe
Operational
Infrastructure Integrations : Europe
Operational
Logs : Europe
Operational
Lookout : Europe
Operational
Mobile : Europe
Operational
Open Instrumentation : Europe
Operational
Proactive Detection : Europe
Operational
Serverless : Europe
Operational
Synthetics : Europe
Operational
isNewUser
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Endpoint Root Certificate Update - April 9th at 00:00 UTC Apr 9, 2026 00:00-02:00 UTC
Update -
Permanent G2 Certificate Transition Postponed to April 09, 2026
To allow customers additional time to update legacy environments and avoid data drops, New Relic is postponing the permanent transition to the DigiCert Global Root G2 certificate by one week.
The final cutover is now scheduled for 00:00 UTC on April 09, 2026.
Please note: This is the final postponement. Because the industry-wide deadline for G1 distrust is April 15th, we cannot delay this change any further without risking a total service interruption for all New Relic customers. Systems not updated by April 9th will lose the ability to send telemetry data to New Relic.
Any further updates will be posted on status.newrelic.com, as well as our forum: https://support.newrelic.com/s/hubtopic/aAXPh000000HVSPOA4/action-required-root-certificate-update-on-april-1-2026
Apr 01, 2026 - 17:11 UTC
To allow customers additional time to update legacy environments and avoid data drops, New Relic is postponing the permanent transition to the DigiCert Global Root G2 certificate by one week.
The final cutover is now scheduled for 00:00 UTC on April 09, 2026.
Please note: This is the final postponement. Because the industry-wide deadline for G1 distrust is April 15th, we cannot delay this change any further without risking a total service interruption for all New Relic customers. Systems not updated by April 9th will lose the ability to send telemetry data to New Relic.
Any further updates will be posted on status.newrelic.com, as well as our forum: https://support.newrelic.com/s/hubtopic/aAXPh000000HVSPOA4/action-required-root-certificate-update-on-april-1-2026
Apr 01, 2026 - 17:11 UTC
Scheduled -
On April 2nd at 00:00 UTC, New Relic will permanently transition to the DigiCert G2 root certificate for all endpoints.
This aligns with an industry-wide security change. On April 15th, 2026, major browser trust stores and security authorities will officially distrust the legacy DigiCert G1 Root Certificate. To maintain its strong continued security posture, New Relic is updating its infrastructure to utilize modern root certificates prior to this deadline.
Most modern systems and agents are designed to handle this change automatically.
If your systems do not recognize and trust these newer root certificates when the update is applied, the secure handshake will fail and would result in a telemetry data drop, meaning your metrics, events, traces, and logs may stop reporting to the New Relic platform. This risk is primarily associated with legacy Java agents (older than v6.4.2), certain Docker images, and systems using pinned certificates.
Any further updates will be posted on status.newrelic.com, as well as our forum: https://support.newrelic.com/s/hubtopic/aAXPh000000HVSPOA4/action-required-root-certificate-update-on-april-1-2026
Mar 18, 2026 - 17:54 UTC
This aligns with an industry-wide security change. On April 15th, 2026, major browser trust stores and security authorities will officially distrust the legacy DigiCert G1 Root Certificate. To maintain its strong continued security posture, New Relic is updating its infrastructure to utilize modern root certificates prior to this deadline.
Most modern systems and agents are designed to handle this change automatically.
If your systems do not recognize and trust these newer root certificates when the update is applied, the secure handshake will fail and would result in a telemetry data drop, meaning your metrics, events, traces, and logs may stop reporting to the New Relic platform. This risk is primarily associated with legacy Java agents (older than v6.4.2), certain Docker images, and systems using pinned certificates.
Any further updates will be posted on status.newrelic.com, as well as our forum: https://support.newrelic.com/s/hubtopic/aAXPh000000HVSPOA4/action-required-root-certificate-update-on-april-1-2026
Mar 18, 2026 - 17:54 UTC