Vendor Status Watch

← all vendors

Packet status history

Current state: operational — “All Systems Operational” per http://status.packet.net (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
3incidents, last 90 days
30incidents on record
Incidents per week, last 12 weeks:

How long do Packet incidents last?

80 minmedian incident duration30 measured
4.5 h90th percentile1 in 10 ran longer
81 minmedian, major/critical only7 incidents

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)

StartedIncidentStatusImpactDuration
2026-08-17 15:38 UTCSV Metro Connectivity Issuesresolvedcritical1 h 32 min
2026-06-30 03:59 UTCAT INCIDENT INC0258173 MC DOWNresolvedmajor1 h 21 min
2026-06-25 00:11 UTCPA Primary Shared Interconnection Connectivity Issueresolvedminor1 h 56 min
2026-05-09 06:10 UTCDown Fabric circuit on FR Metroresolvednone41 h 24 min
2026-04-14 16:25 UTCBrief Network Disruption – Chicago (CH3)resolvedminor22 min
2026-04-06 08:16 UTCPA Shared Interconnection Connectivity Issueresolvedminor6 min
2026-02-06 12:34 UTCSV Metro Isolationresolvedmajor1 h 13 min
2026-01-28 16:33 UTCPacket Loss DC And SV Metroresolvednone0 min
2026-01-22 11:07 UTCDC10 Network Connectivity Issueresolvedminor2 h 04 min
2026-01-21 12:20 UTCMetadata service degradation in some facilitiesresolvednone2 h 13 min
2026-01-20 23:38 UTCSY4 Network Connectivity Issueresolvednone17 min
2026-01-15 07:05 UTCSV15 and SV16 outageresolvedcritical59 min
2025-12-23 16:14 UTCCustomer provisioning issue in Silicon Valley Metroresolvednone59 min
2025-12-19 07:57 UTCDC1 | Equinix Maintenance CHG0111322resolvednone2 h 03 min
2025-12-02 02:47 UTCDC13 Network Connectivity Issueresolvedminor1 h 20 min
2025-11-18 14:26 UTCMetal API Issueresolvedcritical5 h 25 min
2025-11-14 12:04 UTCPrimary and Secondary Metal port impactedresolvedminor46 min
2025-10-21 10:59 UTCConnectivity Issue Multiple Metrosresolvedmajor4 h 04 min
2025-10-17 13:12 UTCEquinix Console Impactresolvedmajor40 min
2025-10-16 18:55 UTCConnectivity issue in Sao Paulo Metroresolvednone1 h 06 min
2025-10-11 00:27 UTCTY11 Rack: rk09.p01.ty11 Downresolvedminor3 h 49 min
2025-09-30 02:07 UTCPrimary Shared Fabric Metal Port impactedresolvedminor6 h 47 min
2025-09-23 20:56 UTCPower issue - Madrid Metroresolvednone53 min
2025-09-23 02:34 UTCNY Network Connectivity Issueresolvedminor1 h 41 min
2025-09-19 18:56 UTCConnectivity issues in London Metroresolvednone47 min
2025-09-19 05:19 UTCMadrid - MD2 Network Connectivity Issueresolvednone28 min
2025-09-03 18:46 UTCSP Metro Customer Connectivity Lossresolvednone3 h 37 min
2025-08-28 02:19 UTCPrimary Shared Interconnection impactedresolvedminor4 h 27 min
2025-08-27 04:15 UTCSG Metro Customer Connectivity Lossresolvednone0 min
2025-08-22 10:38 UTCIncident due to emergency maintenance by a third-party provider impacting Equinix customers.resolvednone1 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
}