CompaniesIterableMonthly reportsFebruary 2019
Iterable in February 2019: incidents, uptime and changes
6incidents posted
0labelled major or critical
100%free of major/critical
93.94%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 0 min, incident time 40 h 40 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 6
Incidents 6
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Ingestion Delays | Minor | 7.5 h | resolved | 02-01 | |
| Data ingestion slow for some customers | Minor | 4.9 h | resolved | 02-01 | |
| Data Ingestion Slow For Some Customers | Minor | 6.1 h | resolved | 02-14 | |
| Data ingestion delays | Minor | 18 h | resolved | 02-16 | |
| Data ingestion delays | Minor | 2.5 h | resolved | 02-17 | |
| Bulk data ingestion delayed for some customers | Minor | 1.7 h | resolved | 02-26 |
Cite this
Iterable posted 6 status incidents in February 2019 (0 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Iterable in February 2019
- Vendor
- Iterable
- Date
- URL
- https://rewindex.com/company/iterable/2019/02