Packet status history
Current state: operational — “All Systems Operational” per http://status.packet.net (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Packet incidents last?
From 30 incidents with a vendor-posted start and resolve time. Longest on record: Down Fabric circuit on FR Metro — 41.4 h (2026-05-09 06:10 UTC). Excluded, never estimated: nothing. 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 (30)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-17 15:38 UTC | SV Metro Connectivity Issues | resolved | critical | 1 h 32 min |
| 2026-06-30 03:59 UTC | AT INCIDENT INC0258173 MC DOWN | resolved | major | 1 h 21 min |
| 2026-06-25 00:11 UTC | PA Primary Shared Interconnection Connectivity Issue | resolved | minor | 1 h 56 min |
| 2026-05-09 06:10 UTC | Down Fabric circuit on FR Metro | resolved | none | 41 h 24 min |
| 2026-04-14 16:25 UTC | Brief Network Disruption – Chicago (CH3) | resolved | minor | 22 min |
| 2026-04-06 08:16 UTC | PA Shared Interconnection Connectivity Issue | resolved | minor | 6 min |
| 2026-02-06 12:34 UTC | SV Metro Isolation | resolved | major | 1 h 13 min |
| 2026-01-28 16:33 UTC | Packet Loss DC And SV Metro | resolved | none | 0 min |
| 2026-01-22 11:07 UTC | DC10 Network Connectivity Issue | resolved | minor | 2 h 04 min |
| 2026-01-21 12:20 UTC | Metadata service degradation in some facilities | resolved | none | 2 h 13 min |
| 2026-01-20 23:38 UTC | SY4 Network Connectivity Issue | resolved | none | 17 min |
| 2026-01-15 07:05 UTC | SV15 and SV16 outage | resolved | critical | 59 min |
| 2025-12-23 16:14 UTC | Customer provisioning issue in Silicon Valley Metro | resolved | none | 59 min |
| 2025-12-19 07:57 UTC | DC1 | Equinix Maintenance CHG0111322 | resolved | none | 2 h 03 min |
| 2025-12-02 02:47 UTC | DC13 Network Connectivity Issue | resolved | minor | 1 h 20 min |
| 2025-11-18 14:26 UTC | Metal API Issue | resolved | critical | 5 h 25 min |
| 2025-11-14 12:04 UTC | Primary and Secondary Metal port impacted | resolved | minor | 46 min |
| 2025-10-21 10:59 UTC | Connectivity Issue Multiple Metros | resolved | major | 4 h 04 min |
| 2025-10-17 13:12 UTC | Equinix Console Impact | resolved | major | 40 min |
| 2025-10-16 18:55 UTC | Connectivity issue in Sao Paulo Metro | resolved | none | 1 h 06 min |
| 2025-10-11 00:27 UTC | TY11 Rack: rk09.p01.ty11 Down | resolved | minor | 3 h 49 min |
| 2025-09-30 02:07 UTC | Primary Shared Fabric Metal Port impacted | resolved | minor | 6 h 47 min |
| 2025-09-23 20:56 UTC | Power issue - Madrid Metro | resolved | none | 53 min |
| 2025-09-23 02:34 UTC | NY Network Connectivity Issue | resolved | minor | 1 h 41 min |
| 2025-09-19 18:56 UTC | Connectivity issues in London Metro | resolved | none | 47 min |
| 2025-09-19 05:19 UTC | Madrid - MD2 Network Connectivity Issue | resolved | none | 28 min |
| 2025-09-03 18:46 UTC | SP Metro Customer Connectivity Loss | resolved | none | 3 h 37 min |
| 2025-08-28 02:19 UTC | Primary Shared Interconnection impacted | resolved | minor | 4 h 27 min |
| 2025-08-27 04:15 UTC | SG Metro Customer Connectivity Loss | resolved | none | 0 min |
| 2025-08-22 10:38 UTC | Incident due to emergency maintenance by a third-party provider impacting Equinix customers. | resolved | none | 1 h 47 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 Packet with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"packet"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}