New Relic Status: How to Check If New Relic Is Down Right Now (2026)
Updated June 2026 · 8 min read · API Status Check
Quick Answer
Check New Relic status at status.newrelic.com (official) for real-time APM, Infrastructure, Synthetics, and platform status by data center region.
📡 Monitor your APIs — know when they go down before your users do
Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.
Affiliate link — we may earn a commission at no extra cost to you
The Official New Relic Status Page
New Relic maintains an official status page at status.newrelic.com. It shows real-time status across the full New Relic observability platform:
What Each New Relic Status Means
Monitor your app independently of New Relic
Better Stack monitors your application health endpoints directly — so you get paged when your app goes down even if New Relic itself is having an outage. Free tier included.
Try Better Stack Free →New Relic Data Centers: US vs. EU
New Relic operates separate data center regions. Your account is provisioned in one of these regions and data never leaves it:
US Data Center (Default)
Most New Relic accounts use the US data center by default. Your ingest endpoints are metric-api.newrelic.com, log-api.newrelic.com, and trace-api.newrelic.com. APM agents connect to collector.newrelic.com. status.newrelic.com tracks both US and EU data centers separately.
EU Data Center (GDPR)
EU-region accounts use metric-api.eu.newrelic.com, log-api.eu.newrelic.com, and collector.eu.newrelic.com. Required for GDPR compliance. EU data center incidents may be separate from US incidents — check the EU-specific component on status.newrelic.com if you're on the EU data center.
Agent Buffering During Outages
New Relic APM agents (Java, .NET, Node.js, Python, Ruby, Go, PHP) buffer data in memory when they cannot reach New Relic's ingest endpoints. For short outages (< 5 minutes), data typically resumes after reconnect with minimal gaps. For longer outages, in-memory buffers overflow and some metric data is dropped. Transaction traces and error details are most likely to be lost.
New Relic Telemetry SDKs & OpenTelemetry
If you use the New Relic Telemetry SDK or OpenTelemetry with New Relic as a backend, data is sent via the Metric API, Trace API, or Event API. These have the same status as the rest of the platform. During an ingest outage, the OTLP endpoint (otlp.nr-data.net) also fails — implement a retry or dead-letter strategy in your telemetry pipeline.
5 Ways to Check New Relic Status Right Now
Official New Relic Status Page
Visit status.newrelic.com for per-product, per-region status. Subscribe to email notifications for incidents affecting your data center.
status.newrelic.com →Try Opening the New Relic UI
Navigate to one.newrelic.com (US) or one.eu.newrelic.com (EU). If the page fails to load or login hangs, the New Relic Platform (UI) component is likely having issues — check the status page.
Test the New Relic Ingest API Directly
Send a test metric to New Relic's Metric API to verify data ingest is working.
# Test New Relic Metric API ingest (US data center)
curl -X POST https://metric-api.newrelic.com/metric/v1 \
-H "Api-Key: YOUR_LICENSE_KEY" \
-H "Content-Type: application/json" \
-d '[{"metrics":[{"name":"test.metric","type":"gauge","value":1,"timestamp":'$(date +%s)'000}]}]'
# 202 Accepted = ingest working, 403 = key issue, 503 = outageX/Twitter Search
Search 'New Relic down' or 'newrelic outage' on X. DevOps and SRE teams report New Relic issues quickly.
Search X for 'new relic down' →New Relic Support & Community
Open a support ticket at support.newrelic.com or check the New Relic Community Forum (discuss.newrelic.com). For critical production incidents, use the phone support option available on Enterprise plans.
New Relic Support →Common New Relic Errors During Outages
These are the errors and symptoms you'll see when New Relic is experiencing issues:
"No data in APM — gap in metrics chart"Data ingest has stopped or the APM agent is failing to connect. Check your agent logs for connection errors to collector.newrelic.com. If status.newrelic.com shows operational, verify your license key, network firewall rules, and agent proxy settings."NRQL query timed out"New Relic's query engine is overloaded or experiencing degraded performance. Simplify your query by narrowing the time range or reducing the number of facets. During platform-wide query degradation, all accounts are affected and you must wait for recovery."Dashboards showing "no data" for all widgets"Either data ingest is failing (metrics/events not reaching New Relic) or the query engine is down. Check status.newrelic.com — if both Data Ingest and the Platform show operational, check your agent's connection logs and verify your account isn't over its data ingest limits."Alert conditions not triggering / missed pages"New Relic's Alert evaluation engine is degraded or down. Critical alerts will not fire during this period. Switch to manual monitoring or a secondary alerting system. After recovery, check the alert history for the missed evaluation window."Synthetics checks paused / not running"New Relic Synthetics service is degraded. Scheduled ping and scripted browser checks will not execute from New Relic's monitoring locations. External monitoring tools will still work — use them as a backup during Synthetics outages."one.newrelic.com not loading / 502 Bad Gateway"The New Relic UI (Platform component) is down. Data may still be ingesting in the background. Check status.newrelic.com — if only the UI is affected, your monitoring data is still being collected and will appear once the UI recovers.What to Do When New Relic Is Down
Immediate Response
- Confirm on status.newrelic.com — identify which component and region is affected
- Check your application directly — use health endpoints, logs, and server metrics via SSH
- Activate your runbook for monitoring-blind periods (manual error log review)
- Notify on-call team that automated alerting is unavailable during the outage
- Switch to secondary monitoring (Datadog, Better Stack, or Grafana) if configured
- Document incident start time for SLA credit claim against New Relic SLA
Long-Term Resilience
- Set up a secondary monitoring tool (Better Stack, Datadog, or Grafana Cloud) for critical alerts
- Use OpenTelemetry with multiple exporters — send to New Relic and a backup simultaneously
- Implement health endpoints in your apps so you can monitor directly without APM
- Subscribe to status.newrelic.com email notifications for proactive awareness
- Keep a runbook for alert-free periods so the team knows what to monitor manually
Frequently Asked Questions
Where is the official New Relic status page?
New Relic's official status page is at status.newrelic.com. It tracks APM, Infrastructure, Browser, Synthetics, Alerts, Logs, Mobile, and the New Relic Platform UI separately for both US and EU data centers. Subscribe to email notifications to be alerted when incidents affect your region.
Will I lose monitoring data if New Relic goes down?
For short outages (minutes), most APM agents buffer data in memory and send it when connectivity restores — you see a gap in charts but data is not lost. For longer outages, in-memory buffers overflow and some metric data is dropped. Error traces and transaction details are most at risk. Custom events sent via the Event API may also be lost if retries are exhausted.
How do I know if it is New Relic vs. my application that is having issues?
Check status.newrelic.com first. If New Relic is operational, the issue is in your application, your agents, or network connectivity between your infrastructure and New Relic. Check agent logs for connection errors, verify your New Relic license key is active, and confirm your firewall allows outbound traffic to collector.newrelic.com on port 443.
Can I still use New Relic if the UI is down but ingest is working?
Yes — the New Relic Platform (UI) and data ingest are separate components. If only the UI is down, your agents continue sending data to New Relic. Once the UI recovers, all ingested data during the outage will be visible. Use the NerdGraph API (api.newrelic.com/graphiql) to query data programmatically if the UI is unavailable.
How does New Relic compare to Datadog for reliability?
Both New Relic and Datadog are enterprise-grade observability platforms with strong SLAs. New Relic has had several notable outages historically. Datadog's architecture is more distributed, which tends to limit blast radius during partial failures. For maximum reliability, teams use both tools with OpenTelemetry as a vendor-neutral collection layer — sending metrics to multiple backends simultaneously.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time New Relic goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for New Relic + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial