CompaniesLaunchDarklyIncidents
LaunchDarkly: LaunchDarkly JIRA and VSTS integrations were unavailable.
Heroku outage, Mar 16, 2020 · 8 vendors, 9 incidents
LaunchDarkly’s incident started in the same window without naming Heroku (timing only, not evidence of a link). (timing only, posted +17 min vs the first vendor naming Heroku)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Heroku<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>4 vendors, 4 blamed Heroku<br/>RevenueCat, Substack, Bitrise, crates.io"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed Heroku<br/>RevenueCat"]:::blames
root --> h4
me["LaunchDarkly (this incident)<br/>posted +17 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
LaunchDarkly JIRA and VSTS integrations were unavailable. Due to an issue at an upstream provider, the JIRA integration and the VSTS integration were unavailable between 9:13am PDT and 9:25am PDT. You may need to manually associate JIRA issues or VSTS issues that were modified during this window. https://status.heroku.com/incidents/1973
From LaunchDarkly’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.launchdarkly.com (opens in new tab).
LaunchDarkly profileRecent LaunchDarkly incidentsMarkdownJSON