Routing Problems on Reliance Broadband?

Status
Not open for further replies.
Code:
C:\Windows\system32>tracert -d google.com

Tracing route to google.com [216.58.196.14]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  100.100.100.1
  2     *        *        *     Request timed out.
  3     7 ms     8 ms     8 ms  59.185.211.205
  4     7 ms     7 ms     7 ms  59.185.211.206
  5     7 ms     7 ms     7 ms  74.125.51.205
  6     8 ms     7 ms     6 ms  209.85.241.52
  7     8 ms     7 ms     7 ms  216.239.41.149
  8     7 ms     7 ms     7 ms  216.58.196.14

Trace complete.
 
is it just me or anybody else is facing issue reaching to broadbandforum too?

i see some unnecessary hops in route. I am able to reach to IR (india end in 7 ms and then flagtel is not happily doing its job somehow.)

Code:
tracert broadbandforum.co

Tracing route to broadbandforum.co [173.236.194.106]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  10.168.1.1
  2     2 ms     2 ms     2 ms  115.252.208.1
  3     7 ms     6 ms     6 ms  115.255.237.94
  4     6 ms     9 ms     7 ms  115.255.237.93
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    41 ms    36 ms    45 ms  62.216.147.73
  8   184 ms   185 ms   185 ms  xe-0-0-0.0.pjr03.ldn001.flagtel.com [85.95.26.238]
  9     *      175 ms   178 ms  xe-4-2-0.0.cji01.ldn004.flagtel.com [62.216.129.138]
10   181 ms   181 ms     *     ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]
11   178 ms   179 ms     *     ae10.mpr2.lhr2.uk.zip.zayo.com [64.125.31.194]
12   183 ms   180 ms   179 ms  ae12.mpr3.lhr3.uk.zip.zayo.com [64.125.28.22]
13   247 ms   248 ms   248 ms  xe-2-3-0.cr2.dca2.us.zip.zayo.com [64.125.27.165]
14   254 ms   256 ms   254 ms  ae15.er5.iad10.us.zip.zayo.com [64.125.31.42]
15   251 ms   259 ms   254 ms  208.185.23.134.t00867-03.above.net [208.185.23.134]
16   254 ms   253 ms     *     ip-208-113-156-4.dreamhost.com [208.113.156.4]
17     *      259 ms   258 ms  ip-208-113-156-73.dreamhost.com [208.113.156.73]
18   253 ms     *      253 ms  ps380171.dreamhost.com [173.236.194.106]

Trace complete.
 
time for Facebook to establish servers in India
Google and facebook both use AKAMAI application routing servers in down south to route traffic. I forgot the name, there use to be one more data center in up in north which was doing application routing for facebook. There servers are located at nehru place and mysore too. I have visited there server farm once...... not getting the name on mind ....
 
Any way to fix this on my end? Browsing and downloading I can manage, but gaming is impossible once load times start.

Will going from 1 mbps to 4/8 mbps help?
 
Will going from 1 mbps to 4/8 mbps help
well my current throughput is 50mbps down (at this moment) and still facing the slowness... so you can decide if upgrade can help you. Broadbandforum for me is refusing to load .... and then after two three try the page is opening.

We all have to wait for this problem to get solve or until ISP's find a better route arrangements.

hume dava ki nai........ dua ki jarurat hai!

my torrent screenshot, my subscribed plan is 4mbps.........but ....;) FYI,
60e3MdN.jpg
 


Last edited:
@Raju ram din

SG is looking fine?

Yes, routing to Singapore is working fine. Try browsing singtel.com, it will load very fast. I think cable cut is causing slowdowns to America and Europe.

Traceroute to singtel.com.

Tracing route to singtel.com [203.126.100.199]
over a maximum of 30 hops:

1 3 ms 2 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 16 ms 16 ms 17 ms static-mum-59.185.211.221.mtnl.net.in [59.185.21
1.221]
4 17 ms 17 ms 15 ms static-mum-59.185.211.222.mtnl.net.in [59.185.21
1.222]
5 74 ms 73 ms 72 ms 121.244.47.189
6 * * * Request timed out.
7 109 ms 111 ms 111 ms 59.163.25.242.static.vsnl.net.in [59.163.25.242]

8 84 ms 84 ms 87 ms 59.163.52.29.static.vsnl.net.in [59.163.52.29]
9 82 ms 83 ms 82 ms 203.208.171.169
10 82 ms 82 ms 82 ms 203.208.174.34
11 82 ms 83 ms 82 ms GE-5-1.kovan.singnet.com.sg [165.21.12.50]
12 83 ms 84 ms 83 ms 165.21.43.58
13 * * * Request timed out.
14 86 ms 86 ms 83 ms 203.126.100.199

Trace complete.
 
Yes, routing to Singapore is working fine. Try browsing singtel.com, it will load very fast. I think cable cut is causing slowdowns to America and Europe.
Traceroute to singtel.com.

your traffic is getting routed thru Germany and then to Singapore. It is not using TIC or WE3 or any pacific bound cable. Ideally it should leave india from chennai or mumbai and travel towards Indonesia or Singapore directly.
 
your traffic is getting routed thru Germany and then to Singapore. It is not using TIC or WE3 or any pacific bound cable. Ideally it should leave india from chennai or mumbai and travel towards Indonesia or Singapore directly.

Well, I am on mtnl, just came to know about this cable cut through some post in mtnl forms. Its a shame, ISP don't post this important information on facebook pages, this will actually improve their customer confidence.
 
Flagtel cable seems fixed..... pings are moving back to normal.... no more timeouts.....

Code:
ping riot.nl

Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=211ms TTL=239
Reply from 213.136.12.232: bytes=32 time=211ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=211ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=209ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=213ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=212ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=211ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
Reply from 213.136.12.232: bytes=32 time=211ms TTL=239
Reply from 213.136.12.232: bytes=32 time=211ms TTL=239
Reply from 213.136.12.232: bytes=32 time=210ms TTL=239
 
Status
Not open for further replies.

Back