majority of sites not opening on mtnl---

  • Thread starter Thread starter banda
  • Start date Start date
  • Replies Replies 60
  • Views Views 11,055
at my end. internet is pretty much unusable since 9... :D this server on the other hand works fine. yohoo!
 
yes same, almost unusable. i was wondering since hathway is working it must be MTNL problem somewhere but since u confirmed problem with airtel too, hathway must be using something else.Myplace> ping hi5.com34 packets transmitted, 15 received, 55% packet loss, time 37150msFriendsplace> ping hi5.com22 packets transmitted, 22 received, 0% packet loss, time 22788msMyplace> traceroute hi5.com 3 59.160.16.158 37.953 ms 14.996 ms 15.031 ms 4 59.163.16.138.static.vsnl.net.in (59.163.16.138) 256.908 ms 257.486 ms 257.752 ms 5 * if-1-1.core2.PDI-PaloAlto.Teleglobe.net (64.86.84.129) 369.733 ms 369.544 ms 6 * if-3-1.mcore4.PDI-PaloAlto.teleglobe.net (216.6.86.17) 375.696 ms 375.837 ms 7 * if-0-0-0.core3.SQN-SanJose.teleglobe.net (216.6.33.5) 373.852 ms * 8 if-4-0-0.core4.SQN-SanJose.teleglobe.net (216.6.33.18) 377.715 ms * * 9 ix-2-0-0.core4.SQN-SanJose.teleglobe.net (66.198.97.6) 369.682 ms * *10 * * *11 * * *Unable to look up 154.54.3.130: Temporary failure in name resolution12 154.54.3.130 360.477 ms 420.177 ms 352.557 ms13 sona_networks.demarc.cogentco.com (38.101.48.78) 356.523 ms 358.607 ms *14 * * 204.13.51.242 (204.13.51.242) 360.608 msFriendsplace> traceroute hi5.com 4 192.168.27.2 (192.168.27.2) 1.805 ms 1.688 ms 2.284 ms 5 121.241.1.38.mumbai-static.vsnl.net.in (121.241.1.38) 3.966 ms 3.375 ms 4.365 ms 6 59.163.16.13.static.vsnl.net.in (59.163.16.13) 3.414 ms 4.658 ms 3.316 ms 7 59.163.16.142.static.vsnl.net.in (59.163.16.142) 243.279 ms 243.238 ms 242.709 ms 8 if-1-1.core2.PDI-PaloAlto.Teleglobe.net (64.86.84.129) 270.500 ms 259.050 ms 258.218 ms 9 if-5-0.core2.SQN-SanJose.Teleglobe.net (64.86.84.134) 260.494 ms 264.168 ms 259.716 ms10 if-5-0-0.core4.SQN-SanJose.teleglobe.net (66.198.96.2) 271.185 ms 259.958 ms 260.271 ms11 ix-2-0-0.core4.SQN-SanJose.teleglobe.net (66.198.97.6) 269.670 ms 410.731 ms 284.918 ms12 vl3490.mpd01.sjc01.atlas.cogentco.com (154.54.6.81) 270.897 ms 288.351 ms 283.146 ms13 te9-3.mpd01.sfo01.atlas.cogentco.com (154.54.2.53) 276.997 ms 276.850 ms 283.958 ms14 vl3492.mpd01.sfo02.atlas.cogentco.com (154.54.3.122) 293.201 ms 273.970 ms 274.060 ms15 sona_networks.demarc.cogentco.com (38.101.48.78) 277.039 ms 287.657 ms 282.867 ms16 204.13.51.242 (204.13.51.242) 274.007 ms 279.618 ms 290.193 msI cant figure out much difference in routing but his line is so stable and continuous without any drops!Strange, very strange.In mycase from core2.PDI-PaloAlto it goes to mcore4.PDI-PaloAlto and then it goes to SQN-SanJoseIn his case its direct core2.PDI-PaloAlto to SQN-SanJosemay be thats the difference but then hathway and MTNL both use VSNL as backbone then why different routes?
 
seems like everything is ok now...dunno for how long it will be like this in the working condition........:ashamed:
 
10-15days.btw everything ok? and then u ask contradicting question.nothing is ok here.
 
170KBps is not just OK. its almost very good.
 


Its pathetic speed even dial up was better in its days........this is so worse, nothing opens easily...
 
mine has gone better now. atleast now my yahoo mail is opening fast.and this forum too
 
Unintentional double post........hope it gets settled soon, i am still having problems opening majority of sites including yahoomail
 
surfing is quite sluggish but for me torrents are still giving me decent speeds..
http://img186.imageshack.us/img186/107/screenshot181890rf9.jpg
 

Back