CompaniesIterableMonthly reportsJanuary 2017
Iterable in January 2017: incidents, uptime and changes
3incidents posted
0labelled major or critical
100%free of major/critical
99.88%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 0 min, incident time 53 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 2 · No impact listed 1
Incidents 3
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Degraded Performance on Track and Update APIs | No impact listed | 0 min | resolved | 01-06 | |
| Degraded Database Performance | Minor | 3 min | resolved | 01-30 | |
| Degraded Database Performance | Minor | 50 min | resolved | 01-30 |
Cite this
Iterable posted 3 status incidents in January 2017 (0 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Iterable in January 2017
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/2017/01