CompaniesLaunchDarklyMonthly reportsMarch 2017
LaunchDarkly in March 2017: incidents, uptime and changes
Vendor-reported outage time 2 h 46 min, incident time 10 h 22 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 3 · Minor 2 · No impact listed 1
Major and critical incidents 3
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Data streaming delays | Major | 43 min | resolved | 03-21 | |
| Data streaming delays | Major | 1.5 h | resolved | 03-22 | |
| Data streaming delays | Major | 31 min | resolved | 03-28 |
Other incidents 3
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Site navigation broken by third-party script | No impact listed | 0 min | resolved | 03-30 | |
| Streaming API is experiencing a partial outage | Minor | 1.2 h | resolved | 03-31 | |
| Some Streaming API connections timing out | Minor | 6.4 h | resolved | 03-31 |
Cite this
LaunchDarkly posted 6 status incidents in March 2017 (3 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- LaunchDarkly in March 2017
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/2017/03