Skip to main content

AS46320

BLU

BLU Fibre Networks inc.

Registry

Authoritative registration data

AS number
46320
Name
BLU
Organisation
BLU Fibre Networks inc.
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

56

IPv6 prefixes

2

Total announced

58

Announced prefixes

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

Prefixes announced by AS46320
116.214.112.0/21 IPv4 /21 not checked
134.65.176.0/21 IPv4 /21 not checked
216.234.168.0/21 IPv4 /21 not checked
134.195.160.0/22 IPv4 /22 not checked
134.195.176.0/22 IPv4 /22 not checked
143.203.12.0/22 IPv4 /22 not checked
148.222.176.0/22 IPv4 /22 not checked
172.99.196.0/22 IPv4 /22 not checked
172.99.204.0/22 IPv4 /22 not checked
173.195.108.0/22 IPv4 /22 not checked
193.47.48.0/22 IPv4 /22 not checked
199.241.52.0/22 IPv4 /22 not checked
208.87.20.0/22 IPv4 /22 not checked
216.39.224.0/22 IPv4 /22 not checked
23.227.208.0/22 IPv4 /22 not checked
23.227.212.0/22 IPv4 /22 not checked
38.45.200.0/22 IPv4 /22 not checked
66.118.16.0/22 IPv4 /22 not checked
66.205.236.0/22 IPv4 /22 not checked
103.70.20.0/23 IPv4 /23 not checked
161.129.178.0/23 IPv4 /23 not checked
205.142.228.0/23 IPv4 /23 not checked
66.205.236.0/23 IPv4 /23 not checked
103.70.22.0/24 IPv4 /24 not checked
103.70.23.0/24 IPv4 /24 not checked
104.166.104.0/24 IPv4 /24 not checked
104.166.105.0/24 IPv4 /24 not checked
104.166.106.0/24 IPv4 /24 not checked
104.166.107.0/24 IPv4 /24 not checked
134.195.176.0/24 IPv4 /24 not checked
134.195.177.0/24 IPv4 /24 not checked
134.195.178.0/24 IPv4 /24 not checked
148.222.180.0/24 IPv4 /24 not checked
148.222.181.0/24 IPv4 /24 not checked
148.222.182.0/24 IPv4 /24 not checked
155.254.240.0/24 IPv4 /24 not checked
155.254.241.0/24 IPv4 /24 not checked
155.254.242.0/24 IPv4 /24 not checked
155.254.243.0/24 IPv4 /24 not checked
170.39.23.0/24 IPv4 /24 not checked
172.99.204.0/24 IPv4 /24 not checked
172.99.205.0/24 IPv4 /24 not checked
205.142.230.0/24 IPv4 /24 not checked
205.142.231.0/24 IPv4 /24 not checked
38.103.159.0/24 IPv4 /24 not checked
38.108.75.0/24 IPv4 /24 not checked
38.108.84.0/24 IPv4 /24 not checked
38.108.92.0/24 IPv4 /24 not checked
38.159.38.0/24 IPv4 /24 not checked
38.57.25.0/24 IPv4 /24 not checked
38.80.71.0/24 IPv4 /24 not checked
38.80.74.0/24 IPv4 /24 not checked
66.205.238.0/24 IPv4 /24 not checked
66.205.239.0/24 IPv4 /24 not checked
67.218.217.0/24 IPv4 /24 not checked
67.218.223.0/24 IPv4 /24 not checked
2606:3780::/32 IPv6 /32 RPKI not found
2607:1d40::/32 IPv6 /32 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 AS46320
Address families
CANIX Montreal 10,000 Mbps IPv4

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 AS46320 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS46320 in AS paths

Observed upstreams
Families
AS174 COGENT-174 422 12,236
v4 v6
AS6461 ZAYO-6461 372 6,802
v4 v6
AS6939 HURRICANE 106 1,260
v4 v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS46320 in AS paths

Observed downstreams
Families
AS20221 IATA 290 1,306
v4

No rows match “”.

Showing – of

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 74
v4 v6
AS852 ASN852 2 60
v4
AS22652 FIBRENOIRE-INTERNET 2 60
v4
AS1403 EBOX 1 39
v4 v6
AS36236 NETACTUATE 1 37
v4 v6
AS35280 F5 1 35
v4

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.