Wallarm status history
Current state: partial outage — “Partial System Outage” per https://status.wallarm.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Wallarm incidents last?
From 52 incidents with a vendor-posted start and resolve time. Longest on record: Service Disruption in US region — 13.2 h (2025-11-10 00:29 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 (52)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-14 18:48 UTC | Service disruption in US region | resolved | critical | 13 min |
| 2026-09-14 15:01 UTC | Service disruption in US region | resolved | major | 9 min |
| 2026-08-28 03:34 UTC | Service disruption in US region | resolved | major | 35 min |
| 2026-08-11 11:24 UTC | Service disruption in EU region | resolved | minor | 6 min |
| 2026-08-03 02:45 UTC | Service disruption in EU and US region | resolved | major | 27 min |
| 2026-07-14 09:42 UTC | Service disruption in EU region | resolved | major | 27 min |
| 2026-07-04 05:57 UTC | Service disruption in EU region | resolved | minor | 24 min |
| 2026-06-26 03:00 UTC | Service disruption in EU region | resolved | major | 31 min |
| 2026-06-20 06:00 UTC | Service disruption in EU region | resolved | minor | 21 min |
| 2026-06-06 05:57 UTC | Service disruption in EU region | resolved | major | 24 min |
| 2026-06-04 07:39 UTC | Service disruption in EU region | resolved | major | 13 min |
| 2026-06-03 03:03 UTC | Service disruption in EU region | resolved | major | 22 min |
| 2026-06-02 13:25 UTC | Service disruption in US | resolved | minor | 13 min |
| 2026-06-02 11:21 UTC | Service disruption in EU region | resolved | major | 3 h 52 min |
| 2026-06-02 05:10 UTC | Service disruption in EU region | resolved | major | 47 min |
| 2026-06-01 10:21 UTC | Service disruption in EU region | resolved | major | 33 min |
| 2026-05-29 05:09 UTC | Service disruption in EU region | resolved | major | 1 h 20 min |
| 2026-04-15 01:11 UTC | Service disruption in US region | resolved | minor | 3 h 26 min |
| 2026-04-14 11:04 UTC | Service disruption in EU and US region | resolved | minor | 51 min |
| 2026-04-07 06:29 UTC | Service disruption in EU and US region | resolved | major | 2 h 35 min |
| 2026-04-02 15:51 UTC | Service disruption in EU region | resolved | minor | 44 min |
| 2026-03-31 15:02 UTC | Service disruption in EU region | resolved | minor | 2 h 17 min |
| 2026-03-24 17:29 UTC | Service fully restored in EU | resolved | minor | 19 min |
| 2026-03-14 05:40 UTC | Service disruption in US region | resolved | major | 2 h 35 min |
| 2026-03-09 08:50 UTC | Service disruption in US region | resolved | major | 22 min |
| 2026-03-06 16:52 UTC | Service disruption in EU and US region | resolved | minor | 7 h 23 min |
| 2026-02-24 19:04 UTC | Service fully restored in EU | resolved | major | 30 min |
| 2026-02-20 20:45 UTC | Service disruption in US region | resolved | minor | 41 min |
| 2026-02-18 12:26 UTC | Service disruption in US | resolved | none | 21 min |
| 2026-02-17 14:40 UTC | Service fully restored in US and EU | resolved | major | 1 h 44 min |
| 2026-02-13 16:10 UTC | Service disruption in US | resolved | minor | 45 min |
| 2026-02-11 13:22 UTC | Service fully restored in in EU and US | resolved | none | 14 min |
| 2026-01-30 18:08 UTC | Service Disruption in US region | resolved | minor | 2 h 13 min |
| 2026-01-26 05:20 UTC | Service disruption in US | resolved | minor | 1 h 31 min |
| 2026-01-22 17:16 UTC | Service disruption in US | resolved | minor | 5 h 05 min |
| 2026-01-14 11:45 UTC | Service Disruption in US and EU region | resolved | minor | 4 h 49 min |
| 2025-12-11 15:34 UTC | Service fully restored in EU | resolved | none | 9 min |
| 2025-12-01 05:56 UTC | Service disruption in US region | resolved | minor | 33 min |
| 2025-12-01 00:10 UTC | Service disruption in EU | resolved | minor | 5 h 24 min |
| 2025-11-24 16:25 UTC | Service fully restored in US | resolved | major | 55 min |
| 2025-11-13 14:48 UTC | Service fully restored in US | resolved | none | 2 h 40 min |
| 2025-11-10 20:19 UTC | Service Disruption in US region | resolved | minor | 2 h 05 min |
| 2025-11-10 00:29 UTC | Service Disruption in US region | resolved | minor | 13 h 11 min |
| 2025-11-09 15:55 UTC | Issue mitigated in US | resolved | major | 4 h 43 min |
| 2025-11-07 16:55 UTC | Service Disruption in US region | resolved | major | 59 min |
| 2025-11-06 03:09 UTC | Service disruption in EU region | resolved | major | 1 h 26 min |
| 2025-11-01 12:17 UTC | Service disruption in US region | resolved | minor | 1 h 25 min |
| 2025-10-30 21:25 UTC | Service disruption in US region | resolved | major | 17 min |
| 2025-10-30 20:12 UTC | Service disruption in US region | resolved | major | 22 min |
| 2025-10-30 12:27 UTC | Service fully restored in US | resolved | minor | 26 min |
| 2025-10-30 04:54 UTC | Service disruption in US region | resolved | major | 1 h 26 min |
| 2025-10-28 10:12 UTC | Service fully restored in US region | resolved | major | 3 h 38 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 Wallarm with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"wallarm"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}