Vendor Status Watch

← all vendors

Roam status history

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

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

How long do Roam incidents last?

2.2 hmedian incident duration6 measured
5.0 h90th percentile1 in 10 ran longer
2.8 hmedian, major/critical only5 incidents

From 6 incidents with a vendor-posted start and resolve time. Longest on record: AWS incident in me-central-1 impacting some customers — 9.1 days (2026-03-10 16:31 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 (6)

StartedIncidentStatusImpactDuration
2026-07-20 15:30 UTCChat messages and invites delayedresolvedmajor0 min
2026-07-14 14:54 UTCRoam Lobby pages are slow to load and sometimes errorresolvedmajor2 h 46 min
2026-03-10 16:31 UTCAWS incident in me-central-1 impacting some customersresolvedmajor9 d 2 h
2026-02-10 20:45 UTCNetwork Error Connecting to Roamresolvedmajor1 h 40 min
2025-10-08 15:53 UTCRoam Lobbies Are Unavailableresolvedminor1 h 26 min
2025-08-26 07:00 UTCRoam Chat Message Delivery Impairedresolvedmajor5 h 02 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 Roam with the template

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

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