CompaniesLaunchDarklyMonthly reportsMarch 2020
LaunchDarkly in March 2020: incidents, uptime and changes
Vendor-reported outage time 1 h 27 min, incident time 6 h 45 min. Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours. Last 90 days.
By vendor label: Major 1 · Minor 3 · No impact listed 1
Major and critical incidents 1
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Increased connect times for streaming API | Major | 1.4 h | resolved | 03-12 |
Other incidents 4
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Degraded performance in the experimentation service | No impact listed | 40 min | resolved | 03-04 | |
| Increased connect times for mobile streaming API the Asia Pacific region | Minor | 1.1 h | resolved | 03-06 | |
| LaunchDarkly JIRA and VSTS integrations were unavailable. | Minor | 0 min | resolved | 03-16 | |
| Experimentation results are delayed | Minor | 4.2 h | resolved | 03-16 |
Cite this
LaunchDarkly posted 5 status incidents in March 2020 (1 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- LaunchDarkly in March 2020
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/2020/03