rewindex

CompaniesTelnyxUptime

Telnyx uptime

From vendor reports 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.

91.77%free of major or critical incidents, last 30 days
84.41%free of major or critical incidents, last 90 days
63.85%free of any incident, last 90 days
48incidents started, last 90 days

Last 90 days, by UTC day

Aug 7 (UTC day): 8 h 57 min with a major or critical incident open, 9 h 48 min with any incident open, 2 incidents startedAug 8 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 9 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 10 (UTC day): 21 h 19 min with a major or critical incident open, 21 h 19 min with any incident openAug 11 (UTC day): 6 h 13 min with a major or critical incident open, 6 h 13 min with any incident open, 1 incident startedAug 12 (UTC day): no vendor-reported incident openAug 13 (UTC day): 0 min with a major or critical incident open, 14 h 47 min with any incident open, 1 incident startedAug 14 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openAug 15 (UTC day): 20 h 2 min with a major or critical incident open, 24 h with any incident open, 1 incident startedAug 16 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 17 (UTC day): 24 h with a major or critical incident open, 24 h with any incident open, 1 incident startedAug 18 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 19 (UTC day): 24 h with a major or critical incident open, 24 h with any incident open, 1 incident startedAug 20 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 21 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openAug 22 (UTC day): 3 h 58 min with a major or critical incident open, 24 h with any incident openAug 23 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openAug 24 (UTC day): 31 min with a major or critical incident open, 19 h 28 min with any incident open, 1 incident startedAug 25 (UTC day): no vendor-reported incident openAug 26 (UTC day): no vendor-reported incident openAug 27 (UTC day): 0 min with a major or critical incident open, 57 min with any incident open, 1 incident startedAug 28 (UTC day): no vendor-reported incident openAug 29 (UTC day): no vendor-reported incident openAug 30 (UTC day): no vendor-reported incident openAug 31 (UTC day): no vendor-reported incident openSep 1 (UTC day): 1 h 3 min with a major or critical incident open, 3 h 32 min with any incident open, 2 incidents startedSep 2 (UTC day): 0 min with a major or critical incident open, 2 h 26 min with any incident open, 1 incident startedSep 3 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 4 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 5 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 6 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 7 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 8 (UTC day): 25 min with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 9 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedSep 10 (UTC day): 7 h 59 min with a major or critical incident open, 23 h 59 min with any incident open, 3 incidents startedSep 11 (UTC day): 4 h 20 min with a major or critical incident open, 4 h 20 min with any incident openSep 12 (UTC day): no vendor-reported incident openSep 13 (UTC day): no vendor-reported incident openSep 14 (UTC day): 1 h 10 min with a major or critical incident open, 1 h 10 min with any incident open, 1 incident startedSep 15 (UTC day): 0 min with a major or critical incident open, 8 h 32 min with any incident open, 2 incidents startedSep 16 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 17 (UTC day): 0 min with a major or critical incident open, 24 h with any incident openSep 18 (UTC day): 0 min with a major or critical incident open, 16 h 27 min with any incident openSep 19 (UTC day): no vendor-reported incident openSep 20 (UTC day): no vendor-reported incident openSep 21 (UTC day): no vendor-reported incident openSep 22 (UTC day): 1 h with a major or critical incident open, 2 h 47 min with any incident open, 2 incidents startedSep 23 (UTC day): 6 h 6 min with a major or critical incident open, 19 h 55 min with any incident open, 3 incidents startedSep 24 (UTC day): no vendor-reported incident openSep 25 (UTC day): 54 min with a major or critical incident open, 54 min with any incident open, 1 incident startedSep 26 (UTC day): no vendor-reported incident openSep 27 (UTC day): no vendor-reported incident openSep 28 (UTC day): 36 min with a major or critical incident open, 36 min with any incident open, 1 incident startedSep 29 (UTC day): no vendor-reported incident openSep 30 (UTC day): no vendor-reported incident openOct 1 (UTC day): no vendor-reported incident openOct 2 (UTC day): 46 min with a major or critical incident open, 46 min with any incident open, 1 incident startedOct 3 (UTC day): no vendor-reported incident openOct 4 (UTC day): no vendor-reported incident openOct 5 (UTC day): no vendor-reported incident openOct 6 (UTC day): 6 h 21 min with a major or critical incident open, 6 h 21 min with any incident open, 1 incident startedOct 7 (UTC day): 19 h 30 min with a major or critical incident open, 19 h 30 min with any incident openOct 8 (UTC day): no vendor-reported incident openOct 9 (UTC day): no vendor-reported incident openOct 10 (UTC day): 0 min with a major or critical incident open, 2 h 2 min with any incident open, 1 incident startedOct 11 (UTC day): no vendor-reported incident openOct 12 (UTC day): 5 h 27 min with a major or critical incident open, 5 h 27 min with any incident open, 1 incident startedOct 13 (UTC day): 0 min with a major or critical incident open, 2 h 34 min with any incident open, 2 incidents startedOct 14 (UTC day): no vendor-reported incident openOct 15 (UTC day): no vendor-reported incident openOct 16 (UTC day): 5 h 38 min with a major or critical incident open, 5 h 38 min with any incident open, 1 incident startedOct 17 (UTC day): 8 min with a major or critical incident open, 8 min with any incident openOct 18 (UTC day): no vendor-reported incident openOct 19 (UTC day): no vendor-reported incident openOct 20 (UTC day): no vendor-reported incident openOct 21 (UTC day): 4 h 56 min with a major or critical incident open, 4 h 56 min with any incident open, 1 incident startedOct 22 (UTC day): 11 h 18 min with a major or critical incident open, 11 h 18 min with any incident openOct 23 (UTC day): 0 min with a major or critical incident open, 5 h 2 min with any incident open, 1 incident startedOct 24 (UTC day): no vendor-reported incident openOct 25 (UTC day): no vendor-reported incident openOct 26 (UTC day): no vendor-reported incident openOct 27 (UTC day): 0 min with a major or critical incident open, 2 h 33 min with any incident open, 1 incident startedOct 28 (UTC day): 0 min with a major or critical incident open, 6 h 45 min with any incident open, 3 incidents startedOct 29 (UTC day): 0 min with a major or critical incident open, 24 h with any incident open, 1 incident startedOct 30 (UTC day): 0 min with a major or critical incident open, 3 h 9 min with any incident open, 1 incident startedOct 31 (UTC day): no vendor-reported incident openNov 1 (UTC day): no vendor-reported incident openNov 2 (UTC day): 0 min with a major or critical incident open, 8 h 24 min with any incident open, 1 incident startedNov 3 (UTC day): 5 h 57 min with a major or critical incident open, 11 h with any incident open, 5 incidents startedNov 4 (UTC day): 0 min with a major or critical incident open, 6 min with any incident open

Aug 7today

no incident minor incident minor, 6 h+ major/critical major/critical, 6 h+ before archive

Last 7 days, by hour

now

Numbers

WindowFree of major/criticalFree of any incidentOutage timeIncident timeIncidents
Last 30 days91.77%83.48%2.5 days5.0 days20
Last 90 days84.41%63.85%14.0 days32.5 days48

This is what Telnyx itself reported, so it can miss outages the vendor never posted and overstate ones where an incident was left open. Regional or single-component incidents count the same as global ones. Recomputed .

See the incidents: Telnyx status history · last 90 days · Telnyx status page (opens in new tab) · Markdown