Skip to main content

AS396216

BRIDGEDBB-01

Bridged Broadband, LLC

Registry

Authoritative registration data

AS number
396216
Name
BRIDGEDBB-01
Organisation
Bridged Broadband, LLC
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

2

Total announced

5

Announced prefixes

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

Prefixes announced by AS396216
66.242.62.0/23 IPv4 /23 not checked
66.242.62.0/24 IPv4 /24 not checked
66.242.63.0/24 IPv4 /24 not checked
2602:f475::/36 IPv6 /36 not checked
2602:f475::/37 IPv6 /37 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 AS396216
Address families
KCIX 100,000 Mbps IPv4 · IPv6
OmahaIX 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 AS396216 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS396216 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 1,547 64,920
v4 v6
AS1299 TWELVE99 560 15,711
v4 v6

No rows match “”.

Showing of

Observed downstreams

3 networks seen after AS396216 in AS paths

Observed downstreams
Families
AS395582 540 31,920
v4
AS33616 446 31,581
v4
AS394778 811 15,266
v4 v6

No rows match “”.

Showing of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS1003 ANDREWNET 1 2
v4
AS36236 NETACTUATE 1 2
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.