Skip to main content

AS214953

MRICKL

++++++++++++++++++++++++++++++++++++

Registry

Authoritative registration data

AS number
214953
Name
MRICKL
Organisation
++++++++++++++++++++++++++++++++++++
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

4

Total announced

4

Announced prefixes

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

Prefixes announced by AS214953
2a0c:9a46:1900::/44 IPv6 /44 RPKI valid
2a0c:9a46:1910::/44 IPv6 /44 RPKI valid
2a0c:9a46:1920::/44 IPv6 /44 RPKI valid
2a0c:9a46:1930::/44 IPv6 /44 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 AS214953
Address families
FogIXP 1,000 Mbps IPv6
LOCIX DUSSELDORF: Peering LAN 1,000 Mbps 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 AS214953 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS214953 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 95 378
v6
AS212895 ROUTE64_ORG 139 166
v6
AS34927 iFog-GmbH 24 81
v6
AS34872 Servperso_Systems 9 36
v6
AS39351 ESAB-AS 1 3
v6
AS401753 BIXCE 1 3
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS214953 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 6
v6
AS25091 IP-Max 1 3
v6
AS58299 OPENFACTORY-AS 1 3
v6
AS199854 ITBYPASSION 1 3
v6
AS210937 Showfom 1 3
v6
AS213151 CHRISELSEN 1 3
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.