AlertFox is part of the Ipswitch family of tools and services. Learn More »


In order to ensure the quality of the back-end operations, AlertFox will be offline for a short period starting at 11:00am GMT on Thursday, March 6th.  Estimated downtime is 30-45 minutes. This will affect the user interface on as well as scheduled measurements and notifications. [Update] It took us a little longer than expected,

While our administrators are dealing with the AlertFox database (in order to overcome potential performance issues) some customers report failures when accessing reports or running “Test Now”. We are aware of this problem and are trying to fix it. Please refer to this post for updates. [Update] The underlying cause has been identified and a

Last night we had a database storage issue that has affected the storage of classic results for some customers between 0:00 and 6:00am CET on 2014/1/29. iMacros results and alerting were not affected.    

30 minutes after detecting missing iMacros measurements, our system is within normal limits again. We apologize for this incident. Classic measurements have not been affected.

[Update] Upgrading iDrone backend

Wednesday, 27 November 2013 by

We have received reports on missing iDrone sensors’ results. The dev crew has identified a database related performance bottleneck and will assign more resources to handle the load. We’ll update this ticket accordingly. [Update 15:08: Still working on it] [Update 16:25: New backend processes are in place. Let us know if you experience any more

We are currently experiencing a problem with handling iMacros sensors’ results as they come in from our measurement servers.  As a consequence, we are not able to detect measurement failures and send appropriate notifications. You will notice this issue as “gaps” in the sensor’s logs and as “white spots” in the tactical overview report. Classic

False alarms due to disk issues

Wednesday, 11 September 2013 by

In the last week, two of our monitoring stations experienced disk problems that have resulted in several false alarms for iMacros sensors. As the error message referred to a local file, many of you have already concluded that this was not a problem related to your websites: We apologize for the malfunction of our service.

An HTTP test at AlertFox involves more than simply pinging port 80 (or  443). Instead, our test servers initiate a real HTTP connection. That’s why we are able to check for keywords on the served page. It has now come to our attention that the user-agent used by our HTTP test may cause servers to

We are sorry to report some unscheduled downtime of our real browser transaction monitoring service. The reason was a problem with one of the hard disks. Unfortunately we did not detect it before it happened, so all we could do was repair the system after the damage had occurred. As a result, your account might