Vendor Status Watch

← all vendors

BlazeMeter status history

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

1incidents, last 30 days
1incidents, last 90 days
10incidents on record
Incidents per week, last 12 weeks:

How long do BlazeMeter incidents last?

106 minmedian incident duration9 measured
13.6 h90th percentile1 in 10 ran longer
median, major/critical onlynone posted

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)

StartedIncidentStatusImpactDuration
2026-09-15 14:59 UTCLoad Engine Availability Issues in Google, Iowaresolvednone1 h 46 min
2026-05-26 15:52 UTCCapacity Issues with Google Public Locationsresolvednone6 d 0 h
2026-05-07 21:05 UTCNew User Registrations are currently brokenresolvednone13 h 37 min
2026-03-30 14:51 UTCIssue with JMeter Plugins Repository Certificateresolvedminor3 h 38 min
2026-01-21 14:36 UTCSome Dedicated IPs Encountering Issues when Running Testsresolvedminor1 h 14 min
2025-10-15 07:22 UTCIssues with Starting or Stopping Tests due to database maintenance.resolvedmaintenance1 h 30 min
2025-10-07 15:17 UTCmock.blazemeter.com was briefly displaying a 404 when navigating to it.resolvednone1 h 16 min
2025-10-03 21:17 UTCThe US Illinois Location for API Monitoring is offlineresolvedminor1 h 35 min
2025-09-24 11:29 UTCDATA Processing delays in Blazemeterresolvedminor4 h 58 min
2025-09-11 22:10 UTCData Processing Delays Causing Long Test Shutdown Timesresolvedminor1 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
}