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


We mentioned some potential unwanted side effect in our previous blog post from 20th of September . Unfortunately, a very limited set of users received alerts raised following the malfunctions we observed in the cloud. Classic sensors alerting was not triggered and operation was stable throughout the whole instability period. Transaction monitoring failed in some cases,

On Sunday 20th of September, from 10:00AM(UTC) to 15:30PM(UTC), our cloud platform provider experienced several issues. We expect little to no side effect. However, please keep this event in mind should you have noticed anything unusual about your iMacros sensors. Thank you for your understanding.

The AlertFox backend currently has problems performing transaction measurements. This is related to some performance degradation in our cloud, and our provider (Amazon) is currently working to fix this asap. We apologize for any inconvenience this may cause. Update: Amazon confirmed everything is back to normal, and AF can resume full speed service. We expect little to

The AlertFox backend currently has problems performing transaction measurements. Staff is working on identifying and rectifying the cause. Classic sensors are not affected. Update 1: The reason for our problems is an issue with the Amazon infrastructure we’re using. iDrone sensors are not affected Update 2: Only minutes after Amazon sent a promising update, our

Over the last several hours, classic measurements’ results (HTTP, HTTPS, DNS, FTP) intermittently fail to be stored in some customers’ accounts. This leads to missing results and alerts -  at least until a next measurement is able to properly register a result. A quick fix is in place already, and we’re working on a full

An unhandled database exception caused the alerting service to stop.  It took years before this issue surfaced, and today was the day. The issue has been resolved and alerting works fine again. Clearly, alerting is one of the key features of AlertFox so this issue is embarrassing and we will make sure it does not happen

Starting next week, we will update our classic sensors’ back-end architecture to match our transaction (iMacros) sensors. Besides improved scalability and performance, this will allow for future feature extensions (like additional monitoring locations).

No action is required from our customers.

When we announced a back-end change to our HAR engine, we told you that clear-text HAR files for SSL connections were a possible future extension. Today we’re happy to tell you that we will be rolling out exactly this feature within the next weeks and across all regions. Just as with HTTP connections today, your

2015-04-01 iDrone Back-end Update

Tuesday, 31 March 2015 by

On Wednesday, April 1st, 2015, we will update our iDrone back-end. The change is expected to be completely transparent.   [Update] The operation went smoothly. Let us know in case you encounter any problem.

Backend Update: New SMS Provider

Friday, 13 March 2015 by

After receiving reports about missing or heavily delayed SMS notifications, our team has changed the SMS provider for the AlertFox backend. Our new provider has a reputation for top notch reliability and allows for future extensions of our alerting features (e.g. phone alerts). Note that the notification SMS’s sender ID (+1 781-209-6001) will differ from