CompaniesLaunchDarklyMonthly reportsFebruary 2017
LaunchDarkly in February 2017: incidents, uptime and changes
Vendor-reported outage time 1 h 11 min, incident time 5 h 16 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 1 · No impact listed 1
Major and critical incidents 1
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Streaming API is experiencing a partial outage | Major | 1.2 h | resolved | 02-22 |
Other incidents 2
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Events collection service is down after a deploy | No impact listed | 2.4 h | resolved | 02-16 | |
| Audit log is affected by S3 outage | Minor | 4.1 h | resolved | 02-28 |
Cite this
LaunchDarkly posted 3 status incidents in February 2017 (1 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- LaunchDarkly in February 2017
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/2017/02