Vendor Status Watch

← all vendors

Apwide status history

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

0incidents, last 30 days
0incidents, last 90 days
3incidents on record

How long do Apwide incidents last?

3.8 hmedian incident duration3 measured
7.2 h90th percentile1 in 10 ran longer
3.8 hmedian, major/critical only3 incidents

From 3 incidents with a vendor-posted start and resolve time. Longest on record: Performance issue on Golive — 7.2 h (2026-02-05 07:46 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 (3)

StartedIncidentStatusImpactDuration
2026-03-10 19:04 UTCOutage on Goliveresolvedcritical1 h 22 min
2026-02-05 07:46 UTCPerformance issue on Golivepostmortemmajor7 h 10 min
2025-11-05 06:20 UTCGolive and Time Squad outagepostmortemcritical3 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 Apwide with the template

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

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