AS138296
STARNET7-AS
Juweriyah Networks Private Limited
Registry
Authoritative registration data
- AS number
- 138296
- Name
- STARNET7-AS
- Organisation
- Juweriyah Networks Private Limited
- Country
-
IN
India
- RIR
- APNIC
- Registered
Source:asn:rdap
retrieved
IPv4 prefixes
140
IPv6 prefixes
3
Total announced
143
Announced prefixes
Observed in BGP by route collectors, not a registry allocation list
matching
| 103.134.4.0/22 | IPv4 | /22 | not checked | |
| 103.204.132.0/22 | IPv4 | /22 | not checked | |
| 103.205.212.0/22 | IPv4 | /22 | not checked | |
| 103.207.248.0/22 | IPv4 | /22 | not checked | |
| 103.41.32.0/22 | IPv4 | /22 | not checked | |
| 27.0.148.0/22 | IPv4 | /22 | not checked | |
| 38.130.144.0/22 | IPv4 | /22 | not checked | |
| 38.20.140.0/22 | IPv4 | /22 | not checked | |
| 103.143.8.0/23 | IPv4 | /23 | not checked | |
| 103.157.178.0/23 | IPv4 | /23 | not checked | |
| 103.167.176.0/23 | IPv4 | /23 | not checked | |
| 103.115.154.0/24 | IPv4 | /24 | not checked | |
| 103.115.155.0/24 | IPv4 | /24 | not checked | |
| 103.119.172.0/24 | IPv4 | /24 | not checked | |
| 103.119.173.0/24 | IPv4 | /24 | not checked | |
| 103.119.82.0/24 | IPv4 | /24 | not checked | |
| 103.119.83.0/24 | IPv4 | /24 | not checked | |
| 103.123.154.0/24 | IPv4 | /24 | not checked | |
| 103.123.155.0/24 | IPv4 | /24 | not checked | |
| 103.123.224.0/24 | IPv4 | /24 | not checked | |
| 103.123.225.0/24 | IPv4 | /24 | not checked | |
| 103.123.226.0/24 | IPv4 | /24 | not checked | |
| 103.123.227.0/24 | IPv4 | /24 | not checked | |
| 103.124.122.0/24 | IPv4 | /24 | not checked | |
| 103.124.123.0/24 | IPv4 | /24 | not checked | |
| 103.124.22.0/24 | IPv4 | /24 | not checked | |
| 103.124.23.0/24 | IPv4 | /24 | not checked | |
| 103.127.116.0/24 | IPv4 | /24 | not checked | |
| 103.127.117.0/24 | IPv4 | /24 | not checked | |
| 103.127.252.0/24 | IPv4 | /24 | not checked | |
| 103.132.100.0/24 | IPv4 | /24 | not checked | |
| 103.132.101.0/24 | IPv4 | /24 | not checked | |
| 103.133.116.0/24 | IPv4 | /24 | not checked | |
| 103.134.4.0/24 | IPv4 | /24 | not checked | |
| 103.134.5.0/24 | IPv4 | /24 | not checked | |
| 103.134.6.0/24 | IPv4 | /24 | not checked | |
| 103.134.7.0/24 | IPv4 | /24 | not checked | |
| 103.142.106.0/24 | IPv4 | /24 | not checked | |
| 103.143.8.0/24 | IPv4 | /24 | not checked | |
| 103.143.9.0/24 | IPv4 | /24 | not checked | |
| 103.157.178.0/24 | IPv4 | /24 | not checked | |
| 103.157.179.0/24 | IPv4 | /24 | not checked | |
| 103.157.222.0/24 | IPv4 | /24 | not checked | |
| 103.157.223.0/24 | IPv4 | /24 | not checked | |
| 103.158.48.0/24 | IPv4 | /24 | not checked | |
| 103.158.49.0/24 | IPv4 | /24 | not checked | |
| 103.163.190.0/24 | IPv4 | /24 | not checked | |
| 103.163.191.0/24 | IPv4 | /24 | not checked | |
| 103.167.176.0/24 | IPv4 | /24 | not checked | |
| 103.167.177.0/24 | IPv4 | /24 | not checked | |
| 103.171.210.0/24 | IPv4 | /24 | not checked | |
| 103.171.211.0/24 | IPv4 | /24 | not checked | |
| 103.171.51.0/24 | IPv4 | /24 | not checked | |
| 103.172.156.0/24 | IPv4 | /24 | not checked | |
| 103.172.157.0/24 | IPv4 | /24 | not checked | |
| 103.172.85.0/24 | IPv4 | /24 | not checked | |
| 103.172.86.0/24 | IPv4 | /24 | not checked | |
| 103.172.87.0/24 | IPv4 | /24 | not checked | |
| 103.173.120.0/24 | IPv4 | /24 | not checked | |
| 103.173.121.0/24 | IPv4 | /24 | not checked | |
| 103.173.177.0/24 | IPv4 | /24 | not checked | |
| 103.173.205.0/24 | IPv4 | /24 | not checked | |
| 103.173.244.0/24 | IPv4 | /24 | not checked | |
| 103.173.245.0/24 | IPv4 | /24 | not checked | |
| 103.174.244.0/24 | IPv4 | /24 | not checked | |
| 103.174.245.0/24 | IPv4 | /24 | not checked | |
| 103.175.140.0/24 | IPv4 | /24 | not checked | |
| 103.175.141.0/24 | IPv4 | /24 | not checked | |
| 103.175.61.0/24 | IPv4 | /24 | not checked | |
| 103.177.180.0/24 | IPv4 | /24 | not checked | |
| 103.179.232.0/24 | IPv4 | /24 | not checked | |
| 103.179.236.0/24 | IPv4 | /24 | not checked | |
| 103.179.237.0/24 | IPv4 | /24 | not checked | |
| 103.179.46.0/24 | IPv4 | /24 | not checked | |
| 103.179.47.0/24 | IPv4 | /24 | not checked | |
| 103.181.209.0/24 | IPv4 | /24 | not checked | |
| 103.181.54.0/24 | IPv4 | /24 | not checked | |
| 103.181.55.0/24 | IPv4 | /24 | not checked | |
| 103.190.212.0/24 | IPv4 | /24 | not checked | |
| 103.190.213.0/24 | IPv4 | /24 | not checked | |
| 103.195.80.0/24 | IPv4 | /24 | not checked | |
| 103.195.81.0/24 | IPv4 | /24 | not checked | |
| 103.204.132.0/24 | IPv4 | /24 | not checked | |
| 103.204.133.0/24 | IPv4 | /24 | not checked | |
| 103.204.134.0/24 | IPv4 | /24 | not checked | |
| 103.204.135.0/24 | IPv4 | /24 | not checked | |
| 103.207.248.0/24 | IPv4 | /24 | not checked | |
| 103.207.249.0/24 | IPv4 | /24 | not checked | |
| 103.207.250.0/24 | IPv4 | /24 | not checked | |
| 103.207.251.0/24 | IPv4 | /24 | not checked | |
| 103.217.138.0/24 | IPv4 | /24 | not checked | |
| 103.217.139.0/24 | IPv4 | /24 | not checked | |
| 103.218.106.0/24 | IPv4 | /24 | not checked | |
| 103.218.107.0/24 | IPv4 | /24 | not checked | |
| 103.225.116.0/24 | IPv4 | /24 | not checked | |
| 103.225.117.0/24 | IPv4 | /24 | not checked | |
| 103.31.140.0/24 | IPv4 | /24 | not checked | |
| 103.31.141.0/24 | IPv4 | /24 | not checked | |
| 103.31.142.0/24 | IPv4 | /24 | not checked | |
| 103.31.143.0/24 | IPv4 | /24 | not checked | |
| 103.31.220.0/24 | IPv4 | /24 | not checked | |
| 103.31.221.0/24 | IPv4 | /24 | not checked | |
| 103.41.32.0/24 | IPv4 | /24 | not checked | |
| 103.41.33.0/24 | IPv4 | /24 | not checked | |
| 103.41.34.0/24 | IPv4 | /24 | not checked | |
| 103.41.35.0/24 | IPv4 | /24 | not checked | |
| 103.68.142.0/24 | IPv4 | /24 | not checked | |
| 103.68.143.0/24 | IPv4 | /24 | not checked | |
| 103.93.192.0/24 | IPv4 | /24 | not checked | |
| 103.93.193.0/24 | IPv4 | /24 | not checked | |
| 103.93.195.0/24 | IPv4 | /24 | not checked | |
| 110.44.10.0/24 | IPv4 | /24 | not checked | |
| 110.44.11.0/24 | IPv4 | /24 | not checked | |
| 157.20.86.0/24 | IPv4 | /24 | not checked | |
| 157.20.87.0/24 | IPv4 | /24 | not checked | |
| 202.179.70.0/24 | IPv4 | /24 | not checked | |
| 202.179.72.0/24 | IPv4 | /24 | not checked | |
| 202.179.73.0/24 | IPv4 | /24 | not checked | |
| 202.179.74.0/24 | IPv4 | /24 | not checked | |
| 202.179.75.0/24 | IPv4 | /24 | not checked | |
| 202.179.76.0/24 | IPv4 | /24 | not checked | |
| 202.179.79.0/24 | IPv4 | /24 | not checked | |
| 202.179.81.0/24 | IPv4 | /24 | not checked | |
| 202.179.82.0/24 | IPv4 | /24 | not checked | |
| 202.179.83.0/24 | IPv4 | /24 | not checked | |
| 202.179.84.0/24 | IPv4 | /24 | not checked | |
| 202.179.85.0/24 | IPv4 | /24 | not checked | |
| 202.179.86.0/24 | IPv4 | /24 | not checked | |
| 202.179.87.0/24 | IPv4 | /24 | not checked | |
| 202.179.88.0/24 | IPv4 | /24 | not checked | |
| 202.179.90.0/24 | IPv4 | /24 | not checked | |
| 202.179.91.0/24 | IPv4 | /24 | not checked | |
| 202.179.92.0/24 | IPv4 | /24 | not checked | |
| 202.179.93.0/24 | IPv4 | /24 | not checked | |
| 202.179.94.0/24 | IPv4 | /24 | not checked | |
| 202.179.95.0/24 | IPv4 | /24 | not checked | |
| 27.0.148.0/24 | IPv4 | /24 | not checked | |
| 27.0.149.0/24 | IPv4 | /24 | not checked | |
| 27.0.150.0/24 | IPv4 | /24 | not checked | |
| 27.0.151.0/24 | IPv4 | /24 | not checked | |
| 2404:58c0::/32 | IPv6 | /32 | not checked | |
| 2405:8540::/32 | IPv6 | /32 | RPKI not found | |
| 2001:df2:380::/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
matching
| Address families | ||
|---|---|---|
| AMS-IX Mumbai | 10,000 Mbps | IPv4 · IPv6 |
| DE-CIX Mumbai: DE-CIX Mumbai Peering LAN | 10,000 Mbps | IPv4 · IPv6 |
| Extreme IX Bangalore | 10,000 Mbps | IPv4 |
| Extreme IX Mumbai: Extreme IX | 100,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 AS138296 in BGP paths by route collectors.
Observed upstreams
8 networks seen before AS138296 in AS paths
matching
| Families | |||
|---|---|---|---|
| AS9583 SIFY-AS-IN | 4,826 | 41,472 |
v4
v6
|
| AS17762 HTIL-TTML-IN-AP | 1,739 | 10,090 |
v4
v6
|
| AS17439 NCINSPL-IN | 732 | 8,563 |
v4
|
| AS45117 INPL-IN-AP | 162 | 222 |
v4
|
| AS35280 F5 | 33 | 220 |
v4
v6
|
| AS55836 RELIANCEJIO-IN | 4 | 5 |
v6
|
| AS4755 TATACOMM-AS | 1 | 4 |
v4
|
| AS9498 BBIL-AP | 1 | 3 |
v4
v6
|
No rows match “”.
Showing – of
Observed downstreams
18 networks seen after AS138296 in AS paths
matching
| Families | |||
|---|---|---|---|
| AS149187 BILALISP-AS-IN | 1,192 | 4,621 |
v4
v6
|
| AS138311 LIMERICK-AS-IN | 1,008 | 2,029 |
v4
v6
|
| AS135733 SPEARHEAD-AS | 584 | 1,324 |
v4
|
| AS135762 CLEARBM-AS | 253 | 1,319 |
v4
|
| AS134014 NET4USERVICES-AS-IN | 491 | 1,020 |
v6
|
| AS141246 NINEST-AS-IN | 255 | 990 |
v4
|
| AS45243 FXWIRELESS-TECH-AS-AP | 281 | 902 |
v4
|
| AS149211 INFOCUS-AS-IN | 252 | 331 |
v4
|
| AS135788 VEDANT-AS-IN | 251 | 331 |
v4
|
| AS138799 FWAWSPL-AS | 248 | 326 |
v4
|
| AS141514 SANCFILT-AS-IN | 247 | 323 |
v4
|
| AS17762 HTIL-TTML-IN-AP | 60 | 320 |
v4
v6
|
| AS142169 IRINN-HIRDHAV-AS-IN | 129 | 161 |
v4
v6
|
| AS141846 NETFIX-AS-IN | 83 | 102 |
v4
|
| AS141805 HUBCOM-AS-IN | 35 | 59 |
v4
|
| AS4755 TATACOMM-AS | 30 | 40 |
v4
|
| AS55836 RELIANCEJIO-IN | 1 | 2 |
v4
|
| AS133968 LOGON-AS-IN | 1 | 2 |
v4
|
No rows match “”.
Showing – of
Uncertain adjacencies
4 adjacencies that may be an artefact of collector peering
matching
| Families | |||
|---|---|---|---|
| AS142289 ROXONIC-AS-AP | 1 | 8 |
v4
v6
|
| AS24482 SGGS-AS-AP | 1 | 4 |
v4
v6
|
| AS36236 NETACTUATE | 1 | 4 |
v4
v6
|
| AS45489 SLT-GLOBAL | 1 | 4 |
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.