Network Status

Dear Clients,

We are currently investigating an issue affecting our server's database functionality. Specifically, our YUM repository attempts to update, but each update triggers an error in MySQL. This issue is currently under active investigation by our technical team.

Rest assured, we are diligently working to identify the root cause of this problem and implement a solution promptly. Our goal is to resolve the issue and restore normal operations as quickly as possible.

We understand the inconvenience this may cause and appreciate your patience and understanding during this time. Updates regarding the progress of our investigation and any developments toward a resolution will be communicated promptly.

Thank you for your understanding.

Sincerely,

Administration

07/03/2024 - Update: Shortly after the databases went offline for the second time, we were able to revert the automatic update in the YUM repository and bring the databases back online. We have confirmed that this is a known bug in the YUM repository with cPanel and cPanel is working on releasing a bugfix. For now, we have enabled a version lock to our YUM repositories.

We are aware of an email issue within Server 2 where emails are not getting delivered. We are looking into this issue and hope to have it resolved soon.

08/07/2022 0046: Emails have now been restored.

We have experienced an issue with our cron job and our server has terminated some client's accounts that the system believed were overdue. We have interrupted the cronjob process and have begun restoring accounts. We will have further updates as soon as possible.

Update 1: Our billing center has canceled orders, added late fees, and canceled active addons. If you are affected by late fees or your service is canceled, please submit a support ticket and we will take care of your issue as soon as possible. We have already gone through and removed most of the late fees that had been added by the system. 

Update 2: Our server is still in progress with restoring the accounts that have been erroneously terminated.

Update 3: Accounts have been restored. If you have been affected by invoices not being generated, please let us know via support ticket to the billing department and we will take care of your billing issues.

We are currently investigating a mail deliverability problem with incoming emails to the server. Mail can still be sent but can not be received. We are actively investigating this issue and will release more information once it becomes available.

Dear Users,

USHost247 will begin migrating from older servers to newer, higher capacity servers. Servers are currently being configured and setup to get ready for the migration of accounts. We will release a new announcement with the updated information for those running custom nameservers. For those that currently use NS1.NOC10.NET and NS2.NOC10.NET as your nameservers, there will be no modifications needed from your end. As with all migrations, there is a chance for error and delays in DNS propagation, which we will keep the old server up and running until the migration is fully complete. We will release more information as it comes available.

During our monitoring process, we could see that software raid resync going on in the server server2.noc10.net. This would be the server's response to handle a disk issue that happened recently and should be completed successfully without any issues. However, you may notice a slightly degraded server performance during this resync process, until it gets completed.

Users seem to be having a problem logging into cPanel. Once credentials are verified, cPanel loads into a solid white page. 
We are currently looking into this problem and will update this as more information when found out.

>>
Problem has been replicated. Investigating

>>
Problem has been solved.

Users have reported FTP connection issues after server migration. 
We are working on investigating and resolving the issue.

We have been informed of a cron job problem that is currently affecting more than one account. We are currently investigating this issue. We will update with any information as it comes available.

*We have identified some problems in the error logs and are currently working to correct these errors and then test crons to make sure they are working correctly. If you use cron jobs in cPanel, please pay attention to make sure they are running correctly. If not, please contact us and let us know.

DetailsThe links between Newark and our datacenter of Beauharnois are down:
6x100G
20x10G
We will update this taso as soon as we have more information.

There has been a main fiber line cut near the datacenter and has knocked out connectivity to North American BHS datacenter.

Here is the update from OVH:

Within 3 to 4 weeks, we will finish the work on our own 2nd route towards New York/Newark and we are going to activate an optical failover of 6x100 Gbps through the following 2 routes: BHS/NYC-NWK. This will allow us to terminate the rental of the 20x10 Gbps through Newark.         We are going to increase the capacity of Montreal/Chicago to 2x100 Gbps then 4x100 Gbps while waiting for our own route to be finished between BHS and Chicago by Toronto/Detroit. We cannot yet provide an ETA, knowing that we lack 800 KMs between Toronto and Detroit, MI. We already have in place BHS towards Toronto and Detroit, MI towards Chicago, IL.         At the same time, we are working on the network in the USA between New York and Newark (NY) then Chicago (IL) and Ashburn (VA). This new USA network is planned to be deployed in Q2 2016 and will not only provide redundancy from BHS towards Chicago through New York but also allow for the connection of a datacenter in the USA.      We sincerely apologize for the latest BHS downtime. We underestimated the time and the complexity of the fiber optic network construction projects in Canada, thus creating an unreasonable delay in securing each kilometer connecting the BHS Datacenter. Even though today it's done and we have 100% redundancy, we are really sad to announce this under such circumstance. Within the next 10 days, we will offer compensation which conforms to our SLA for the month of November. The exact times concerning the incident:  - down at 11:53 AM GMT-5 (5:53 PM GMT+1) - at 4:48 PM GMT-5 (10:48 PM GMT+1), traffic to the BHS datacenter from the outside returned to normal thanks to the optical fiber by the South - in contrast, the links between BHS and the other OVH datacenters and the VAC (Anti-DDoS) were affected until the complete repair of the North fiber. Traffic was able to resume at 10:44PM (04h44 GMT+1). Best Regards, Octave

We have sceduled a server2 restart at 22:30. This restart will simply install a few updates that have been performed on the server. There will be minimal downtime during the restart. 1-5 minutes.

We are currently having a directory issue causing user's websites to show a 404 error. We are in progress of getting each account back online. Some users may already have their accounts back online and may have not noticed a difference. Some may take longer than others. No data loss has occurred.

We are currently working with the datacenter to get our email server back online. There is a small backlog of queued emails, the emails will get processed as soon as the issue is worked out with the datacenter.

We are aware of some users having blank databases after the transfer. We have taken backups of the databases from the old server and currently reimporting every database. This will take some time to upload and import. We apologize for any inconveinences. 

We have reported an issue to cPanel technicians that has disallowed users access to cPanel and WHM. When trying to load into the login screen, the page will take a long time to load or often time out instead. We still have direct access to the server. We will update everyone with more information as it comes.

Clients are having trouble logging into cPanel. Template in cPanel does not display correctly and soon as a user clicks on something, the user is immediately logged out and directed straight to cPanel login screen.

We have a server reboot scheduled for 12am, 2/9/2013. 

Websites are going down for various times and coming back online at random times. We had a problem this morning that was said to be resolved; same problem exists. 

Dear Users,

Lately our HTTPD service has been crashing and restarting itself. Usually ending up 10-20 seconds downtime. (As you may see on HostTracker)

We will be taking the server down for critical maintenance. Once finished, the server will be back online. Should not take more then 20 minutes.