Is OpsGenie Down? How to Tell and What to Do

OpsGenie is the on-call management and alert routing backbone for thousands of engineering teams. When OpsGenie degrades, pages stop reaching on-call engineers, escalation policies don't execute, and your incident response process breaks exactly when you need it most.

Statusfield brings reported OpsGenie incidents into the same workspace as your other monitors. Select supported components and route relevant changes to your team. Vendor reports can lag an incident, so check your own application as well.

Follow OpsGenie incidents with your team

Statusfield brings reported status for OpsGenie together with your other critical tools. Choose the changes that should alert your team. Eligible new accounts can start a free trial — no credit card required.

Start free trial

Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.

Common Signs of an OpsGenie Outage

Symptom	What's likely happening
Alerts not being created despite integrations firing	Alert ingestion API is degraded
On-call engineers not receiving pages	Notification delivery is down
Escalation policies not triggering	Escalation engine is degraded
OpsGenie web UI not loading	Web infrastructure is affected
Mobile app push notifications delayed	Mobile push delivery is degraded
Integrations (Datadog, PagerDuty, Prometheus) not creating alerts	Webhook receiver is down
Schedules and rotations not updating	Scheduling service is degraded
API calls returning 5xx	OpsGenie API is unavailable

How to Confirm It's OpsGenie, Not Your Integration

1. Test alert creation via the OpsGenie API

bash

curl -X POST "https://api.opsgenie.com/v2/alerts" \
  -H "Content-Type: application/json" \
  -H "Authorization: GenieKey YOUR_API_KEY" \
  -d '{"message":"Test alert","description":"Incident response check"}'

A 503 or connection failure confirms the API is degraded — not a misconfiguration on your integration.

2. Check the OpsGenie dashboard directly

If the web UI fails to load or shows errors, the platform is down. In that case, your on-call notifications are not being delivered regardless of what your monitoring tools are firing.

3. Test a direct notification

In the OpsGenie dashboard (if accessible), manually create a test alert to your own on-call schedule. If the alert creates but the notification never arrives, the delivery pipeline is degraded.

4. Check integration-side logs

If your alerting source (Datadog, Grafana, Prometheus) shows the webhook fired successfully but OpsGenie never created the alert, the issue is on OpsGenie's ingestion side.

Why OpsGenie Outages Are High-Stakes

OpsGenie outages are different from most vendor outages. They don't degrade your product — they degrade your ability to respond to any incident affecting your product.

During an OpsGenie outage:

A production outage can go unresponsed for an extended period
On-call engineers have no way to know they're needed
Escalation paths don't execute — if the primary doesn't respond, the backup never gets paged
Post-incident timelines are incomplete — no alert means no record of when the incident started

Follow reported OpsGenie status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.

Follow OpsGenie incidents with your team

Follow reported incidents for OpsGenie in Statusfield and send relevant updates to your configured channels. Eligible new accounts can start a free trial — no credit card required.

Start free trial

Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.

What to Do During an OpsGenie Outage

Immediate (first 5 minutes)

Switch to your backup escalation path — direct call/SMS, Slack emergency channel, or PagerDuty if it's your secondary. Do this immediately; don't wait.
Manually page on-call engineers — if you have a production incident open, reach your on-call directly via phone or messaging.
Pause integrations that would create alert noise — if monitoring tools keep firing alerts into a degraded OpsGenie, your queue will be polluted. Mute non-critical integrations temporarily.
Document the gap — note the time OpsGenie went down for post-incident SLA calculations.

Communication (first 15 minutes)

Notify all on-call engineers via a backup channel that OpsGenie is down and they should watch for direct contact.
Communicate with stakeholders that your incident response time may be slower during the degradation.
If you have an active production incident, use your backup communication channel to coordinate response.

Recovery

Once OpsGenie recovers, verify alert queues — alerts may have been queued during the outage and fire in bulk on recovery.
Confirm all open alerts are assigned and acknowledged.
Re-enable muted integrations after queue processing is complete.

OpsGenie Components and What Each Outage Looks Like

Component	Impact when degraded
Alert ingestion API	Alerts from integrations not created
Notification delivery	Alerts created, but engineers not paged
Escalation engine	Primary not responding; backup never paged
Mobile push delivery	Mobile app notifications delayed
Web UI	Dashboard inaccessible
Schedule management	On-call rotations not updating
Webhook receivers	Integration-triggered alerts not processed
SMS delivery	Phone notifications fail to send

Why You Need External Monitoring for Your Alert Tool

Your alerting infrastructure is only as reliable as the weakest link. If that link is OpsGenie, you need something outside it to tell you when it's down.

Teams that have gone through an OpsGenie outage without external monitoring typically experience:

A production incident that went unresponsed for 30+ minutes because no one got paged
An SLA breach that wasn't caught in time to communicate proactively
Post-mortem confusion about the incident timeline because the alert never fired

Following Opsgenie’s reported status in Statusfield adds provider context. To detect whether your own alerting process has stopped, send a heartbeat after its checks complete and route missing-check-in alerts through a separate available destination. Check current heartbeat access before relying on this setup.

Monitor OpsGenie and Keep Incident Response Reliable

Eligible first-time customers can start a free trial, no credit card required.

Follow OpsGenie incidents with your team

Follow OpsGenie and your other vendors in one Statusfield workspace. Select supported components and route the updates your team needs. Eligible new accounts can start a free trial — no credit card required.

Start free trial

Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.

FAQ

Is OpsGenie down right now?

This article is a troubleshooting guide, not a live outage verdict. Check the Statusfield catalog and the official vendor status page for the latest reported status, affected components and observation times. Compare those reports with what your own application is experiencing.

How can I get alerts about OpsGenie incidents?

Does an operational OpsGenie status mean my application is working?

No. A vendor status page describes reported service conditions. Your account, integration, network or application can still fail. Check your own public HTTPS endpoint and use logs or workflow tests to investigate the customer experience.

Browse the service catalog and plans and alert destinations.

Is OpsGenie Down? How to Tell and What to Do