CompaniesIterableMonthly reportsFebruary 2017
Iterable in February 2017: incidents, uptime and changes
5incidents posted
0labelled major or critical
100%free of major/critical
98.71%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 0 min, incident time 8 h 37 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: Minor 4 · No impact listed 1
Incidents 5
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Degraded Database Performance | Minor | 1.8 h | resolved | 02-16 | |
| Degraded Back-end Processing Performance | Minor | 4.1 h | resolved | 02-17 | |
| Degraded Back-end Processing Performance | Minor | 2.3 h | resolved | 02-21 | |
| Degraded Back-end Processing Performance | Minor | 27 min | resolved | 02-23 | |
| AWS Outage | No impact listed | 3.2 h | resolved | 02-28 |
Cite this
Iterable posted 5 status incidents in February 2017 (0 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Iterable in February 2017
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/2017/02