Vendor Status Watch

← all vendors

Ubiquiti status history

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

0incidents, last 30 days
2incidents, last 90 days
5incidents on record
Incidents per week, last 12 weeks:
Get Ubiquiti alerts in your Slack — free templateRSS for Ubiquiti

How long do Ubiquiti incidents last?

3.5 hmedian incident duration5 measured
21.4 h90th percentile1 in 10 ran longer
2.2 hmedian, major/critical only1 incident

From 5 incidents with a vendor-posted start and resolve time. Longest on record: Multiple Services: Partial Outage — 21.4 h (2025-10-20 09:51 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 (5)

StartedIncidentStatusImpactDuration
2026-07-24 11:32 UTCMultiple Services: Degraded Performanceresolvedmajor2 h 15 min
2026-07-16 09:05 UTCIncreased CloudFront 5xx Errorsresolvednone2 h 26 min
2026-02-26 17:41 UTCIntermittent Connectivity in EU Regionresolvednone8 h 42 min
2025-10-20 09:51 UTCMultiple Services: Partial Outageresolvedminor21 h 22 min
2025-09-24 10:25 UTCRemote Access and UI Account Service Degraded Performanceresolvedminor3 h 31 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 Ubiquiti with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "ubiquiti"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}