26 Aug

Facebook FNA Nodes Updates

Earlier this year after APRICOT 2018, I posted a list of visible Facebook FNA (CDN caching) nodes across the world with IPv4, IPv6 and the AS name. I got quite a few mails in following months about people mentioning that they installed nodes but do not see their names in the list (and that was normal since list was static). 

I re-ran my script to see emailslatest status of nodes. During last check I saw 1689  nodes (3rd March). Now on 26th Aug i.e after close to 6 months, the total number of nodes has increased to 2204.

Here is the latest sheet containing the list of nodes with ASN, network name, IPv4 and IPv6 – http://link.anuragbhatia.com/fna30aug

Summary of the data and some findings for India

  1. The number of nodes increased by 27% within the last 6 months. 

  2. On Reliance Jio network number of node increased by just 1 – which is a new node they put in Ludhiana, Punjab. 

  3. In Delhi, a number of FNA nodes went up from 16 to 21. Four new additions are ACT (AS18209), MNR Broadband (AS133648), Facebook itself (AS63293) which is worth exploring) and GEONET GEOCITY NETWORK SOLUTIONS (AS45235). This actually makes me wonder why I do not see any FNA nodes on my ex-employer Spectra AS10029 as yet.  (30 Aug 2018 Update: I missed this, please see footer below)

  4. In case of Mumbai (or Bombay as used for BOM airport code), the number went up from 17 to 21. New additions HNS (AS38457), Airtel (AS9498) and Vortex Netsol  (AS136334). 

  5. For Chennai number stayed same at 6 (4 telco – Airtel, Jio, Vodafone, IDEA) and 2 broadband ISPs (ACT and Hathway). 

  6. In Kolkata IDEA added the new FNA node. Rest all seems the same. 

  7. I see zero active nodes in Dishnet Wireless (Aircel) now. Earlier there was one in Kolkata and one in Chennai. 

  8. Still zero active nodes in India’s largest govt. incumbent operator BSNL AS9289. They clearly do not understand the value of content caching nodes. 

  9. There’s a major growth in a number of FNA nodes in Airtel from 9 (in March) to 16 (now at the end of Aug). And for IDEA number went from 6 to 12. While the number of nodes in Vodafone stays same (14). 

  10. There’s no node in any of Tata telecom companies. 

Well, that’s all about for now. Have a good Rakshabandhan. 🙂

Update: 30th Aug 2018

My friends from Spectra pointed out that they do have a node and that made me to re-look at my scripts. Due to a bug in the scripts, I was not getting all the nodes. I have fixed the bug and updated the data in this post. 

24 Sep

Tata Communications (AS4755) pushing traffic to Reliance Jio (AS55836) via Singapore!

Bad route

So it seems like apart from voice interconnect issues, Jio is also facing routing issues on the backbone. I ran a trace to one of IP’s on Jio network allocated to end customer – 169.149.212.122.

I ran trace from all Indian RIPE Atlas probes – https://atlas.ripe.net/measurements/5738489/#!probes

There seem quite a few RIPE Atlas probes which are giving latency on 150ms + range. Seems like they are downstream or downstream of downstream of Tata Comm’s AS4755 and routing is happening via Singapore!

 

 

Two of such traces

jio1 screen-shot-2016-09-24-at-11-26-05-pm

 

This isn’t how regular routing should work since even if both do not announce routes to each other, Jio’s routes are visible at NIXI. E.g NIXI Noida shows 169.149.192.0/18 visible which covers that test IP. Tata AS4755 is probably rejecting that IP.

screen-shot-2016-09-24-at-11-31-45-pm

 

And if we look at Tata AS6453 routing table for their Chennai PoP, it shows AS_PATH as AS3431 (PCCW Global) who happens to be upstream of Jio’s International network AS64049.

screen-shot-2016-09-24-at-11-31-38-pm

 

Clearly, that’s just bad routing!

 

It might be the case Tata is doing intentionally without any evil plans because NIXI might just not have sufficient capacity. Overall ISPs should peer with PNI’s as well as we need IX’es other than just NIXI to promote more peering and promote better interconnect.

 

Disclaimer: This post and expressed comments are in my personal capacity and my employer has no relation with it. 

03 Jul

Reliance Jio orignating Charter’s /16 pool

 

Just noticed that Reliance Jio (AS55836) seems to be originating a /16 which is for Charter Communications (AS20115) – 47.35.0.0/16.

 

route-views>sh ip bgp 47.35.0.0/16 long | exclude 20115
BGP table version is 18764390, local router ID is 128.223.51.103
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network          Next Hop            Metric LocPrf Weight Path
*   47.35.0.0/16     195.208.112.161                        0 3277 3267 174 64049 55836 i
*                    217.192.89.50                          0 3303 6762 64049 55836 i
*                    212.66.96.126                          0 20912 1267 64049 55836 i
*                    162.243.188.2                          0 393406 6453 6762 64049 55836 i
*                    192.241.164.4                          0 62567 2914 174 64049 55836 i
*                    129.250.0.11          1007             0 2914 174 64049 55836 i
*                    104.192.216.1                          0 46450 174 64049 55836 i
*                    202.93.8.242                           0 24441 3491 3491 174 64049 55836 i
*                    66.59.190.221                          0 6539 577 6762 64049 55836 i
*                    144.228.241.130         80             0 1239 174 64049 55836 i
*                    207.172.6.20             0             0 6079 3356 174 64049 55836 i
*                    203.62.252.83                          0 1221 4637 174 64049 55836 i
*                    93.104.209.174                         0 58901 51167 3356 6762 64049 55836 i
Network          Next Hop            Metric LocPrf Weight Path
*                    162.250.137.254                        0 4901 174 64049 55836 i
*                    4.69.184.193             0             0 3356 174 64049 55836 i
*                    208.51.134.254           1             0 3549 3356 174 64049 55836 i
*                    89.149.178.10           10             0 3257 174 64049 55836 i
*                    66.110.0.86                            0 6453 6762 64049 55836 i
*                    134.222.87.1           650             0 286 174 64049 55836 i
*                    95.85.0.2                              0 200130 6453 174 64049 55836 i
*                    12.0.1.63                              0 7018 174 64049 55836 i
*                    173.205.57.234                         0 53364 3257 174 64049 55836 i
*                    206.24.210.80                          0 3561 174 64049 55836 i
*                    5.101.110.2                            0 202018 2914 174 64049 55836 i
*                    207.172.6.1              0             0 6079 3356 174 64049 55836 i
*                    154.11.98.225            0             0 852 174 64049 55836 i
*                    194.85.40.15                           0 3267 174 64049 55836 i
*                    208.74.64.40                           0 19214 174 64049 55836 i
*                    209.124.176.223                        0 101 101 174 64049 55836 i
*                    66.185.128.48            6             0 1668 174 64049 55836 i
*                    203.181.248.168                        0 7660 2516 6762 64049 55836 i
*                    202.232.0.2                            0 2497 701 6762 64049 55836 i
*                    103.247.3.45                           0 58511 64049 55836 i
*                    193.0.0.56                             0 3333 1103 64049 55836 i
Network          Next Hop            Metric LocPrf Weight Path
*                    80.241.176.31                          0 20771 47872 64049 55836 i
*>                   216.218.252.164                        0 6939 64049 55836 i
*                    132.198.255.253                        0 1351 174 64049 55836 i
*                    103.255.249.22                         0 58443 45177 64049 55836 i
*                    114.31.199.1                           0 4826 174 64049 55836 i
route-views>

 

This shows Reliance Jio’s ASN AS55836 announcing 47.35.0.0/16. Charter Communications (AS20115) is originating multiple of /18s out of the same pool.

 

route-views>sh ip bgp 47.35.0.0/16 long
BGP table version is 18764237, local router ID is 128.223.51.103
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network          Next Hop            Metric LocPrf Weight Path
*   47.35.0.0/18     195.208.112.161                        0 3277 3267 6939 20115 i
*                    212.66.96.126                          0 20912 6939 20115 i
*                    162.243.188.2                          0 393406 6939 20115 i
*                    192.241.164.4                          0 62567 6939 20115 i
*                    129.250.0.11          1006             0 2914 1299 20115 i
*                    4.69.184.193             0             0 3356 20115 i
*                    89.149.178.10           10             0 3257 3356 20115 i
*                    194.85.40.15                           0 3267 6939 20115 i
*                    216.218.252.164                        0 6939 20115 i

 

Let’s look for whois record of this /16 pool: https://whois.arin.net/rest/net/NET-47-32-0-0-1

NetRange: 47.32.0.0 - 47.51.255.255
CIDR: 47.32.0.0/12, 47.48.0.0/14
NetName: CC04
NetHandle: NET-47-32-0-0-1
Parent: NET47 (NET-47-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Charter Communications (CC04)
RegDate: 2014-12-23
Updated: 2014-12-23
Ref: https://whois.arin.net/rest/net/NET-47-32-0-0-1

 

It seems highly unlikely that this pool has been transferred over to Jio and hence it’s highly likely that Reliance Jio is falsely advertising this pool. Possible reason for such mistake can be because they have got 47.29.0.0/16, 47.30.0.0/16 and 47.31.0.0/16 but beyond that there are few Charter Pools. So likely someone just mistyped an IP. Another possible reason for such mistype can be that they have also got 49.35.0.0/16 (it’s 49, not 47).

What is much more fascinating is that they even have a RADB route object registered for the same.

whois -h whois.radb.net 47.35.0.0
route:      47.35.0.0/16
descr:      Route Set JIO Maharastra LTE USER Pool
origin:     AS55836
notify:     Ip.abuse@ril.com
mnt-by:     MAINT-AS55836
changed:    ip.management@ril.com 20160624
source:     RADB

 

World of BGP is interesting!

 

Update:

As per update from Mr Morlay Gosh from Reliance Jio on SANOG mailing list- This was mistake and they are removing the same.

http://article.gmane.org/gmane.org.operators.sanog/2929