CompaniesSegmentMonthly reportsFebruary 2017
Segment in February 2017: incidents, uptime and changes
8incidents posted
0labelled major or critical
100%free of major/critical
99.11%free of any incident
0price changes
0notable page changes
Vendor-reported outage time 0 min, incident time 5 h 58 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 6
Incidents 8
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Tracking API Failures | Minor | 0 min | resolved | 02-01 | |
| Intercom Data Delay | No impact listed | 1.5 h | resolved | 02-07 | |
| Settings Page Inaccessible | No impact listed | 12 min | resolved | 02-08 | |
| Data Delay | No impact listed | 12 d | resolved | 02-10 | |
| Iterable Data Latency (resolved) | No impact listed | 0 min | resolved | 02-10 | |
| Data delays | No impact listed | 2 d | resolved | 02-21 | |
| Data delays on Sendwithus integration | Minor | 6.0 h | resolved | 02-27 | |
| AWS S3 outage affecting Segment partners and warehouses | No impact listed | 28 h | resolved | 02-28 |
Cite this
Segment posted 8 status incidents in February 2017 (0 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- Segment in February 2017
- Vendor
- Segment
- Date
- URL
- https://rewindex.com/company/segment/2017/02