Skip to main content

AS151690

FAB1-AS-IN

FAB FIVE NETWORK PRIVATE LIMITED

Registry

Authoritative registration data

AS number
151690
Name
FAB1-AS-IN
Organisation
FAB FIVE NETWORK PRIVATE LIMITED
Country
Flag of India IN India
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

35

IPv6 prefixes

8

Total announced

43

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS151690
103.109.220.0/24 IPv4 /24 not checked
103.109.221.0/24 IPv4 /24 not checked
103.109.222.0/24 IPv4 /24 not checked
103.109.223.0/24 IPv4 /24 not checked
103.110.244.0/24 IPv4 /24 not checked
103.110.245.0/24 IPv4 /24 not checked
103.115.128.0/24 IPv4 /24 not checked
103.147.93.0/24 IPv4 /24 not checked
103.162.74.0/24 IPv4 /24 not checked
103.162.75.0/24 IPv4 /24 not checked
103.172.56.0/24 IPv4 /24 not checked
103.216.99.0/24 IPv4 /24 not checked
103.225.70.0/24 IPv4 /24 not checked
103.239.12.0/24 IPv4 /24 not checked
103.239.13.0/24 IPv4 /24 not checked
103.52.33.0/24 IPv4 /24 RPKI valid
151.158.178.0/24 IPv4 /24 not checked
154.22.138.0/24 IPv4 /24 not checked
160.187.207.0/24 IPv4 /24 not checked
160.19.35.0/24 IPv4 /24 not checked
160.191.124.0/24 IPv4 /24 not checked
160.191.125.0/24 IPv4 /24 not checked
163.128.66.0/24 IPv4 /24 not checked
165.99.142.0/24 IPv4 /24 not checked
165.99.143.0/24 IPv4 /24 not checked
38.128.112.0/24 IPv4 /24 not checked
38.128.113.0/24 IPv4 /24 not checked
38.128.116.0/24 IPv4 /24 not checked
38.128.117.0/24 IPv4 /24 not checked
38.196.186.0/24 IPv4 /24 not checked
38.196.187.0/24 IPv4 /24 not checked
43.228.166.0/24 IPv4 /24 not checked
43.228.167.0/24 IPv4 /24 not checked
43.230.132.0/24 IPv4 /24 not checked
43.230.133.0/24 IPv4 /24 not checked
2401:19a0::/32 IPv6 /32 not checked
2401:a8a0::/32 IPv6 /32 not checked
2001:978:b00::/48 IPv6 /48 not checked
2001:df2:23c0::/48 IPv6 /48 not checked
2001:df2:9640::/48 IPv6 /48 RPKI valid
2001:df3:29c0::/48 IPv6 /48 not checked
2001:df4:88c0::/48 IPv6 /48 not checked
2001:df5:9cc0::/48 IPv6 /48 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS151690
Address families
AMS-IX Mumbai 10,000 Mbps IPv4 · IPv6
DE-CIX Mumbai: DE-CIX Mumbai Peering LAN 10,000 Mbps IPv4
Extreme IX Chennai: Extreme IX LAN 10,000 Mbps IPv4 · IPv6
Extreme IX Delhi: Extreme IX LAN 100,000 Mbps IPv4 · IPv6
Extreme IX Kolkata: Extreme IX LAN 10,000 Mbps IPv4 · IPv6
Extreme IX Mumbai: Extreme IX 110,000 Mbps IPv4 · IPv6
MX-IX Kolkata: Main 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS151690 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS151690 in AS paths

Observed upstreams
Families
AS9498 BBIL-AP 9,623 20,821
v4 v6
AS18229 CTRLS-AS-IN 6,576 18,742
v4 v6
AS133007 UCN-AS 279 1,045
v4
AS4755 TATACOMM-AS 536 684
v4
AS133982 EXCITEL-AS-IN 262 345
v4
AS45528 TIKONAIN-AS 262 344
v4
AS18002 WORLDPHONE-IN 191 260
v4
AS9583 SIFY-AS-IN 10 24
v6
AS153252 RGCOMP-AS-IN 4 6
v4

No rows match “”.

Showing – of

Observed downstreams

42 networks seen after AS151690 in AS paths

No rows match “”.

Showing – of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS142289 ROXONIC-AS-AP 27 134
v4
AS24482 SGGS-AS-AP 26 66
v4
AS36236 NETACTUATE 26 66
v4
AS45489 SLT-GLOBAL 26 66
v4
AS35280 F5 22 56
v4 v6

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.