Resolved issues

• [#3063] Fix a problem in the ping checker when the threshold was set to 100% packet loss. (fixed)
• [#3196] The alerting status icons in the rule list now are coherent when a folder is inactive. (fixed)
• [#2580] Removed all prototype code from our web site. (fixed)
• [#3186] The check now button on the mobile site works again (fixed)
• [#3072] The connect checker can now match a 'welcome' string if returned by the server. (fixed)
• [#3043] Help desk cases without a category appear in the list now. (fixed)
• [#3059] The refresh every NN minutes option is back in the status dashboard. (fixed)
• [#3218] The error-since field in the API and mobile site is now given in the time zone of the user. (fixed)
• [#3096] Our ping checker now records the target IP it was using (in case of round-robin DNS). (fixed)
• [#3119] The connect checker can now write an arbitrary string to the opened socket in each check. (fixed)
• [#3046] The resolve time for a type ping check is now reported correctly too. (fixed)
• [#3065] Access to sub-accounts can now be granted much easier. (fixed)
• [#3091] A dash is now allowed in POSTed variable names. (fixed)
• [#3070] Better handling of minimum checkpoint selection in the rule settings. (fixed)
• [#3062] You can now select a default set of monitoring stations in the preferences. (fixed)
• [#3080] The plugin checker can now call scripts over secure HTTPS connections. (fixed)
• [#3149] We now use jQuery directly from Googles hosted ajaxlibs site to improve caching. (fixed)
• [#2884] The logviewer shows whether checks were done in maintenance mode. (fixed)
• [#3041] We now allow duplicate contacts to facilitate more control on some types of duty-schedules. (fixed)
• [#2643] There is a JavaScript error on the security scan scheduler page. (fixed)
• [#2980] Correct subscription was not shown for some reseller subaccounts. (fixed)
• [#3146] The message log now displays explanational hovers on the status icons. (fixed)
• [#2846] After a vulnerability scan we now also send an email when there were only issues resolved. (fixed)

Time of maintenance window:
October 30, 2008 starting at 12:00 AM CST to October 30, 2008 ending at 2:30 AM CST
Estimated amount of down time:
Most likely you will experience no more than 20 minutes of down time.
Description of maintenance:
The purpose of the power maintenance is to upgrade the distribution panels throughout our data center. This is important in maintaining a reliable power infrastructure, and is merely a pro-active measure to ensure power reliability.

Status: Scheduled Maintenance
Reason: Network Upgrades
Location: Melbourne Data Centre Locations Only
Date: Friday, 17th October 2008
Times: 00.00am - 01.00am local time

The two Core switches SV01-RIALM1-AS1 & SV01-RIALM1-AS2 will be upgraded to provide future growth capabilities for client connections. The redundancy offered to clients in all locations will also be tested during this period to ensure immediate failover of transit services.

Status: Scheduled Maintenance
Reason: Network Upgrades
Location: Melbourne Data Centre Locations Only
Date: Thursday, 16th October 2008
Times: 05.00am - 06.00am local time

"As part of redundancy strategies, an additional fibre circuit has been installed and requires to be connected to Core Switches SV01-RIALM1-AS1 & SV01-RIALM1-AS2. Additionally, all fibre circuits to Optus, Securiton and Enspire will need be relocated to a fibre tray during this period.

Status: Scheduled Maintenance
Reason: Network Upgrades
Date: Saturday, 20th September
Times: 00.00am - 04.00am local time

"In addition to the upgrades that are being performed on this occasion, we will also take this opportunity to migrate to to new routing equipment, and implementing further layer 2 networking changes to facilitate our upgrades.

• [#2786] Submitting a new helpdesk case could suggest FAQ's for different languages. (fixed)
• [#2778] The status icons in the rule overview are now consistent. (fixed)
• [#2633] In the logviewer sometimes a different timezone is shown. (fixed)
• [#2761] The custom reports can now include a list of rules for your reference. (fixed)
• [#2815] We now have a checkpoint in India (fixed)
• [#3036] We now have a monitoring station in Japan. (fixed)
• [#2817] We now have a checkpoint in South Africa. (fixed)
• [#2972] An extra checkpoint could be selected when using both 'master' and a checkpoint selection. (fixed)
• [#2099] You can now directly select 'Maintenance now' from the actions menu in the rule overview. (fixed)
• [#2873] When you had only viewer rights to a specific folder in someones account, selecting [all rules] did not work. (fixed)
• [#2199] The number of rules in your subsciption is shown in a better way. (fixed)
• [#2541] The German date format is wrongly used in some places in the site. (unable to duplicate)
• [#2855] The performance chart and logviewer now also show the resolve time if applicable. (fixed)

------------
Start of maintenance: 10:47 UTC
End of maintenance  : 11:57 UTC
------------

People using this station as a primary master may see an effect in the performance graphs since the services of this checkpoint were taken over by other machines on our network. This server is also our primary gateway for delivering pager (not SMS) messages, but this service was taken over automatically by a backup system. SMS alerting was not affected at all.

Maintenance Details

Location: TPA (Tampa)
Date: 08-31-2008
Time: 00:00-02:00 Eastern
Impact: Brief outage, less than 10 minutes expected.
Device: core router
Reason: Permanent CAM repartitioning for additional IP routes. Reload is required.

• It is now possible to restrict a rule to a subset of our stations.
• New IMAP and POP3 checkers that are able to do SSL and a send a round-trip test message.
• New DNS checkers with many more features.
• In many cases, the log viewer will now also show the DNS resolve performance for a check.
• The web site uses a more flexible subscription model now.
• For resellers it is now possible to use an applet to access their subaccounts.

In addition, the these smaller issues were resolved:

During the two month monitoring period, one of WatchMouse's monitoring stations tried to access the homepage of the sites every five minutes. Sites were expected to download within 4 seconds without any errors. Combining the errors, speed (load time) and availability measurements, WatchMouse calculated a Site Performance Index 'SPI' for each of the sites. An SPI of ≤1,000 represents a ‘well performing' site, 1,001 - 1,999 is regarded as ‘acceptable', while a score of above 2,000 represents a site with ‘serious user issues'.

During the two month monitoring period, one of WatchMouse's monitoring stations tried to access the homepage of the sites every five minutes. Sites were expected to download within 4 seconds without any errors. Combining the errors, speed (load time) and availability measurements, WatchMouse calculated a Site Availability Index (SPI) for each of the sites. An SPI of ≤1,000 represents a ‘well performing' site, 1,001 - 1,999 is regarded as ‘acceptable', while a score of above 2,000 represents a site with ‘serious user issues'.

• [#2743] Adding a description in a custom report results in an error. (fixed)
• [#2357] Links in performance chart can point to a different log entry. (fixed)
• [#2656] There is a JavaScript error on the my subscription page. (unable to duplicate)
• [#2742] The logviewer now shows some more details of a check (fixed)