TPx Communications status history
Current state: operational — “All Systems Operational” per https://tpxcommunications.statuspage.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do TPx Communications incidents last?
From 28 incidents with a vendor-posted start and resolve time. Longest on record: Intermittent On Hold Dropped Calls — 33.1 days (2026-07-02 19:24 UTC). Excluded, never estimated: 1 scheduled maintenance. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (29)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-09 18:28 UTC | Test Incident | resolved | none | 1 min |
| 2026-09-02 17:40 UTC | Los Angeles Internet Traffic Degradation | resolved | minor | 6 d 0 h |
| 2026-08-25 19:28 UTC | Arista Velocloud Platform Maintenance | resolved | minor | 7 d 22 h |
| 2026-08-13 21:22 UTC | Arista Velocloud Platform Maintenance | resolved | minor | 7 d 17 h |
| 2026-08-10 16:15 UTC | Atlanta Slow Internet Event | resolved | minor | 14 h 07 min |
| 2026-08-04 21:40 UTC | Velocloud Security Vulnerability Event | resolved | minor | 8 d 23 h |
| 2026-08-02 22:44 UTC | Velocloud Security Vulnerability Event | resolved | minor | 46 h 57 min |
| 2026-07-23 18:49 UTC | Microsoft Azure Service Issues | resolved | minor | 19 h 56 min |
| 2026-07-21 18:49 UTC | Dallas Internet Slow Speed Event | resolved | critical | 6 d 9 h |
| 2026-07-02 19:24 UTC | Intermittent On Hold Dropped Calls | resolved | minor | 33 d 2 h |
| 2026-07-01 00:24 UTC | Frontier Outage - Los Angeles Area | resolved | major | 21 h 49 min |
| 2026-06-11 19:09 UTC | Texas - Spectrum Outage | resolved | minor | 3 h 35 min |
| 2026-05-29 21:22 UTC | Los Angeles Towerstream OTT Outage | resolved | minor | 2 h 07 min |
| 2026-05-25 15:02 UTC | Users are experiencing issues accessing VCO options. | resolved | major | 3 h 22 min |
| 2026-05-22 14:37 UTC | Updating Resolved Las Vegas Outage | resolved | critical | 1 min |
| 2026-05-22 08:22 UTC | Las Vegas Network Outage | resolved | critical | 3 h 36 min |
| 2026-04-29 00:32 UTC | Frontier Outage - Los Angeles Area | resolved | minor | 3 h 30 min |
| 2026-03-24 12:30 UTC | Dallas Network Interruption | resolved | major | 4 h 39 min |
| 2026-02-18 12:47 UTC | Las Vegas Network Outage | resolved | critical | 3 h 50 min |
| 2026-02-04 23:00 UTC | OneCentral Portal Scheduled Maintenance | resolved | maintenance | 5 h 52 min |
| 2026-02-02 18:18 UTC | Frontier Network Los Angeles Outage | resolved | major | 9 h 44 min |
| 2026-01-22 21:32 UTC | Microsoft Office365 Issues | resolved | minor | 24 h 23 min |
| 2026-01-22 21:28 UTC | Advisory - Winter Storm Fern | resolved | none | 5 d 4 h |
| 2026-01-15 01:47 UTC | Verizon Wireless Outage | resolved | none | 13 h 13 min |
| 2025-12-04 19:01 UTC | Los Angeles Market Slow Internet Event | resolved | minor | 22 h 44 min |
| 2025-11-15 06:24 UTC | Las Vegas Network Outage | resolved | critical | 17 h 08 min |
| 2025-09-09 05:31 UTC | Los Angeles Routing Issue | resolved | major | 36 min |
| 2025-08-25 05:59 UTC | Los Angeles Hardware Outage | resolved | minor | 13 h 11 min |
| 2025-08-21 20:19 UTC | Frontier Outage - Los Angeles Area | resolved | minor | 22 h 55 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch TPx Communications with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"tpx-communications"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}