D@rekills4
Newbie
While the routing was fixed for Singapore, a few servers in Europe were giving 300+ ping.
So it's either Singapore or Europe. -_-
So it's either Singapore or Europe. -_-
D@rekills4 said:While the routing was fixed for Singapore, a few servers in Europe were giving 300+ ping.
So it's either Singapore or Europe. -_-
It was fixed for a while.fabulous_chicken said:Fixed for Singapore? Routing is bad for Singapore for me. EU servers are 200 ping max for me but with lot of packet loss.
I am getting a shitload of packet loss here.x720 said:No packet loss here, but I'd rather not mention the pings on ADSL.
D@rekills4 said:It was fixed for a while.
I am getting a shitload of packet loss here.
Anurag Bhatia said:Hi
Basically it "fixes" whenever they announce prefixes on IP circuits to Tata-VSNL AS4755 but as soon as they stop doing it it goes back to IPLC circuits announced to Tata AS6453.
You can use a tool like BGPlay - http://bgplay.routeviews.org/ with your specific /20 prefix and look at times when you get AS path XXX > 6453 > 4755 > 9829 and when it is XXX > 6453 > 9829 - the pattern will perfactly match the inconsistency you get in latency and times when you see things are "fixed" and when they are "broken".
Also BSNL is having serious issues in domestic routing as well from couple of days. I see very unstable BGP sessions at NIXI and lot of traffic just picking random loopbacks. Another serious problem they have from quite long time is that they do have high capacity IP ports from Tata but none in Delhi (as far as I see). Now whenever they prefer using Tata for any origination & destination in North India, we get loops via Mumbai. E.g here's a traceroute from my home connection in Haryana on BSNL to Tata-VSNL router in Delhi:
Anurags-MacBook-Pro:~ anurag$ traceroute -a 14.140.113.86
traceroute to 14.140.113.86 (14.140.113.86), 64 hops max, 52 byte packets
1 [AS65534] 10.10.0.1 (10.10.0.1) 1.797 ms 1.008 ms 0.992 ms
2 [AS9829] 59.91.224.1 (59.91.224.1) 19.142 ms 18.144 ms 17.477 ms
3 [AS9829] 218.248.169.122 (218.248.169.122) 27.025 ms 26.350 ms 22.949 ms
4 [AS4755] 115.114.57.165.static-mumbai.vsnl.net.in (115.114.57.165) 105.402 ms 110.742 ms 109.412 ms
5 [AS0] 172.31.17.106 (172.31.17.106) 134.004 ms
[AS0] 172.31.19.126 (172.31.19.126) 126.658 ms
[AS0] 172.31.19.22 (172.31.19.22) 179.289 ms
6 [AS4755] 14.140.113.86.static-delhi-vsnl.net.in (14.140.113.86) 132.746 ms 136.336 ms 133.581 ms
Anurags-MacBook-Pro:~ anurag$
Pretty bad route with way too high latency. Ideally latency should be just 30ms with direct forward route but what's happening here is that forward path is bad because BGP session is between BSNL's router in Mumbai/Chennai and NOT in Delhi.
I hope this will help.
This is all Happeing because of curruptionfabulous_chicken said:I'm no expert in networking =P , but do you mean that all our connections are being overcrowded at some location?