Is there an Opsgenie outage?

Opsgenie status: Systems Active

Last checked: 10 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: Feb. 27, 2024, 5:43 p.m.
    Status: Resolved
    Update: We fixed the problem and verified that there are no more login issues.
  • Time: Feb. 27, 2024, 2:42 p.m.
    Status: Monitoring
    Update: The team has identified the issue causing the signature validation error at EU SAML Login. The fix has been started to deploy and SAML login activities are being monitored by team currently
  • Time: Feb. 27, 2024, 2:25 p.m.
    Status: Investigating
    Update: Opsgenie SAML Login functionality is not working at only EU region due to signature verification error at login certificates. Already logged in customers haven't been affected by the error.

Updates:

  • Time: Feb. 27, 2024, 5:45 a.m.
    Status: Postmortem
    Update: ### **Summary** On February 14, 2024, between 20:05 UTC and 23:03 UTC, Atlassian customers on the following cloud products encountered a service disruption: Access, Atlas, Atlassian Analytics, Bitbucket, Compass, Confluence, Ecosystem apps, Jira Service Management, Jira Software, Jira Work Management, Jira Product Discovery, Opsgenie, StatusPage, and Trello. As part of a security and compliance uplift, we had scheduled the deletion of unused and legacy domain names used for internal service-to-service connections. Active domain names were incorrectly deleted during this event. This impacted all cloud customers across all regions. The issue was identified and resolved through the rollback of the faulty deployment to restore the domain names and Atlassian systems to a stable state. The time to resolution was two hours and 58 minutes. ### **IMPACT** External customers started reporting issues with Atlassian cloud products at 20:52 UTC. The impact of the failed change led to performance degradation or in some cases, complete service disruption. Symptoms experienced by end-users were unsuccessful page loads and/or failed interactions with our cloud products. ### **ROOT CAUSE** As part of a security and compliance uplift, we had scheduled the deletion of unused and legacy domain names that were being used for internal service-to-service connections. Active domain names were incorrectly deleted during this operation. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. The detection was delayed because existing testing & monitoring focused on service health rather than the entire system’s availability. To prevent a recurrence of this type of incident, we are implementing the following improvement measures: * Canary checks to monitor the entire system availability. * Faster rollback procedures for this type of service impact. * Stricter change control procedures for infrastructure modifications. * Migration of all DNS records to centralised management and stricter access controls on modification to DNS records. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. ‌ Thanks, Atlassian Customer Support
  • Time: Feb. 14, 2024, 11:32 p.m.
    Status: Resolved
    Update: We experienced increased errors on Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Align, Jira Product Discovery, Atlas, Compass, and Atlassian Analytics. The issue has been resolved and the services are operating normally.
  • Time: Feb. 14, 2024, 10:55 p.m.
    Status: Monitoring
    Update: We have identified the root cause of the Service Disruptions affecting all Atlassian products and have mitigated the problem. We are now monitoring this closely.
  • Time: Feb. 14, 2024, 10:31 p.m.
    Status: Identified
    Update: We have identified the root cause of the increased errors and have mitigated the problem. We continue to work on resolving the issue and monitoring this closely.
  • Time: Feb. 14, 2024, 9:57 p.m.
    Status: Investigating
    Update: We are investigating reports of intermittent errors for all Cloud Customers across all Atlassian products. We will provide more details once we identify the root cause.

Updates:

  • Time: Feb. 27, 2024, 5:45 a.m.
    Status: Postmortem
    Update: ### **Summary** On February 14, 2024, between 20:05 UTC and 23:03 UTC, Atlassian customers on the following cloud products encountered a service disruption: Access, Atlas, Atlassian Analytics, Bitbucket, Compass, Confluence, Ecosystem apps, Jira Service Management, Jira Software, Jira Work Management, Jira Product Discovery, Opsgenie, StatusPage, and Trello. As part of a security and compliance uplift, we had scheduled the deletion of unused and legacy domain names used for internal service-to-service connections. Active domain names were incorrectly deleted during this event. This impacted all cloud customers across all regions. The issue was identified and resolved through the rollback of the faulty deployment to restore the domain names and Atlassian systems to a stable state. The time to resolution was two hours and 58 minutes. ### **IMPACT** External customers started reporting issues with Atlassian cloud products at 20:52 UTC. The impact of the failed change led to performance degradation or in some cases, complete service disruption. Symptoms experienced by end-users were unsuccessful page loads and/or failed interactions with our cloud products. ### **ROOT CAUSE** As part of a security and compliance uplift, we had scheduled the deletion of unused and legacy domain names that were being used for internal service-to-service connections. Active domain names were incorrectly deleted during this operation. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. The detection was delayed because existing testing & monitoring focused on service health rather than the entire system’s availability. To prevent a recurrence of this type of incident, we are implementing the following improvement measures: * Canary checks to monitor the entire system availability. * Faster rollback procedures for this type of service impact. * Stricter change control procedures for infrastructure modifications. * Migration of all DNS records to centralised management and stricter access controls on modification to DNS records. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. ‌ Thanks, Atlassian Customer Support
  • Time: Feb. 14, 2024, 11:32 p.m.
    Status: Resolved
    Update: We experienced increased errors on Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Align, Jira Product Discovery, Atlas, Compass, and Atlassian Analytics. The issue has been resolved and the services are operating normally.
  • Time: Feb. 14, 2024, 10:55 p.m.
    Status: Monitoring
    Update: We have identified the root cause of the Service Disruptions affecting all Atlassian products and have mitigated the problem. We are now monitoring this closely.
  • Time: Feb. 14, 2024, 10:31 p.m.
    Status: Identified
    Update: We have identified the root cause of the increased errors and have mitigated the problem. We continue to work on resolving the issue and monitoring this closely.
  • Time: Feb. 14, 2024, 9:57 p.m.
    Status: Investigating
    Update: We are investigating reports of intermittent errors for all Cloud Customers across all Atlassian products. We will provide more details once we identify the root cause.

Updates:

  • Time: Jan. 29, 2024, 3:29 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Jan. 29, 2024, 3:14 p.m.
    Status: Monitoring
    Update: The team has reverted the changes and identified that corresponding heartbeat and email integration start working now
  • Time: Jan. 29, 2024, 3:08 p.m.
    Status: Identified
    Update: Due to faulty domain configurations, heartbeats updates via email and incoming email services have been rejected starting from 13:45 UTC. The team has been working on the fix. Except for email updates and email integrations, heartbeat feature and integrations are still fully functional.

Updates:

  • Time: Jan. 29, 2024, 3:29 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Jan. 29, 2024, 3:14 p.m.
    Status: Monitoring
    Update: The team has reverted the changes and identified that corresponding heartbeat and email integration start working now
  • Time: Jan. 29, 2024, 3:08 p.m.
    Status: Identified
    Update: Due to faulty domain configurations, heartbeats updates via email and incoming email services have been rejected starting from 13:45 UTC. The team has been working on the fix. Except for email updates and email integrations, heartbeat feature and integrations are still fully functional.

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.

Start monitoring now!

Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.

Get Started for Free