Skip to main content

AS215737

BOUHUIS-AS

Marnix Bouhuis

Registry

Authoritative registration data

AS number
215737
Name
BOUHUIS-AS
Organisation
Marnix Bouhuis
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

1

Total announced

1

Announced prefixes

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

Prefixes announced by AS215737
2001:67c:2924::/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 AS215737
Address families
AMS-IX 1,000 Mbps IPv6
Frys-IX 10,000 Mbps IPv6
INTERIX 10,000 Mbps 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 AS215737 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS215737 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 144 200
v6
AS8283 COLOCLUE-AS 55 84
v6
AS34019 HIVANE 2 4
v6
AS48362 TKSWF-AS 2 4
v6
AS5405 2 2
v6
AS6057 6057 2 2
v6
AS8298 IPNG 2 2
v6
AS39351 ESAB-AS 2 2
v6
AS1764 NEXTLAYER-AS 1 1
v6
AS4230 ASN4230 1 1
v6
AS41051 1 1
v6
AS401753 1 1
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS215737 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

49 adjacencies that may be an artefact of collector peering

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.