All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
[UPDATE] OVH blacked out in portion of Eastern US[who route through Equinix Ashburn]
This morning from my office Internet, I cannot reach any OVH site/VPS. I thought OVH is down but I later find out I can connect to it on my cell connection. So I dig in. My office connection mostly is HE and Cogent and traceroute seems that HE does not know how to route the traffic and lost it. Can anyone with HE only connection test it?
3 1 ms <1 ms <1 ms 216-59-114-49.i95.net [216.59.114.49]
7 * * * Request timed out.
8 10 ms 1 ms 2 ms v408.core1.ash1.he.net [216.66.32.53]
9 11 ms 11 ms 12 ms 10ge1-1.core1.clt1.he.net [184.105.80.58]
10 17 ms 16 ms 18 ms 10ge5-2.core1.atl1.he.net [184.105.80.61]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
Comments
HE.net is not to blame, I can reach www.he.net and 216.66.32.53 on your trace from my servers at OVH.
However I can't reach 216.59.114.49. So it's more about your provider than HE.net
You can file a ticket with OVH and after 5 days get a canned reply that networks outside OVH are not their responsibility.
Interesting. When my provider send the traffic into HE's network, then HE's in charge, right?
Yes, but the traffic in this direction might be arriving and it might be the opposite direction that is broken.
The problem is, the OVH router doesn't know where to send the traffic for you:
There can be various causes for that, and it's not necessarily HE.net's fault.
I suggest that you contact both your ISP and OVH (even though they reacted like I said above, to similar peering issues in the past).
Got it
Looks like it's OVH's peering in Ashburn,VA that's broke. From one of my box with another provider near Washington DC using Inforelay as a provider and traffic go through Level 3. They cannot reach OVH too(or OVH doesn't know how to send traffic back).
Perhaps it's this: http://status.ovh.net/?do=details&id=7800
But very bizarre that no alternative route has kicked in.
@rm_ It appears to me that OVH use peering extensively. They may not have enough transit to go around it.
And anyone in eastern US that usually route through Washington DC will be blacked out and have no way to reach OVH and anyone who hosted with OVH.
It seems to me that it is OVH's fault. In the peering above, HE is already using Atlanta to send the traffic but OVH doesn't know that
Or this
OVH has so many network problem going on at the same time.
I host my Email at OVH. Now, it looks like someone will have hard time sending my emails.
Well E-mail is a simple case, that's why you [should] have at least two incoming mail servers, and absolutely at two or more different providers. The SMTP protocol allows for complete fault-tolerance in this part with no issues.
It is hosted Exchange! I am not running my mail server on VPS at the moment.
Anything stopping you adding an additional MX record to your DNS and having that accept mail?
Yes. Laziness.
Laziness never pays off. Example: your current situation.