BlazeMeter status history
Current state: operational — “All Systems Operational” per https://status.blazemeter.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do BlazeMeter incidents last?
From 9 incidents with a vendor-posted start and resolve time. Longest on record: Capacity Issues with Google Public Locations — 6.0 days (2026-05-26 15:52 UTC). Excluded, never estimated: 1 scheduled maintenance. 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 (10)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-15 14:59 UTC | Load Engine Availability Issues in Google, Iowa | resolved | none | 1 h 46 min |
| 2026-05-26 15:52 UTC | Capacity Issues with Google Public Locations | resolved | none | 6 d 0 h |
| 2026-05-07 21:05 UTC | New User Registrations are currently broken | resolved | none | 13 h 37 min |
| 2026-03-30 14:51 UTC | Issue with JMeter Plugins Repository Certificate | resolved | minor | 3 h 38 min |
| 2026-01-21 14:36 UTC | Some Dedicated IPs Encountering Issues when Running Tests | resolved | minor | 1 h 14 min |
| 2025-10-15 07:22 UTC | Issues with Starting or Stopping Tests due to database maintenance. | resolved | maintenance | 1 h 30 min |
| 2025-10-07 15:17 UTC | mock.blazemeter.com was briefly displaying a 404 when navigating to it. | resolved | none | 1 h 16 min |
| 2025-10-03 21:17 UTC | The US Illinois Location for API Monitoring is offline | resolved | minor | 1 h 35 min |
| 2025-09-24 11:29 UTC | DATA Processing delays in Blazemeter | resolved | minor | 4 h 58 min |
| 2025-09-11 22:10 UTC | Data Processing Delays Causing Long Test Shutdown Times | resolved | minor | 1 h 46 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 BlazeMeter with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"blazemeter"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}