Roadmunk status history
Current state: operational — “All Systems Operational” per https://status.roadmunk.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Roadmunk incidents last?
From 6 incidents with a vendor-posted start and resolve time. Longest on record: APAC region is unavailable — 2.8 days (2025-12-19 19:53 UTC). Excluded, never estimated: 19 resolved before started (vendor data error). 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 (25)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-07-22 01:22 UTC | EU and APAC regions are unavailable | resolved | none | 14 h 16 min |
| 2026-07-15 00:38 UTC | EU region is unavailable | resolved | major | 21 min |
| 2026-07-09 15:04 UTC | Degraded performance | resolved | none | 1 min |
| 2025-12-19 19:53 UTC | APAC region is unavailable | resolved | critical | 2 d 19 h |
| 2025-12-04 16:01 UTC | Intermittent Service Interruption | resolved | major | 24 h 08 min |
| 2025-10-20 09:09 UTC | Authentication failing due to widespread provider outage | resolved | critical | 11 h 16 min |
| 2025-09-05 16:06 UTC | Service Degradation in Roadmunk | resolved | minor | — |
| 2025-09-05 16:06 UTC | Investigating Service Downtime in Roadmunk Application | resolved | major | — |
| 2025-09-05 16:06 UTC | Service degradation in Roadmunk | resolved | none | — |
| 2025-09-05 16:06 UTC | This is an example incident | resolved | none | — |
| 2025-09-05 16:06 UTC | Connectivity Issues | resolved | minor | — |
| 2025-09-05 16:06 UTC | Portfolio Roadmaps | resolved | minor | — |
| 2025-09-05 16:06 UTC | 504 Errors Reported in Roadmunk | resolved | critical | — |
| 2025-09-05 16:06 UTC | Identified Issue on Roadmunk Application | resolved | minor | — |
| 2025-09-05 16:06 UTC | Investigating Errors in Roadmunk Application | resolved | critical | — |
| 2025-09-05 16:06 UTC | Identified Issue on Roadmunk Application | resolved | minor | — |
| 2025-09-05 16:06 UTC | Identified Issue on Roadmunk Application | resolved | minor | — |
| 2025-09-05 16:06 UTC | Investigating Errors in Roadmunk Application | resolved | major | — |
| 2025-09-05 16:06 UTC | AUTHENTICATION - Log In Issue | resolved | critical | — |
| 2025-09-05 16:06 UTC | Users Across All Deployments Encountering Unexpected Error | resolved | critical | — |
| 2025-09-05 16:06 UTC | Authentication delays | resolved | minor | — |
| 2025-09-05 16:06 UTC | Some services experiencing degraded performance | resolved | minor | — |
| 2025-09-05 16:06 UTC | Some accounts hitting errors when logging in with SSO | resolved | none | — |
| 2025-09-05 16:06 UTC | Roadmapping not loading | resolved | critical | — |
| 2025-09-05 16:06 UTC | Authentication issues with SSO | resolved | minor | — |
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 Roadmunk with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"roadmunk"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}