Skip to main content

AS212625

CLEMENTD

Clement Dubreuil

Registry

Authoritative registration data

AS number
212625
Name
CLEMENTD
Organisation
Clement Dubreuil
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

3

Total announced

3

Announced prefixes

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

Prefixes announced by AS212625
2a0c:b641:2b0::/48 IPv6 /48 RPKI valid
2a0c:b641:2b1::/48 IPv6 /48 RPKI valid
2a0c:b641:2b2::/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 AS212625
Address families
LOCIX DUSSELDORF: Peering LAN 1,000 Mbps IPv4 · IPv6
LOCIX FRANKFURT: Peering LAN 1,000 Mbps IPv4 · IPv6
ixFabric - Dusseldorf 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 AS212625 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS212625 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 164 444
v6
AS34872 Servperso_Systems 268 401
v6
AS25091 IP-Max 2 8
v6
AS210233 Pixinko 6 7
v6
AS8298 IPNG 2 4
v6
AS48646 STEFAN6 2 3
v6
AS401753 BIXCE 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS212625 in AS paths

Observed downstreams
Families
AS34872 Servperso_Systems 15 18
v6

No rows match “”.

Showing – of

Uncertain adjacencies

9 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.