Live  /  BlazeMeter  /  Incident

BlazeMeter: Slowness in BlazeMeter

BlazeMeter · blazemeter.comCritical outageResolved2026-09-18 13:17 UTC
Public — what happened

Summary

BlazeMeter reported a critical incident involving slow performance across its service, beginning on 2026-09-18 at 13:09 UTC. The company said its engineering team found what was behind the slowdown, though it did not describe the cause publicly, and made changes to speed things up. BlazeMeter said the interface was responding better afterward and that it was keeping watch to make sure the problem does not return, with the incident marked resolved at 14:26.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach BlazeMeter against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for BlazeMeter: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the BlazeMeter report →

More from BlazeMeter

Covered in The Squid’s Ink, Week 39, 2026, our weekly internet health report.

The full archive is on the BlazeMeter status & history page.

Related: BlazeMeter status & history. SquidGrid is not affiliated with BlazeMeter.