Outages by dayJanuary 31, 2016
Outages on January 31, 2016
UTC day 2016-01-31 ( to your time). Incidents as the vendors posted them on their status pages; impact labels are the vendor’s own.
5incidents started
0labelled major or critical
3vendors with a new incident
3still open from earlier days
By vendor label: Minor 2 · No impact listed 3
Incidents started this day 5
| Vendor | Incident | Impact | Started | Resolved | Status |
|---|---|---|---|---|---|
| Logz.io | S3 fetching is slower than usual | Minor | (11 min) | resolved | |
| Braze | Cache failures causing API timeouts | Minor | (1.1 h) | resolved | |
| Close | [Scheduled] Infrastructure Upgrade | No impact listed | (38 min) | resolved | |
| Logz.io | Data Processing Delays - Reporting Tools Affected | No impact listed | (12 min) | resolved | |
| Logz.io | Data Processing Delays - Reporting Tools Affected | No impact listed | (19 min) | resolved |
Still open from earlier days 3
| Vendor | Incident | Impact | Started | Resolved | Status |
|---|---|---|---|---|---|
| Dialpad | Chat support unavailable | Minor | (3 d) | resolved | |
| Dialpad | Support unavailable through email and chat | Minor | (2 d) | resolved | |
| Discord | Frankfurt server region experiencing connectivity issues | Minor | (11 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: Logz.io, Braze, Close.
Cite this
5 vendor-reported incidents started on 2016-01-31 (UTC) across 3 vendors, 0 labelled major or critical by the vendor.
- Title
- Outages on January 31, 2016
- Vendor
- Rewindex daily outage roundup
- Date
- URL
- https://rewindex.com/outages/2016-01-31