It's hard to imagine how any ISP anywhere in the world can do worse than Lanka Bell Broadband has done over the past few months. Well Lanka Bell just did! They have outdone themselves, they have jumped from one failure a week to two failures a week.
The ink hasn't even dried on my post about Monday's
service disruption when it has happened again today. This time it's not completely offline just massive packet losses.
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=282 ttl=239 time=707 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=285 ttl=239 time=847 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=290 ttl=239 time=782 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=291 ttl=239 time=822 ms
^C
--- google.com ping statistics ---
322 packets transmitted, 40 received, 87% packet loss, time 321559ms
It's better to have a complete failure than a pathetic slow down like this because you are tempted to carry on with your work and get hugely frustrated when mail clients times out and web pages take forever to load.
The moron in charge of Lankabells routers has apparently changed the path for most packets heading out of the country. Now they are send through VSNL while earlier they were being sent through Flagtel
traceroute to google.com traceroute to google.com (209.85.171.100), 30 hops max, 60 byte packets
1 10.12.0.17 (10.12.0.17) 36.584 ms 42.136 ms 47.098 ms
2 10.12.2.114 (10.12.2.114) 47.347 ms 47.579 ms 47.726 ms
3 59.163.253.206.static.vsnl.net.in (59.163.253.206) 361.624 ms 367.662 ms 367.825 ms
4 59.163.16.1.static.vsnl.net.in (59.163.16.1) 368.096 ms 368.256 ms *
5 59.163.16.1.static.vsnl.net.in (59.163.16.1) 372.029 ms 372.261 ms *
6 59.163.16.134.static.vsnl.net.in (59.163.16.134) 436.614 ms 399.798 ms 395.085 ms
7 219.64.231.1.mpls-vpn-sj.static.vsnl.net.in (219.64.231.1) 344.553 ms 348.931 ms 354.040 ms
8 209.85.240.114 (209.85.240.114) 353.768 ms 344.424 ms 344.028 ms
9 (72.14.232.138) 370.391 ms 373.889 ms 216.239.49.198 (216.239.49.198) 373.497 ms
10 (72.14.236.164) 375.276 ms 209.85.250.147 (209.85.250.147) 370.309 ms 355.806 ms
11 216.239.48.134 (216.239.48.134) 365.422 ms 360.927 ms 216.239.46.203 (216.239.46.203) 360.436 ms
12 216.239.48.141 (216.239.48.141) 355.221 ms 209.85.251.129 (209.85.251.129) 370.138 ms 370.113 ms
13 209.85.251.145 (209.85.251.145) 364.860 ms 359.748 ms 74.125.30.134 (74.125.30.134) 363.212 ms
14 cg-in-f100.google.com (209.85.171.100) 359.279 ms 74.125.31.134 (74.125.31.134) 374.295 ms 374.227 ms
This traceroute dump doesn't always show up. What you usually see is stars ( * * * ) the usual indication for a timeout