Past Incidents

Wednesday 26th February 2020

Migration of Liberty, Alpha and Bell.

Today we performing the migration of Liberty.xssl.net, Alpha.xssl.net and Bell.xssl.net.

This migration will start with Liberty.xssl.net at 10:30am and we expect to be finished by 12:30pm.

Updates will be posted as these are progressed.

The migration of Lib... 4 years ago The migration of bel... 4 years ago The migration of Alp... 4 years ago The Migration of Lib... 4 years ago The Sync has finishe... 4 years ago The services on libe... 4 years ago

Monday 24th February 2020

Migration of servers Firefly, Delta and Delphin

Today we will be performing the Migration of 3 servers: firefly.xssl.net - Start of Migration 10am, Expected to finish 12pm. delta.xssl.net - Expected Start of Migration 12pm, Expected finish 2pm (will start once firefly has finished). delphin.xssl.net - Expected start of Migration 2pm, Expected finish 4pm (will start once delta has finished).

While the servers are being moved, services will be down until the restore has finished.

We will do our best to get these done sooner than expected and get services running again. Updates will be posted throughout the day as this is progressed.

Wednesday 19th February 2020

Upgrading Otter.xssl.net

as part of the recent upgrades that we sent notices about yesterday, we will be Migrating the server otter.xssl.net

The server move will start at 7:30pm and we expect service to be back up and running by 9:00pm. We will do our best to get these back up sooner to minimize disruption.

Updates to follow.

The new server is up... 4 years ago The server is still... 4 years ago The services on the... 4 years ago

Issues resolving xssl.net server names

We recently had some issues with the xssl.net DNS zone which has affected some of the United Hosting servers.

We have resolved this now, however those who have accessed servers or mail using the domain during the time of the issue will have cached DNS records for up to 4 hours due to the existing TTL.

Ways to resolve this:

Reboot your computer and router - The cached records should be cleared by this. Failing that, they could be getting cached by DNS servers further up/outside your network.
Use your domain - If you have a domain name on this server, you can access WHM [mydomain.com/whm] Cpanel [mydomain.com/cpanel] and webmail [mydomain.com/webmail]. If you are using a mail client, you can also use your domain name in the mail settings to start connecting right away.
Wait - After 4 hours, this should resolve back to correct IP and the hostname for the server will start working for you without the need to make any changes.