Skip to main content

AS213973

BCIX-OUTREACH

BCIX Management GmbH

Registry

Authoritative registration data

AS number
213973
Name
BCIX-OUTREACH
Organisation
BCIX Management GmbH
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

0

Total announced

0

Announced prefixes

No announced prefixes observed

Route collectors saw no announcements from this AS, or the routing data source was unavailable.

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS213973
Address families
BCIX: BCIX Peering LAN 100,000 Mbps IPv4 · IPv6
DD-IX 10,000 Mbps IPv4 · IPv6
SON-IX 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 AS213973 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS213973 in AS paths

Observed upstreams
Families
AS8218 NEO-ASN 14 99
v4 v6
AS39351 ESAB-AS 4 15
v4 v6
AS50629 LWLCOM 3 3
v4
AS20562 OPEN-PEERING-AS 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

5 networks seen after AS213973 in AS paths

Observed downstreams
Families
AS216188 Host-Unlimited 7 98
v4 v6
AS62365 DESANET-AS 5 44
v4
AS42 WOODYNET-1 9 14
v4
AS203592 cnh-primary 4 12
v4 v6
AS208508 LHDD-AS 6 8
v4

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 4 33
v4 v6
AS24961 MYLOC-AS 3 14
v4 v6
AS13237 LAMBDANET-AS 2 11
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.