Skip to main content

AS57048

RVDM-AS

Robert van der Meulen

Registry

Authoritative registration data

AS number
57048
Name
RVDM-AS
Organisation
Robert van der Meulen
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 AS57048
2a0e:f7c0::/29 IPv6 /29 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 AS57048
Address families
4b42 Internet Exchange Point: Switzerland 1,000 Mbps IPv6
EVIX: Peering LAN 1,000 Mbps IPv6
Frys-IX 1,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 AS57048 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS57048 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 160 226
v6
AS8283 COLOCLUE-AS 51 63
v6
AS200132 31 50
v6
AS34019 HIVANE 2 4
v6
AS5405 2 2
v6
AS39351 ESAB-AS 2 2
v6
AS58057 SECUREBIT 2 2
v6
AS211509 2 2
v6
AS398447 1 1
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS57048 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

13 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 3
v6
AS25091 IP-Max 1 3
v6
AS49544 i3Dnet 1 2
v6
AS1103 SURFNET-NL 1 1
v6
AS3399 1 1
v6
AS6424 1 1
v6
AS29075 1 1
v6
AS39122 1 1
v6
AS50629 LWLCOM 1 1
v6
AS58299 OPENFACTORY-AS 1 1
v6
AS206271 1 1
v6
AS209823 1 1
v6
AS212635 1 1
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.