Vendor Status Watch

← all vendors

MacStadium status history

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

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

How long do MacStadium incidents last?

3.4 hmedian incident duration5 measured
23.2 h90th percentile1 in 10 ran longer
3.2 hmedian, major/critical only4 incidents

From 5 incidents with a vendor-posted start and resolve time. Longest on record: Customer Portal Incident: Support Center & Bare Metal Pages — 23.2 h (2025-09-15 14:23 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-09-09 19:13 UTCHardware Outage in Atlantaresolvedmajor3 h 02 min
2026-04-22 18:36 UTCLas Vegas VPC and ASAv Partial Outageresolvedmajor3 h 21 min
2026-04-21 21:32 UTCVPC and ASAv Partial Outageresolvedmajor10 min
2025-10-20 15:32 UTCCustomer Portal Ticketing System Incidentresolvedminor6 h 03 min
2025-09-15 14:23 UTCCustomer Portal Incident: Support Center & Bare Metal Pagesresolvedmajor23 h 14 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 MacStadium with the template

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

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