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

BLOG

On Friday the 22nd, between 15:38 and 16:43 UTC, we noticed an unexpected error occurred on AlertFox backend. Some transaction sensors (iMacros) results might not have been saved during that period of time. We modified some settings on our side to prevent this happening again. All our apologies for any inconvenience this may have caused. Classic was left unaffected.

As promised, here’s an update on the issue we had on April 30th. Between 8:40 GMT and 22:00 GMT, one of our measurement components failed which took classic monitoring down. Being a web monitoring company, we do not fail to notice the irony that our monitoring took very long to bring this problem to our

As announced on Twitter (cf. here, here, and here), the AlertFox service experienced some technical difficulties. In your “Tactical Overview” the problem may show up as missing results (cf. screenshot).   So here’s what happened and how our system was affected: Our site had a problem connecting to the database storing the results of your

Partial Outage on Feb 02, 2016

Wednesday, 03 February 2016 by

As announced via Twitter, the AlertFox infrastructure experienced a technical issue yesterday. This is to update you on the details: The AlertFox control panel was unavailable between 05:20 GMT and 14:55 GMT. During that interval, no notifications were sent. During that interval, no classic measurements were recorded. Additionally, no classic measurements were recorded for the

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

TOP