Reblaze is quite stable. During the initial phase, there were a few instances where the system went down, but that was mainly because both Reblaze and we were still learning about our environment, their support, and scalability. 

However, once that phase was behind us, there haven't been any major issues due to Reblaze. We also have a kill switch as a backup. If we notice the load increasing and Reblaze may struggle to handle it, we can bypass Reblaze and direct traffic straight to us. Though we haven't used the kill switch yet, we have had no issues so far. It's been a year, and we plan to renew our contract with them once the current license expires. Overall, we are happy with the product.

We haven't encountered any failures. It is a highly resilient product that can handle significantly larger workloads and high volumes of traffic with ease.

We had no real-time issues ever, due to the system. We had problems because of our programming team, upgrading the components without testing it first, moving it to production, and then something would be blocked because it was not tested.

For example, we had false positives when Google Chrome was upgraded and specifically asked for new parameters or was doing more validation. Then, we were stuck and we needed to do more whitelisting.

It's 100 percent stable. We haven't ever had any problem with the stability of the product.

It is very stable. We have not noticed any bugs or issues with it.

Up until now, I haven't had any problems with this product. It is very stable. The moment I installed it, everything ran smoothly and I could forget about everything. Unlike other programs I have worked on before. 

The stability is very good. I can't say it is error-free, but Reblaze knows how to find an error quickly and successfully.

The stability is perfect.

There is no downtime. Up until now, the stability has been good. It's a good solution. 

This is a stable solution.