Direct peering of my ISP with Beam tele in Google DNS route.

acc1444

Regular
[OP]
Regulars
Aug 2, 2008
970
37
C:\Users\admin>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 4 ms 3 ms 5 ms 10.10.10.1
2 5 ms 5 ms 6 ms ---.---.---.--- CPE IP
3 13 ms 31 ms 11 ms 192.168.170.1 ISP private server IP
4 39 ms 17 ms * ***.***.***.*** ( ISP server )
5 11 ms 9 ms 8 ms ***.***.***.***
6 13 ms 11 ms 11 ms 124.124.243.38 Beam tele ip
7 * * * Request timed out.
8 * * 651 ms 72.14.212.118
9 596 ms * 690 ms 72.14.232.99
10 * 209 ms 474 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

I got the first above route without Reliance ip but in the second route, reliance reminds me its presence. I don't know why in the first route, reliance ip did not come.

C:\Users\admin>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 8 ms 2 ms 2 ms 10.10.10.1
2 5 ms 3 ms 3 ms ---.---.---.---
3 13 ms 9 ms 10 ms 192.168.170.1
4 97 ms 11 ms 9 ms ***.***.***.***
5 13 ms 10 ms 11 ms ***.***.***.***
6 14 ms 12 ms 13 ms 124.124.243.38
7 22 ms 21 ms 170 ms 115.255.239.45
8 21 ms 18 ms 21 ms 72.14.212.118
9 50 ms 20 ms 19 ms 72.14.232.99
10 20 ms 19 ms 21 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.



IBF
C:\Users\admin>tracert broadbandforum.in

Tracing route to broadbandforum.in [108.162.197.164]
over a maximum of 30 hops:

1 4 ms 2 ms 2 ms 10.10.10.1
2 5 ms 3 ms 3 ms ---.---.---.--- (CPE IP)
3 12 ms 10 ms 11 ms 192.168.170.1
4 13 ms 11 ms 11 ms ***.***.***.*** (ISP SERVER IP)
5 10 ms 12 ms 11 ms ***.***.***.*** (ISP SERVER IP)
6 14 ms 10 ms 10 ms 124.124.243.38
7 118 ms 101 ms 101 ms 115.255.252.149
8 98 ms 38 ms 95 ms 62.216.147.249
9 115 ms 72 ms 130 ms so-7-0-0.0.ejr03.sin001.flagtel.com [62.216.128.
73]
10 153 ms 107 ms 209 ms so-0-2-0.0.pjr02.hkg005.flagtel.com [85.95.26.12
5]
11 232 ms 204 ms 204 ms so-5-0-0.0.cjr04.hkg003.flagtel.com [85.95.25.21
4]
12 124 ms 203 ms 204 ms xe-1-2-0.0.cji01.hkg003.flagtel.com [62.216.128.
66]
13 121 ms 207 ms 204 ms 119.27.63.48
14 112 ms 222 ms 125 ms 108.162.197.164

Trace complete.



Outlook.com. Microsoft doesn’t allow user to get reply under ping window.
So, normally I was about to reach at end but I couldn’t get the final server ip.
C:\Users\admin>tracert outlook.com

Tracing route to outlook.com [157.56.234.150]
over a maximum of 30 hops:

1 2 ms 3 ms 3 ms 10.10.10.1
2 5 ms 3 ms 3 ms ---.---.---.--- (CPE IP)
3 13 ms 14 ms 9 ms 192.168.170.1
4 12 ms 10 ms 10 ms ***.***.***.*** (ISP SERVER IP)
5 11 ms 9 ms 9 ms ***.***.***.*** (ISP SERVER IP)
6 12 ms 13 ms 10 ms 124.124.243.38
7 105 ms 22 ms 78 ms 115.255.252.130
8 21 ms 18 ms 28 ms 62.216.147.73
9 268 ms 205 ms 304 ms 85.95.26.157
10 231 ms 204 ms 203 ms xe-0-0-0.0.pjr03.ldn001.flagtel.com [85.95.26.20
2]
11 221 ms 164 ms 341 ms 62.216.128.114
12 176 ms 202 ms 203 ms 62.216.147.218
13 232 ms 204 ms 203 ms ge-3-1-0-0.lts-64cb-1a.ntwk.msn.net [207.46.42.2
2]
14 253 ms 279 ms 306 ms ge-3-0-0-0.nyc-64cb-1a.ntwk.msn.net [207.46.43.4
4]
15 303 ms 324 ms 306 ms xe-8-3-0-0.sn1-96cb-1b.ntwk.msn.net [207.46.45.1
15]
16 329 ms 306 ms 408 ms 207.46.47.59
17 335 ms 306 ms 306 ms xe-1-0-0-0.sn2-96c-2a.ntwk.msn.net [207.46.33.12
2]
18 329 ms 306 ms 306 ms 10.22.71.17
19 296 ms 306 ms 306 ms 10.22.71.45
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * *


Facebook




Tracing route to fb.com [66.220.149.88]
over a maximum of 30 hops:

1 8 ms 2 ms 2 ms 10.10.10.1
2 5 ms 3 ms 3 ms ---.---.---.--- (CPE IP)
3 23 ms 9 ms 9 ms 192.168.170.1
4 13 ms 12 ms 12 ms ***.***.***.*** (ISP SERVER IP)
5 11 ms 11 ms 11 ms ***.***.***.*** (ISP SERVER IP)
6 15 ms 12 ms 11 ms 124.124.243.38
7 79 ms 101 ms 101 ms 115.255.252.149
8 130 ms 101 ms 101 ms 115.248.224.100
9 129 ms 101 ms 102 ms 115.248.212.246
10 223 ms 37 ms 166 ms 62.216.147.249
11 103 ms 101 ms 102 ms so-7-0-0.0.ejr03.sin001.flagtel.com [62.216.128.73]
12 124 ms 204 ms 204 ms so-0-2-0.0.pjr02.hkg005.flagtel.com [85.95.26.125]
13 125 ms 204 ms 204 ms so-5-0-0.0.cjr04.hkg003.flagtel.com [85.95.25.214]
14 124 ms 204 ms 204 ms xe-1-2-0.0.cji01.hkg003.flagtel.com [62.216.128.66]
15 125 ms 204 ms 204 ms 32934.hkg.equinix.com [119.27.63.13]
16 329 ms 306 ms 306 ms xe-10-3-0.bb01.sjc1.tfbnw.net [204.15.21.186]
17 328 ms 306 ms 307 ms ae3.dr01.snc5.tfbnw.net [74.119.77.186]
18 329 ms 306 ms 306 ms po510.csw02a.snc5.tfbnw.net [74.119.78.22]
19 329 ms 306 ms 306 ms www-slb-10-02-snc5.facebook.com [66.220.149.88]

Trace complete.





I observed direct peering of ISP with Beam tele ip, 124.124.243.38.

I will not reveal my location but according to google map, geographical distance between HY to my city(in different state) is 1200 km even though I'm getting average ping time between 13-20ms. My ISP's main AP is connected to Fiber. So, it may be possible it is connected to Beam Tele through fiber.
Beam tele is creating milestone in ISP market. I hope it explodes to many cities.
 

mgcarley

Founder, Hayai Broadband
Regulars
Jun 22, 2009
6,301
113
124.124.243.38 is a Reliance IP, not a Beam IP.

route: 124.124.0.0/16
descr: Reliance Infocomm Ltd Internet Data centre

Beam has the /16 of 124.123.x.x but of course this would not include anything in 124.124.x.x

Also, just because the whois of 123.123.243.38 says "Reliance - Navi Mumbai" doesn't mean that's where the server is physically located, even though such pings are indeed possible from your city to Mumbai or even your city to Hyderabad (in theory) - but the distance from me to you is less than half of 1200km (by road, according to Google Maps).

It is 100% certain that your ISP is connected to Reliance's backbone through Fibre (via your ISPs AP, City PoP & Core), which makes sense because your ISP buys from Reliance (and others) but Beam does not... for you to reach a Beam IP your traffic would traverse either Tata or Vodafone's network, as both your ISP and Beam buy from them.
 

acc1444

Regular
[OP]
Regulars
Aug 2, 2008
970
37
124.124.243.38 is a Reliance IP, not a Beam IP.



Beam has the /16 of 124.123.x.x but of course this would not include anything in 124.124.x.x

Also, just because the whois of 123.123.243.38 says "Reliance - Navi Mumbai" doesn't mean that's where the server is physically located, even though such pings are indeed possible from your city to Mumbai or even your city to Hyderabad (in theory) - but the distance from me to you is less than half of 1200km (by road, according to Google Maps).

It is 100% certain that your ISP is connected to Reliance's backbone through Fibre (via your ISPs AP, City PoP & Core), which makes sense because your ISP buys from Reliance (and others) but Beam does not... for you to reach a Beam IP your traffic would traverse either Tata or Vodafone's network, as both your ISP and Beam buy from them.


Yeah. I checked now. Something I mistakenly passed wrong info about 124.124.243.38 is of Beam but in real it's of Reliance.

I'm sorry. I think I might have checked two ips at the same time in which one was of Beam tele and I was confused between them because both start from 124.XX.XX.XX.

I know that whole set up of my ISP.

I asked to Area manager about infra of ISP when he visited my place,
it is simple open mesh network. One main AP is connected to ISP server via fiber which is connected to main internet backbone from ISP buys bandwidth, e.g. reliance/tata.
And then, main AP is connected to another APs through WLAN. Thus, they expand it to various areas and region. Those APs feed signals to clients. Thus, connectivity is delivered.

In tikona, they use Nanobridge to extend signal for next AP. Nanobridge is not mostly used for consumers. Sometimes they use for consumers otherwise ruckus AP is used which receive signal from nanobridge and one more nanobridge is connected with it through LAN. They call it primary secondary.