Its actually not MTNL's fault inasmuch as the fault lies with Flag telecom i.e their upstream Bandwidth provider..though MTNL can be blamed for not monitoring the quality of service they get from Flag ie the absurd routing from FLAG..Since MTNL would not do anything i emailed FLAG directly asking them for reason for the Circuitous route..I complained of high pings on India >> HKG route..where data is being routed through EGypt , Yet to recieve any response..presumably coz of Easter/gd friday holidayz & the weekend..
The crux of the problem lies here i think..I did a whois on hop 6 and 7....6 39 ms 37 ms 41 ms 126.96.36.199 --------------> london7 203 ms 187 ms 193 ms so-6-2-0.0.cjr02.ldn004.flagtel.com [188.8.131.52] -------------------> london Both belong to flag telecom ... and i think are on the same network(maybe close distance...)..but the latency is a whooping 150+ ms.. so if this can be taken care of it would make matters a lot better.@ cyberwiz : can ya send me the email of the person u contacted....il too send them some HATE mails...
Thats not where the problem is, 184.108.40.206 is in India , whois merely says the IP address belongs to FLAG telelcom of GB
150 ms jump from mumbai to London is ok..
Problem is with their absurd routing..earlier they were routing all data bound for east Asia thru HKIX, now for some reason they are not using that link..and using all sorts of circuitos routes to get their data from India to E Asia