Live  /  BlazeMeter  /  Incident

BlazeMeter: Load Engine Availability Issues in Google, Iowa

BlazeMeter · blazemeter.comResolved2026-09-15 14:59 UTC
Public — what happened

Summary

BlazeMeter reported problems getting load engines in its Google public location in Iowa, beginning on 2026-09-15 at 14:59 UTC. The company said tests run from that location could be slow to boot or might not start correctly, and it attributed the trouble to a capacity shortage on Google's end. BlazeMeter advised customers to steer clear of the Google Iowa location for now and consider AWS or Azure locations instead. The incident was marked as being monitored, with a resolution time of 16:47 the same day.

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.