Is New Relic Down Right Now?
APM dashboards gone dark, traces disappearing, alerts silent — when your observability platform goes down, you are flying blind. This guide helps you diagnose New Relic outages fast and minimize the blind spot.
The average API outage costs $5,600 per minute
Gartner estimates downtime costs $5,600/min on average. 98% of organizations say a single hour of downtime costs over $100,000. Proactive monitoring catches issues in under 30 seconds.
📡 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
Check New Relic Status Now
New Relic publishes detailed per-region status for each platform component:
New Relic Platform Components
New Relic is a full-stack observability platform. Identify the specific component affected — NRDB issues impact everything, while an APM agent issue only affects one language runtime.
Language agents (Java, Python, Node, Ruby, .NET, Go, PHP)
Core telemetry database powering all queries and dashboards
End-to-end transaction tracing across services
Alert evaluation, anomaly detection, incident correlation
Host, container, Kubernetes metrics
Real-user monitoring (RUM) for web apps
Scripted and ping monitors for uptime testing
Log ingestion and search via NRDB
Break the observability blind spot
When New Relic goes down, your team is blind. Better Stack runs external synthetic checks that operate independently of your APM stack — alerting you before you lose visibility completely.
Try Better Stack Free →Diagnosing APM Data Gaps
Data gaps are the most common New Relic complaint. The root cause is almost always one of five things:
Collector endpoint unreachable
License key invalid
Agent sampling under load
NRDB write degradation
Application restart broke agent
Verify Agent Connectivity
Test whether your New Relic agent can reach the collector endpoint from your application server:
# Test collector reachability (US datacenter)
curl -s https://collector.newrelic.com/status/mongrel \
-o /dev/null -w "%{http_code}"
# EU datacenter
curl -s https://collector.eu.newrelic.com/status/mongrel \
-o /dev/null -w "%{http_code}"
# Expected: 200 = reachable | 000 = blocked/unreachable
# Check agent log for connection errors (Java example)
grep -i "error\|warn\|connect" /var/log/newrelic/newrelic_agent.log | tail -20Alert 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
Frequently Asked Questions
Is New Relic down right now?
Check the official New Relic status page at status.newrelic.com. It shows per-region health for APM, Distributed Tracing, NRDB, Alerting, Infrastructure Monitoring, and Browser. New Relic publishes detailed incident timelines with impact and resolution notes.
Why is my New Relic APM data missing or showing gaps?
Data gaps in New Relic APM are caused by: (1) New Relic collector outage — check status.newrelic.com, (2) Agent connectivity issue — the APM agent cannot reach the New Relic collector endpoint, (3) License key invalid or expired — check account settings, (4) Agent version incompatibility — outdated agents may stop reporting, (5) High-cardinality data sampling — New Relic may sample or drop metrics under load, (6) Application deploy broke the agent instrumentation. Check your agent logs for connection errors first.
Why are New Relic alerts not firing?
New Relic alert failures have several causes: (1) NRDB query engine degradation — alerts query NRDB for signal evaluation, check status.newrelic.com, (2) Notification channel failure — Slack webhook, PagerDuty, or email channel broken, (3) Alert condition in "Lost Signal" state — no data flowing for the monitored entity, (4) Muting rules covering the alert — check Alerts & AI → Muting Rules, (5) Alert policy not linked to notification channels — verify the policy → notification channel association. Test your notification channels from the Alerts UI.
What is NRDB and how does it affect New Relic?
NRDB (New Relic Database) is the proprietary telemetry database that stores all New Relic data — metrics, events, logs, and traces. When NRDB is degraded, all New Relic capabilities degrade simultaneously: dashboards show stale data, NRQL queries fail or timeout, alerts cannot evaluate, and distributed traces become incomplete. NRDB status is listed separately on status.newrelic.com and is the most impactful component when degraded.
How do I get notified when New Relic itself is down?
Use an external monitoring service independent of New Relic: (1) Subscribe to status.newrelic.com email or Slack notifications, (2) Use Better Stack to monitor your New Relic UI URL and get alerts via SMS/phone before your team notices, (3) API Status Check tracks New Relic status and can alert you. The circular dependency problem — New Relic going down disables your alerts — is solved only with an external monitoring layer.
🛠 Tools We Use & Recommend
Tested across our own infrastructure monitoring 200+ APIs daily
Uptime Monitoring & Incident Management
Used by 100,000+ websites
Monitors your APIs every 30 seconds. Instant alerts via Slack, email, SMS, and phone calls when something goes down.
“We use Better Stack to monitor every API on this site. It caught 23 outages last month before users reported them.”
Secrets Management & Developer Security
Trusted by 150,000+ businesses
Manage API keys, database passwords, and service tokens with CLI integration and automatic rotation.
“After covering dozens of outages caused by leaked credentials, we recommend every team use a secrets manager.”
SEO & Site Performance Monitoring
Used by 10M+ marketers
Track your site health, uptime, search rankings, and competitor movements from one dashboard.
“We use SEMrush to track how our API status pages rank and catch site health issues early.”