cloud72.dotcanada.com Service interruption (Resolved)
Affecting Server – cloud72 | Priority – Critical
Cloud72 is currently experiencing issues related to HTTPD, CPANEL and WHM.
Our server administrators are working on identifying and resolving the issues right now. We will provide updates as soon as they become available.
dotCanada::Support Response Team
10:52 AM _ EST
Admin team reports that the cloud72 server server will not mount or boot correctly due to HPBS issues (the related file system). Our team is working on it right now as a priority, but at this
moment we are unable to provide an estimated time of repair. Updates to follow
11:10 AM EST
Our administrators have confirmed that services have been completely restored to server cloud72. We would like to apologize for your inconvenience.
Date – 27/02/2013 09:19 – 27/02/2013 10:25
Last Updated – 27/02/2013 10:25
RBL Listing (Resolved)
Affecting Server – cloud75 | Priority – High
Sunday February 17 (1:04 p.m.)
We are receiving a large number of calls from clients experiencing bounce back email messages as a result of a blacklisting at CBL(and at Spanhause as a result). Our administrators are working right now to resolve the issue including communicating with the list administrators and working to get this listing lifted. We will update this announcement with our progress.
Sunday, February 17 (7:15 p.m.)
Our team has been working on this server and spam report. We are investigating the possibility that this may have ben the result of a report of a previous issue from earlier this week. Because dotCanada takes these kinds of reports very seriously, we must execute all scans before we can submit the server for delisting. We expect to have this resolved shortly.
Monday, February 18 (3:16 p.m.)
We have completed the necessary scans and are analyzing the results prior to contact CBL to have this server released from their blacklist.
Monday, February 18 (9:40 p.m.)
We have contacted CBL to have this server released from their blacklist.
Tuesday February (4:25 AM)
CBL has confirmed removal from their blacklist. Some mail servers may have to wait for new definitions, but for the most part clients should no longer see bounce messages.
Date – 17/02/2013 12:48 – 19/02/2013 00:00
Last Updated – 19/02/2013 15:44
Spamhause RBL listing (resolved) (Resolved)
Affecting Server – cloud72 | Priority – High
Saturday, February 16 (11:04 a.m.)
We are receiving a large number of calls from clients experiencing bounce back email messages as a result of a black listing at Spamhause. Our administrators are working right now to resolve the issue including communicating with the list administrators and working to get this listing lifted. We will update this announcement with our progress.
Sunday, February 17 (5:15 a.m.)
At dotCanada we take these kinds of reports very seriously and act on them immediately to protect our reputation and the reputation of our clients. Our team has been working on this server and spam report through the night. The server has been given the all clear and it was determined that the only reported spam was sourced from an exploited email account. The outgoing mail was stopped yesterday while we cleared up the queue.
We also ran several scanner tools on the server to ensure that there was no account level exploitation and the results were negative.
Thank you all for your patience.
Sunday, February 17 (8:06 p.m.)
We have received notice from the RBL listing our server that the server has been delisted. This means that mail should start flowing properly again. Some mail servers may take a couple of hours to receive the update from the list server.
We appreciate your patience in this matter.
Date – 16/02/2013 11:04 – 17/02/2013 20:06
Last Updated – 17/02/2013 19:11
Chkdsk in Progress (Resolved)
Affecting Server – cloud72 | Priority – High
This issue has been resolved.
We are aware of an extended chkdsk in progress on cloud72.
At approximately 8 p.m. Saturday evening, cloud72 experienced a server issue that resulted in a server reboot. During this reboot, the server identified that the filesystem was not cleanly unmounted and started a chkdsk.
We apologize for the length of the delay and we will be providing a complete post-mortem once the server chkdsk has finished. We will provide as much detail as possible and we will review everything to see how this could be avoided in the future. We must wait for the reboot to finish before checking the logs for the reason.
Date – 16/02/2013 20:44
Last Updated – 17/02/2013 00:21