Outages by dayFebruary 10, 2017
Outages on February 10, 2017
UTC day 2017-02-10 ( to your time). Incidents as the vendors posted them on their status pages; impact labels are the vendor’s own.
19incidents started
3labelled major or critical
14vendors with a new incident
6still open from earlier days
By vendor label: Critical 1 · Major 2 · Minor 4 · No impact listed 12
Incidents started this day 19
Still open from earlier days 6
| Vendor | Incident | Impact | Started | Resolved | Status |
|---|---|---|---|---|---|
| Smartsheet | Smartsheet Application & API | Major | (32 h) | resolved | |
| Bandwidth | Bandwidth Local Market Impairment (LATA: 244 Roanoke, VA) | Major | (8.0 h) | resolved | |
| Smartsheet | System Generated Emails | Minor | (8.0 h) | resolved | |
| Mixpanel | Intermittent errors on a subset of projects | Minor | (4 d) | resolved | |
| Datadog | Investigating an issue with our schedule downtime API. | Minor | (5 min) | resolved | |
| Stitch | Intermittent Google Analytics Issues | No impact listed | (47 h) | resolved |
Times show in your time zone (UTC in the page source). An incident counts as “still open” here if it started up to 7 days earlier and had not been resolved by the start of this UTC day (unresolved ones count for 24 hours). See each vendor’s monthly report: Plivo, JFrog, Close, Greenhouse, Mapbox, Twilio, Segment, Bitbucket, Mixpanel, CircleCI, Travis CI, Optimizely.
Cite this
19 vendor-reported incidents started on 2017-02-10 (UTC) across 14 vendors, 3 labelled major or critical by the vendor.
- Title
- Outages on February 10, 2017
- Vendor
- Rewindex daily outage roundup
- Date
- URL
- https://rewindex.com/outages/2017-02-10