We’ve had some intermittent reports in the past short while about problems similar to the ones on Saturday.
All hands are on deck working on it, and we’ll update as soon as we have more info.
Our sincere apologies for any inconvenience, and thanks for the understanding.
Update 22:00 EST:
We’ve made further adjustments to the system. While symptoms disappeared quite quickly, we continue to monitor the situation.
If, perchance, this recurs and you happen to be near a shell, please run this command:
dig +trace [domain]
and then email us those results. If you also include a “traceroute” it may be helpful as well.
The data suggests that these issues are confined to the legacy platform and we will be posting at length about this in the days and weeks to come as this has underscored the need to sunset the legacy system.
Domains on the new platform appear unaffected by these issues, so migrating your domains over to the new system is never a bad idea.
We are very sorry for these issues and are directing all efforts to preventing a recurrence.
More as it comes in.
Can you tell me if my web site is hosted by yourself. If so, it has been down for almost 12hrs. If you are the host and the website is not up by tomorrow morning at 8:30am then I will have to change providers. This is costing my business…
Please advise asap.
Your issue is an unrelated issue (sorry, don’t mean to pass the buck). The DNS is fine for this domain (which is with us) but it appears that there is no webserver running on your host.
markjr@spitfire:~$ telnet inlinefiberglass.com 80Trying 209.250.157.142...
telnet: Unable to connect to remote host: Connection refused
I also dropped you an email to this effect.