OVH Community, your new community space.

Slow ping times to OVH

09-10-2012, 09:46

17-09-2012, 12:55
Quote Originally Posted by helpseeker
Any news?

since the last 2 days the problem re-appeared.
I have sent this to the network team, sorry for the poor latency

16-09-2012, 12:59
Any news?

since the last 2 days the problem re-appeared.

07-09-2012, 17:38

Yes we are aware of the issue and doing our best to resolve it. Apologies if it causes any issues.

07-09-2012, 17:19
Back at it again with 150ms+ pings

06-09-2012, 17:10
Had a complete loss of connectivity for a few minutes, after that golden.

06-09-2012, 16:52

Do you have any issues now? They should all be resolved.

06-09-2012, 15:32
I'm getting packet loss to my PCC at the moment, quite bad too

06-09-2012, 11:48
This doesn't seem to be general traffic but rather following a definite pattern over the past few days.

06-09-2012, 11:14

No, there appears to be some congestion because one of routes to the USA is offline, we are looking into why at peak time the pings increase for certain UK ISPs.

06-09-2012, 08:41
What's going on here, some DDOS attack?

05-09-2012, 23:27
Some serious variation there, high pings and low speed

05-09-2012, 17:09
Neil has said they are aware of the issue, cheers Neil!

Hi Mark

Thank you for your email. We have are aware of the issue and have noticed a high pings with certain ISPs, see

Our network team is working on the issue we hope to have it resolved shortly.

Kind Regards,


05-09-2012, 16:37
Yep, VPNs on my server are at a crawl

It's faster using HSPA on my phone than these servers at the moment.

05-09-2012, 16:36
Our remote network monitoring server (on BT infinity from Oxford) has been noticing fairly slow pings to our OVH servers an hour ago or something, but as go these things.

Seems to be more normal now.


05-09-2012, 16:04
Pinging several of my dedicated servers I'm getting slow ping times today

The below is typical:

64 bytes from icmp_seq=801 ttl=58 time=146 ms
64 bytes from icmp_seq=802 ttl=58 time=7.80 ms
64 bytes from icmp_seq=803 ttl=58 time=144 ms
64 bytes from icmp_seq=804 ttl=58 time=170 ms
64 bytes from icmp_seq=805 ttl=58 time=159 ms
64 bytes from icmp_seq=806 ttl=58 time=170 ms
64 bytes from icmp_seq=807 ttl=58 time=159 ms
64 bytes from icmp_seq=808 ttl=58 time=8.30 ms
64 bytes from icmp_seq=809 ttl=58 time=8.88 ms
64 bytes from icmp_seq=810 ttl=58 time=177 ms
64 bytes from icmp_seq=811 ttl=58 time=8.53 ms
64 bytes from icmp_seq=812 ttl=58 time=8.49 ms
64 bytes from icmp_seq=813 ttl=58 time=9.92 ms
64 bytes from icmp_seq=814 ttl=58 time=9.23 ms
64 bytes from icmp_seq=815 ttl=58 time=8.97 ms
64 bytes from icmp_seq=816 ttl=58 time=168 ms
64 bytes from icmp_seq=817 ttl=58 time=8.45 ms
64 bytes from icmp_seq=818 ttl=58 time=171 ms

As you can see it goes up to 177ms, which is big!

This was done from both our datacenter in Slough, our London office, and our Stockton office, all on different internet connections so it's a not a problem anywhere local to us.

traceroute to (, 30 hops max, 40 byte packets
1 ( 2.408 ms 2.300 ms 2.475 ms
2 ( 5.713 ms 5.695 ms 5.671 ms
3 * * *
4 ( 12.420 ms 12.403 ms 12.377 ms
5 * ( 177.601 ms *