It's stable. I wouldn't say any application is without bugs, but I haven't seen many. We had issues once or twice, but it was mostly with browser caching. There haven't been any major issues, but there were improvements that could be made in a couple of areas. They were always happy to listen to us. They had their product teams, product owners, and product managers listen to our feedback. They would slowly take the right feedback and try to implement some of the features we wanted. They always ask us, "What is your priority? What will make the best impact for you as a customer?" We give our honest feedback. When we say what we need, they know that many other customers will love it.

They were also really good with Log4j vulnerabilities. They came back with a fix less than two days after that came out. We had to turn off the services, but it was all good because [Runscope] didn't have an immediate impact. It was the performance container. They had some vulnerabilities because the original JMeter uses some of those Log4j packages. They had to fix the log of JMeter and then update their container.

The solution is quite stable. There were some issues that impacted us a couple of months ago. There was an incident in which they did an upgrade, and we weren't able to execute the load for four hours.

The stability has absolutely gotten better over the years. They had some challenges when they initially migrated the platform to GCP, but most of those were resolved. Overall, they have very high availability for their platform. If there's an issue, they have a status page where they publish updates to keep customers in the loop. 

If you email their support team or open a ticket through the application, they're always very quick to respond when there's a more global uptime issue or something like that. Overall, they have very high availability.

I would rate the stability a six out of ten. It's good. But one suggestion – people tend to rate based on cost these days. Because of that pricing, there are a lot of other new technologies on the market. That's why some people integrate BlazeMeter with an Application Performance Monitor (APM) tool, like Elastic Search or Elastic module. You can pull anything, even CPU utilization or memory usage, by installing agents.

It's actually really good.  

BlazeMeter is pretty solid. The only complaint is performance. When we get massive tests, we run into some issues.

Stability-wise, I rate the solution a seven out of ten.

The solution is very stable. We had a few issues with users getting 404 errors recently, but that's the first time we have encountered any problems in three quarters. 

BlazeMeter has been stable without downtime, and any performance issues are usually linked to the tested application, not BlazeMeter.

Stability-wise, I rate the solution an eight out of ten since my organization is still streamlining things at our end.

It is a stable solution. When we compare BlazeMeter with other tools in the market, I can say that the solution's overall performance has also been very good in our company.

The product is stable.

I rate the solution’s stability a seven out of ten.

I haven't noticed any stability issues with BlazeMeter so far. 

I didn't get much opportunity to work on the tool, but as per my experience, I can say that BlazeMeter serves as an alternate tool whenever my company faces some hurdles or challenges with the JMeter and k6. To record the scripts, I use BlazeMeter as an extension. With BlazeMeter, it is very easy to identify if a request belongs to an application or not, and in the initial phase itself, we can neglect the requests that don't belong to the application. In BlazeMeter, depending upon the requests, users can select a particular domain.

It is very stable. We haven't seen any instability or unavailability issues so far.

The load testing time in BlazeMeter is too high since, in our company, we have seen that it takes four to five minutes to do an entire load testing process, and after that, we run the tests, which is a big problem for us.

Stability-wise, I rate the solution a five out of ten.

I don't recall having any issues with its stability. I'm extremely satisfied with that.

BlazeMeter is a stable solution.

It's stable. Sometimes we do face issues, but they are understandable things.

Every month or two months, something will happen in the back end. The UI will say, for example, that performance testing is down due to this or that reason, and that they are fixing it. Sometimes it affects our testing. We will be in a demo or in a call with our stakeholders where we are presenting and something will be down.

We will raise a support ticket and they will say they are analyzing it and fixing it. They won't take much time, but at that time, it's a pain point. But it happens in all tools. Because it is a cloud tool it's expected, but it's not happening very frequently, so we are happy with it.

It has been stable so far as per our company's user's usage.

We've found the stability to be reliable. We're not running into any performance issues at all. There are no bugs or glitches. It doesn't crash or freeze. 

There were some minor issues with stability.

The stability is good. 

This is a cloud-based solution. I've never really had any trouble with it.

Stability was great; no issues.

Occasionally, we have long wait times or trouble starting tests.

We encountered no stability issues in using it.

We have found the solution to be stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

So far I haven't encountered any issues so it seems very stable to me.

We did not encounter any stability issues.

It is stable. 

This solution seems very stable.

We have not encountered any particular stability issues.

The application has been stable in most of our tests to date. We experience the odd bug, but BlazeMeter are quick to resolve any issues.

We had some stability issues; sometimes the load generators do not start at all.

We had stability problems several times and we lost all our credits.