Opsgenie

Dec 16, 15:30 UTC
Resolved – Our team has identified the issue in Schedule API between 15:30 UTC and 17:00 UTC. We saw performance degradation and 5XX errors in response. Faulty deployment has been reverted quickly in the USA region and rapid recovery is seen. We are monitoring the system for a full recovery right now. The Schedule API is up and running again without any data loss.

Nov 6, 19:59 UTC
Resolved – Our engineers have been closely monitoring the platform and are declaring this incident resolved. Thank you for your patience.

Nov 6, 19:49 UTC
Monitoring – Our engineering team has implemented fixes. We will continue to monitor all systems. Thank you for your patience.

Nov 6, 19:47 UTC
Investigating – We’ve noticed that Opsgenie Web UI is responding slowly or unavailable in US region.

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.

Sep 24, 20:54 UTC
Resolved – We’ve verified that OEC endpoints are back online.

Sep 24, 20:49 UTC
Monitoring – We reverted the faulty routing configuration change and started getting traffic on OEC endpoints

Sep 24, 20:22 UTC
Identified – We’ve identified a recent change that has broken some endpoint routing configurations and caused OEC endpoint requests to be directed to wrong service. We’re reverting that change on production at the moment.

Sep 24, 19:56 UTC
Update – We are continuing to investigate this issue.

Sep 24, 19:55 UTC
Investigating – We’ve been notified that a number of OEC clients have been failing to create Jira tickets. We’re currently investigating the issue.

Sep 12, 03:28 UTC
Resolved – This issue has been resolved.

Sep 12, 02:40 UTC
Monitoring – We have identified the root cause and the issue appears to be resolved.

Sep 12, 02:08 UTC
Investigating – Users attempting to sign up are encountering reCaptcha errors that are preventing a successful signup.