OVH Community, your new community space.

ISP Problem


mmihov
12-10-2008, 08:53
Thank you.

JALZOO
11-10-2008, 21:37
Contact oles@ovh.net about this problem.

mmihov
11-10-2008, 16:12
The problem is the downlink path - from ovh to us. We tested with different uplink paths and the result is identical.

mmihov
11-10-2008, 16:10
Tracing route to 77.111.207.117 over a maximum of 30 hops

1 1 ms <1 ms <1 ms mania-megalan.routers.megalan.bg [213.240.241.250]
2 2 ms 1 ms 1 ms 77.70.115.241
3 1 ms 2 ms 2 ms 87.120.6.153
4 35 ms 36 ms 34 ms 87.120.7.246
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 116 ms 117 ms 118 ms gsw-3-m1.routers.ovh.net [213.251.190.52]
9 115 ms 115 ms 115 ms 77.111.207.117

Trace complete.

helpseeker
11-10-2008, 16:03
post a traceroute maybe?

mmihov
11-10-2008, 08:42
Dear Colleges,

We are a big ISP, located in Sofia/Bulgaria. We have troubles accessing your sites. We have two international connections, and the problem is only with the first one - via Neterra.bg ISP.

Our customers are reporting for higher latency to your servers:

Reply from 77.111.207.117: bytes=1400 time=120ms TTL=48
Reply from 77.111.207.117: bytes=1400 time=118ms TTL=48
Reply from 77.111.207.117: bytes=1400 time=119ms TTL=48
Reply from 77.111.207.117: bytes=1400 time=118ms TTL=48
Reply from 77.111.207.117: bytes=1400 time=119ms TTL=48

The normal latency (via other ISPs is):

64 bytes from 77.111.207.117: icmp_seq=0 ttl=48 time=46.929 ms
64 bytes from 77.111.207.117: icmp_seq=1 ttl=48 time=46.597 ms
64 bytes from 77.111.207.117: icmp_seq=2 ttl=48 time=46.014 ms
64 bytes from 77.111.207.117: icmp_seq=3 ttl=48 time=45.563 ms

This is a big trouble for our customers, because they are having very fast and intensive connection to their servers located by your customer.

It seems that your looking glass is not working, that's why I'm writing here.

Thank you for your help in advance.

Regards,
Mihail Mihov
Megalan Network Ltd.