IMPORTANT: Please read the Outage Communication Rules before posting!
Since some time earlier today (June 3), the website IPs 185.27.134.116 and 185.27.134.98 have been down.
If your website is on one of these IPs, you may see errors like this:
- ERR_CONNECTION_TIMED_OUT
- The connection has timed out
- Error 522: Connection timed out
You can view the website IP address of your hosting account in the client area.
This issue is caused by a storage issue on the server. The storage is currently being automatically checked and repaired, but this is expected to take some time to be finished.
Our best guess is that it will be fixed by tomorrow morning (UTC), but it depends on the completion of the automated checks.
Update June 4: The checks are still in progress. We don’t know when they will be completed.
Additionally, the following IP addresses also went down later that day:
- 185.27.134.139
- 185.27.134.140
- 185.27.134.165
- 185.27.134.166
- 185.27.134.167
- 185.27.134.214
- 185.27.134.215
When connecting to any of these IPs, you will see an error like:
- ERR_CONNECTION_REFUSED
- Unable to connect
It’s unclear at this time what caused this or when it will be fixed.
Update June 4: The Connection Refused issue was fixed shortly ago and all websites on the IPs in the second list should be up again.
The IPs in the first list are still undergoing maintenance. It’s progressing but we don’t know yet how long it will take.
Update June 5: The maintenance on the IPs 185.27.134.116 and 185.27.134.98 is still in progress. The automated maintenance is making progress, but it’s impossible to say when it will be done.
Update June 9: I checked with iFastNet earlier today and it seems that the maintenance process has gotten stuck. iFastNet is looking for solutions on how to bring the IPs back up in another way. It’s possible that some data loss may occur because of this, but it’s hard to say anything definitively at this time.
Update June 18: It appears that the maintenance definitively failed. Due to multiple disk failures, most website files were corrupted and were lost. New hardware is on it’s way to bring the server back online, but most of your website files will probably be lost.
If you don’t want to wait for that, you can move your domain name to a different account. @Greenreader9 has written a great post on how to do that: Website IPs 185.27.134.116 and 185.27.134.98 are down - #190 by Greenreader9
Update June 27: The new disks have been installed and the IP addresses, FTP access and so on are all back online!
Unfortunately, as stated before, most website files were lost because of the hardware failure. But all the databases are still in-tact, so you may be able to recover some of your website that way.
The issue is considered resolved for now. We terribly regret the loss of data that has occurred, but there isn’t anything we can do to bring back your files now.