Routing Problems on Reliance Broadband?

Status
Not open for further replies.
Is only reliance and MTNL affected by this ?
I guess beam and airtel are having no issues.
 
Airtel routing is fine......

Code:
tracert worldoftanks-sea.com

Tracing route to worldoftanks-sea.com [92.223.17.86]
over a maximum of 30 hops:

  1     4 ms     1 ms     6 ms  192.168.2.1
  2    34 ms    32 ms    36 ms  43.230.45.107
  3     *      326 ms   570 ms  43.230.45.105
  4    49 ms    49 ms    38 ms  161-36-87-183.mysipl.com [183.87.36.161]
  5    22 ms    28 ms    33 ms  nsg-static-65.54.75.182-airtel.com [182.75.54.65]
  6   111 ms    62 ms    64 ms  182.79.245.197
  7   109 ms   113 ms   112 ms  p38670.sgw.equinix.com [202.79.197.222]
  8   235 ms   180 ms   272 ms  sg1-a9001-edge-1-be20-2000.wargaming.net [92.223.116.131]
  9   102 ms   135 ms    92 ms  sg2-n5596-fe-1-vl231.wargaming.net [92.223.116.163]
 10   113 ms   101 ms   113 ms  92.223.17.86

Trace complete.

Airtel route to EU...

Code:
tracert riot.nl

Tracing route to riot.nl [213.136.12.232]
over a maximum of 30 hops:

  1     4 ms     2 ms     3 ms  192.168.2.1
  2     4 ms     2 ms     2 ms  43.230.45.107
  3     *        *      768 ms  43.230.45.105
  4    14 ms    11 ms     8 ms  161-36-87-183.mysipl.com [183.87.36.161]
  5     6 ms     5 ms     5 ms  nsg-static-65.54.75.182-airtel.com [182.75.54.65]
  6   106 ms   134 ms   145 ms  182.79.222.21
  7   127 ms   126 ms   131 ms  amsix-501.xe-0-0-0.jun1.bit-2a.network.bit.nl [80.249.208.35]
  8   137 ms   121 ms   123 ms  http-linux.lb.network.bit.nl [213.136.12.232]

Trace complete.

This is through CableNet
 
so airtel-singtel is fine then ... i think only WE3 and TIC is affected with this.
 
for all below, 10.168.1.1 is my local router connecting to reliance using fiber mux.
Code:
tracert -d worldoftanks-sea.com

Tracing route to worldoftanks-sea.com [92.223.17.86]
over a maximum of 30 hops:

  1     2 ms    <1 ms    <1 ms  10.168.1.1
  2     1 ms     8 ms     1 ms  115.252.208.1
  3    20 ms    17 ms    16 ms  115.255.237.94
  4    20 ms    17 ms    17 ms  115.255.237.93
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7   100 ms    99 ms   100 ms  62.216.145.229
  8    87 ms    93 ms    83 ms  62.216.144.234
  9   131 ms   131 ms   130 ms  203.208.158.21
10    88 ms    87 ms    87 ms  203.208.175.74
11   135 ms   134 ms   137 ms  92.223.116.163
12    83 ms    82 ms    84 ms  92.223.17.86

Trace complete.

I think hop 5-6 is a non routing hops ... that is why packet loss.

Code:
tracert -d riot.nl

Tracing route to riot.nl [213.136.12.232]
over a maximum of 30 hops:

  1    <1 ms    <1 ms     *     10.168.1.1
  2     2 ms     2 ms     1 ms  115.252.208.1
  3    18 ms    18 ms    17 ms  115.255.237.94
  4    16 ms    18 ms    18 ms  115.255.237.93
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    42 ms    52 ms    43 ms  62.216.147.73
  8   193 ms   189 ms   188 ms  85.95.26.233
  9   190 ms   195 ms     *     195.66.237.51
10   207 ms   207 ms   217 ms  213.136.1.105
11   204 ms   205 ms   204 ms  213.136.12.232

Code:
tracert -d google.com

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

  1    <1 ms    <1 ms     1 ms  10.168.1.1
  2     2 ms     2 ms     1 ms  115.252.208.1
  3    17 ms    17 ms    17 ms  115.255.237.94
  4    18 ms    16 ms    16 ms  115.255.237.93
  5     *        *        *     Request timed out.
  6    18 ms    17 ms    17 ms  72.14.204.158
  7    17 ms    17 ms    18 ms  66.249.95.106
  8    18 ms    19 ms    18 ms  209.85.240.17
  9    17 ms    17 ms    18 ms  173.194.36.96
 


No....anything in pacific from india should be below 100ms. and idealy under 60ms....
 
routing on excitel which uses sify is also going via London
be2328.ccr21.lon01.atlas.cogentco.com

while airtel dsl is working fine.
 
Status
Not open for further replies.

Back