Tag: System Status Updates

VA, USA Monitoring Location Issue

May 21, 2015 – The Dotcom-Monitor server at VA, USA monitoring location is unavailable for monitoring since 05/21/2015 10:30 PM CST. We’re working with VA’s support for resolution. We will provide more updates on time-to-repair as soon as it becomes available.

Read More ⟩

The server maintenance

May 19, 2015  11:55 AM –  2:00 PM UTC the planned maintenance is scheduled (installing of a new software on a main server), monitoring will be unavailable during this time interval.

Read More ⟩

The server maintenance

May 18, 2015 – Today from 12.05 AM to 2.00 AM UTC we conducted maintenance (installing new software on main server), monitoring was unavailable this time interval. Regards.

Read More ⟩

London, UK Monitoring Location Issue

May 06, 2015 – The Dotcom-Monitor server at London, UK monitoring location is unavailable for monitoring due to network issues it has been experiencing since 05/06/2015 02:00 AM CST. We will provide more updates on time-to-repair as soon as it becomes available.

Read More ⟩

CA, USA Monitoring Location tune-up

April 24, 2015 – On 04/24/2015 Dotcom-Monitor will be performing fine-tuning of the CA, USA monitoring location in order to enhance the performance of the monitoring software. This may result in the absence of response times or increased response times from this location during this maintenance and fine-turning process. In the

Read More ⟩

Dotcom-Monitor Issues

April 8, 2015 Dotcom-Monitor experienced a partial outage between 6:54am and 7:35am (CST). The outage resulted in some devices not being monitored at the specified frequency. The issue has been traced to index corruption on the database. We are currently working on root cause analysis. As of 7:35am all services

Read More ⟩

Dotcom-Monitor Issues

April 01, 2015 – Dotcom-Monitor has experienced problems this night between 10:30 PM CST and 12:30 AM CST that resulted in some partial monitoring. The issue has been resolved around 12:30 AM CST. The problem has been traced to the bug in the code, which under rare conditions causes system degradation.

Read More ⟩