Vendor Status Watch

← all vendors

Wallarm status history

Current state: partial outage — “Partial System Outage” per https://status.wallarm.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

3incidents, last 30 days
9incidents, last 90 days
52incidents on record
Incidents per week, last 12 weeks:

How long do Wallarm incidents last?

44 minmedian incident duration52 measured
4.7 h90th percentile1 in 10 ran longer
34 minmedian, major/critical only26 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-14 18:48 UTCService disruption in US regionresolvedcritical13 min
2026-09-14 15:01 UTCService disruption in US regionresolvedmajor9 min
2026-08-28 03:34 UTCService disruption in US regionresolvedmajor35 min
2026-08-11 11:24 UTCService disruption in EU regionresolvedminor6 min
2026-08-03 02:45 UTCService disruption in EU and US regionresolvedmajor27 min
2026-07-14 09:42 UTCService disruption in EU regionresolvedmajor27 min
2026-07-04 05:57 UTCService disruption in EU regionresolvedminor24 min
2026-06-26 03:00 UTCService disruption in EU regionresolvedmajor31 min
2026-06-20 06:00 UTCService disruption in EU regionresolvedminor21 min
2026-06-06 05:57 UTCService disruption in EU regionresolvedmajor24 min
2026-06-04 07:39 UTCService disruption in EU regionresolvedmajor13 min
2026-06-03 03:03 UTCService disruption in EU regionresolvedmajor22 min
2026-06-02 13:25 UTCService disruption in USresolvedminor13 min
2026-06-02 11:21 UTCService disruption in EU regionresolvedmajor3 h 52 min
2026-06-02 05:10 UTCService disruption in EU regionresolvedmajor47 min
2026-06-01 10:21 UTCService disruption in EU regionresolvedmajor33 min
2026-05-29 05:09 UTCService disruption in EU regionresolvedmajor1 h 20 min
2026-04-15 01:11 UTCService disruption in US regionresolvedminor3 h 26 min
2026-04-14 11:04 UTCService disruption in EU and US regionresolvedminor51 min
2026-04-07 06:29 UTCService disruption in EU and US regionresolvedmajor2 h 35 min
2026-04-02 15:51 UTCService disruption in EU regionresolvedminor44 min
2026-03-31 15:02 UTCService disruption in EU regionresolvedminor2 h 17 min
2026-03-24 17:29 UTCService fully restored in EUresolvedminor19 min
2026-03-14 05:40 UTCService disruption in US regionresolvedmajor2 h 35 min
2026-03-09 08:50 UTCService disruption in US regionresolvedmajor22 min
2026-03-06 16:52 UTCService disruption in EU and US regionresolvedminor7 h 23 min
2026-02-24 19:04 UTCService fully restored in EUresolvedmajor30 min
2026-02-20 20:45 UTCService disruption in US regionresolvedminor41 min
2026-02-18 12:26 UTCService disruption in USresolvednone21 min
2026-02-17 14:40 UTCService fully restored in US and EUresolvedmajor1 h 44 min
2026-02-13 16:10 UTCService disruption in USresolvedminor45 min
2026-02-11 13:22 UTCService fully restored in in EU and USresolvednone14 min
2026-01-30 18:08 UTCService Disruption in US regionresolvedminor2 h 13 min
2026-01-26 05:20 UTCService disruption in USresolvedminor1 h 31 min
2026-01-22 17:16 UTCService disruption in USresolvedminor5 h 05 min
2026-01-14 11:45 UTCService Disruption in US and EU regionresolvedminor4 h 49 min
2025-12-11 15:34 UTCService fully restored in EUresolvednone9 min
2025-12-01 05:56 UTCService disruption in US regionresolvedminor33 min
2025-12-01 00:10 UTCService disruption in EUresolvedminor5 h 24 min
2025-11-24 16:25 UTCService fully restored in USresolvedmajor55 min
2025-11-13 14:48 UTCService fully restored in USresolvednone2 h 40 min
2025-11-10 20:19 UTCService Disruption in US regionresolvedminor2 h 05 min
2025-11-10 00:29 UTCService Disruption in US regionresolvedminor13 h 11 min
2025-11-09 15:55 UTCIssue mitigated in USresolvedmajor4 h 43 min
2025-11-07 16:55 UTCService Disruption in US regionresolvedmajor59 min
2025-11-06 03:09 UTCService disruption in EU regionresolvedmajor1 h 26 min
2025-11-01 12:17 UTCService disruption in US regionresolvedminor1 h 25 min
2025-10-30 21:25 UTCService disruption in US regionresolvedmajor17 min
2025-10-30 20:12 UTCService disruption in US regionresolvedmajor22 min
2025-10-30 12:27 UTCService fully restored in USresolvedminor26 min
2025-10-30 04:54 UTCService disruption in US regionresolvedmajor1 h 26 min
2025-10-28 10:12 UTCService fully restored in US regionresolvedmajor3 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
}