Opsgenie: API v1 outage and degraded performance on outgoing integrations
Timeline of updates
- resolved
We sent an library upgrade to backend services at 14:44 UTC, during blue-green deploy phase everything seemed OK. When we shut down old instances transaction durations started to increase. We understood that the problem was in the caching layer. Revert decision made at 15:45 UTC, but a bug in deployment automation prevented us to solve the problem immediately. We started to revert instances manually. Between 16:28 UTC and 16:42 UTC backend services receiving API v1 requests, fully went down. Also we experienced delays at outgoing integrations up to 20 minutes. API v2 and alerting / notification flows were functional during the incident. A detailed post-mortem will be published later on.
From Opsgenie’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on opsgenie.status.atlassian.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Opsgenie, started 2018-02-21 15:35 UTC, resolved after 21 h, 1 update(s).
- Title
- API v1 outage and degraded performance on outgoing integrations
- Vendor
- Opsgenie
- Date
- URL
- https://rewindex.com/company/opsgenie/incidents/xm97mcnm1tg0
Opsgenie profileRecent Opsgenie incidentsAll outages on February 21, 2018Opsgenie in February 2018MarkdownJSON