Is there an Opsgenie outage?

Opsgenie status: Systems Active

Last checked: 4 minutes ago

Get notified about any outages, downtime or incidents for Opsgenie and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Opsgenie outages and incidents

Outage and incident data over the last 30 days for Opsgenie.

There have been 1 outages or incidents for Opsgenie in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Opsgenie

Outlogger tracks the status of these components for Xero:

Public Website Active
Alert Flow Active
Alert REST API Active
Configuration REST APIs Active
Email Notification Delivery Active
Heartbeat Monitoring Active
Heartbeat REST API Active
Incident Flow Active
Incident REST API Active
Incoming Call Routing Active
Incoming Email Service Active
Incoming Integration Flow Active
Logs Active
Mobile Application Active
Mobile Notification Delivery Active
Opsgenie Actions Active
Outgoing Integration Flow Active
Pricing & Billing Active
Reporting & Analytics Active
Signup, Login & Authorization Active
SMS Notification Delivery Active
Voice Notification Delivery Active
Web Application Active
Alert Flow Active
Alert REST API Active
Configuration REST APIs Active
Email Notification Delivery Active
Heartbeat Monitoring Active
Heartbeat REST API Active
Incident Flow Active
Incident REST API Active
Incoming Call Routing Active
Incoming Email Service Active
Incoming Integration Flow Active
Logs Active
Mobile Application Active
Mobile Notification Delivery Active
Opsgenie Actions Active
Outgoing Integration Flow Active
Pricing & Billing Active
Reporting & Analytics Active
Signup, Login & Authorization Active
SMS Notification Delivery Active
Voice Notification Delivery Active
Web Application Active
Component Status
Public Website Active
Active
Alert Flow Active
Alert REST API Active
Configuration REST APIs Active
Email Notification Delivery Active
Heartbeat Monitoring Active
Heartbeat REST API Active
Incident Flow Active
Incident REST API Active
Incoming Call Routing Active
Incoming Email Service Active
Incoming Integration Flow Active
Logs Active
Mobile Application Active
Mobile Notification Delivery Active
Opsgenie Actions Active
Outgoing Integration Flow Active
Pricing & Billing Active
Reporting & Analytics Active
Signup, Login & Authorization Active
SMS Notification Delivery Active
Voice Notification Delivery Active
Web Application Active
Active
Alert Flow Active
Alert REST API Active
Configuration REST APIs Active
Email Notification Delivery Active
Heartbeat Monitoring Active
Heartbeat REST API Active
Incident Flow Active
Incident REST API Active
Incoming Call Routing Active
Incoming Email Service Active
Incoming Integration Flow Active
Logs Active
Mobile Application Active
Mobile Notification Delivery Active
Opsgenie Actions Active
Outgoing Integration Flow Active
Pricing & Billing Active
Reporting & Analytics Active
Signup, Login & Authorization Active
SMS Notification Delivery Active
Voice Notification Delivery Active
Web Application Active

Latest Opsgenie outages and incidents.

View the latest incidents for Opsgenie and check for official updates:

Updates:

  • Time: Aug. 2, 2022, 10:59 p.m.
    Status: Postmortem
    Update: ### **SUMMARY** On July 19, 2022, between 05:40 and 07:10 UTC, Atlassian customers in the EU region using Jira, Confluence and Opsgenie experienced problems loading pages through the web UI. The incident was automatically detected at 05.14 by one of Atlassian’s automated monitoring systems. The main disruption was resolved within 16 minutes with the full recovery taking additional 74 minutes. ### **IMPACT** Between July 19, 2022, 05:40 UTC and July 19, 2022, 07:10 UTC Jira, Confluence and OpsGenie users saw some web pages fail to load. During the 16 minute period from 06:40 UTC to 6:56 UTC, customers were unable to access Jira Confluence and OpsGenie web UI because the Atlassian Proxy \(the ingress point for service requests\) was unable to service most requests. ### **ROOT CAUSE** The issue was caused by an AWS initiated change that impacted Elastic Block Store \(EBS\) volume performance to such an extent that new instance creation and therefore auto scaling, was blocked.  As a result, the products above, as well as essential internal Atlassian services could not auto scale to the increasing incoming service requests as the EU region came online. Once the AWS change had been rolled back, most Atlassian services recovered. Some internal services required manual scaling as a result of unhealthy nodes preventing scaling initiation, which prolonged complete recovery. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity and we apologize to customers whose services were impacted during this incident. We see two main avenues to increase our resiliency during an incident where AWS auto scaling is blocked: * Implement step scaling: Simple scaling in most cases works well. In this case due to nodes becoming unhealthy, simple scaling stops responding to scaling alarms and therefore the service can become “stuck” and will not recover once scaling is possible again. We are exploring the use of step scaling, as this will allow scaling even in the case of instances becoming unhealthy. * Implement improved alarming to identify “stuck” scaling to increase the TTR when scaling is available again. We are taking these immediate steps to improve the platform’s resiliency. Thanks, Atlassian
  • Time: July 19, 2022, 8:52 a.m.
    Status: Resolved
    Update: Between 07:00 UTC to 07:45 UTC, we experienced degraded functionality for some features in Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, and Atlassian Developer. The issue has been resolved and the service is operating normally.
  • Time: July 19, 2022, 8:43 a.m.
    Status: Monitoring
    Update: Multiple Atlassian Cloud products and addons were unavailable to customers in some EU regions. The issue has been resolved and we are monitoring for further impact.

Updates:

  • Time: Aug. 2, 2022, 10:59 p.m.
    Status: Postmortem
    Update: ### **SUMMARY** On July 19, 2022, between 05:40 and 07:10 UTC, Atlassian customers in the EU region using Jira, Confluence and Opsgenie experienced problems loading pages through the web UI. The incident was automatically detected at 05.14 by one of Atlassian’s automated monitoring systems. The main disruption was resolved within 16 minutes with the full recovery taking additional 74 minutes. ### **IMPACT** Between July 19, 2022, 05:40 UTC and July 19, 2022, 07:10 UTC Jira, Confluence and OpsGenie users saw some web pages fail to load. During the 16 minute period from 06:40 UTC to 6:56 UTC, customers were unable to access Jira Confluence and OpsGenie web UI because the Atlassian Proxy \(the ingress point for service requests\) was unable to service most requests. ### **ROOT CAUSE** The issue was caused by an AWS initiated change that impacted Elastic Block Store \(EBS\) volume performance to such an extent that new instance creation and therefore auto scaling, was blocked.  As a result, the products above, as well as essential internal Atlassian services could not auto scale to the increasing incoming service requests as the EU region came online. Once the AWS change had been rolled back, most Atlassian services recovered. Some internal services required manual scaling as a result of unhealthy nodes preventing scaling initiation, which prolonged complete recovery. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity and we apologize to customers whose services were impacted during this incident. We see two main avenues to increase our resiliency during an incident where AWS auto scaling is blocked: * Implement step scaling: Simple scaling in most cases works well. In this case due to nodes becoming unhealthy, simple scaling stops responding to scaling alarms and therefore the service can become “stuck” and will not recover once scaling is possible again. We are exploring the use of step scaling, as this will allow scaling even in the case of instances becoming unhealthy. * Implement improved alarming to identify “stuck” scaling to increase the TTR when scaling is available again. We are taking these immediate steps to improve the platform’s resiliency. Thanks, Atlassian
  • Time: July 19, 2022, 8:52 a.m.
    Status: Resolved
    Update: Between 07:00 UTC to 07:45 UTC, we experienced degraded functionality for some features in Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, and Atlassian Developer. The issue has been resolved and the service is operating normally.
  • Time: July 19, 2022, 8:43 a.m.
    Status: Monitoring
    Update: Multiple Atlassian Cloud products and addons were unavailable to customers in some EU regions. The issue has been resolved and we are monitoring for further impact.

Updates:

  • Time: July 19, 2022, 8:27 a.m.
    Status: Resolved
    Update: The Problem has been resolved and the services are operating normally! Opsgenie has faced partial outages due to a minor update by the cloud provider and the team has worked with the cloud provider team to solve the incident in time. Only 15% of total requests and 4.1% of customers are affected by the incident. We will take the necessary actions to prevent facing a similar incident.
  • Time: July 19, 2022, 7:30 a.m.
    Status: Monitoring
    Update: The Fix has been deployed and rapid recovery is seen. We are monitoring the system for a full recovery.
  • Time: July 19, 2022, 6:38 a.m.
    Status: Identified
    Update: Our team has identified that Web and Mobile Application are responding slowly or unavailable for only Frankfurt.
  • Time: July 19, 2022, 6:31 a.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: July 19, 2022, 6:30 a.m.
    Status: Identified
    Update: Our team has identified the issue and are working on a fix. Next update in 1 hour or with a resolution of the incident
  • Time: July 19, 2022, 6:01 a.m.
    Status: Investigating
    Update: We've noticed that the Web and Mobile Application are responding slowly or unavailable for Frankfurt and North Virginia regions. This is not affecting our APIs. Our engineering team is actively investigating this incident and working to bring Opsgenie back up to speed as quickly as possible. We'll keep you posted with further updates on this page.

Updates:

  • Time: July 19, 2022, 8:27 a.m.
    Status: Resolved
    Update: The Problem has been resolved and the services are operating normally! Opsgenie has faced partial outages due to a minor update by the cloud provider and the team has worked with the cloud provider team to solve the incident in time. Only 15% of total requests and 4.1% of customers are affected by the incident. We will take the necessary actions to prevent facing a similar incident.
  • Time: July 19, 2022, 7:30 a.m.
    Status: Monitoring
    Update: The Fix has been deployed and rapid recovery is seen. We are monitoring the system for a full recovery.
  • Time: July 19, 2022, 6:38 a.m.
    Status: Identified
    Update: Our team has identified that Web and Mobile Application are responding slowly or unavailable for only Frankfurt.
  • Time: July 19, 2022, 6:31 a.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: July 19, 2022, 6:30 a.m.
    Status: Identified
    Update: Our team has identified the issue and are working on a fix. Next update in 1 hour or with a resolution of the incident
  • Time: July 19, 2022, 6:01 a.m.
    Status: Investigating
    Update: We've noticed that the Web and Mobile Application are responding slowly or unavailable for Frankfurt and North Virginia regions. This is not affecting our APIs. Our engineering team is actively investigating this incident and working to bring Opsgenie back up to speed as quickly as possible. We'll keep you posted with further updates on this page.

Updates:

  • Time: June 30, 2022, 10:09 p.m.
    Status: Resolved
    Update: Problem has been resolved and the services are operating normally! We will take the necessary actions to prevent facing a similar incident, and sorry for the inconvenience while we worked on this
  • Time: June 30, 2022, 9:58 p.m.
    Status: Monitoring
    Update: Fix has been deployed to USA region and rapid recovery is seen. We are monitoring the system for a full recovery.
  • Time: June 30, 2022, 9:15 p.m.
    Status: Identified
    Update: Our team has identified the issue with addition/update/deletion operations of team, schedule, forwarding and escalations. We are working to fix it. Check back soon for another update! Our team is working hard to get Opsgenie up and running in full performance again.

Check the status of similar companies and alternatives to Opsgenie

Qualys
Qualys

Issues Detected

Ping Identity
Ping Identity

Systems Active

Veracode
Veracode

Systems Active

OPSWAT
OPSWAT

Systems Active

Sonatype
Sonatype

Systems Active

Aqua Security
Aqua Security

Systems Active

appviewx
appviewx

Systems Active

Signifyd
Signifyd

Systems Active

Alert Logic
Alert Logic

Systems Active

Red Canary
Red Canary

Systems Active

Frequently Asked Questions - Opsgenie

Is there a Opsgenie outage?
The current status of Opsgenie is: Systems Active
Where can I find the official status page of Opsgenie?
The official status page for Opsgenie is here
How can I get notified if Opsgenie is down or experiencing an outage?
To get notified of any status changes to Opsgenie, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Opsgenie every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Opsgenie do?
Opsgenie is a tool for alerting and incident response, ensuring critical alerts are never missed and services are restored promptly.