Skip to main content

AS202224

Darknet

-------------------------------

Registry

Authoritative registration data

AS number
202224
Name
Darknet
Organisation
-------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

6

Total announced

7

Announced prefixes

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

Prefixes announced by AS202224
44.31.176.0/24 IPv4 /24 not checked
2a06:a005:108d::/48 IPv6 /48 not checked
2a06:a005:b65::/48 IPv6 /48 not checked
2a0a:6044:7001::/48 IPv6 /48 RPKI valid
2a0a:6044:7002::/48 IPv6 /48 RPKI valid
2a0d:d940:2012::/48 IPv6 /48 RPKI valid
2a10:2f00:18b::/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 AS202224
Address families
4b42 Internet Exchange Point: Switzerland 100 Mbps IPv4 · IPv6
FogIXP 1,000 Mbps IPv4 · IPv6
FogIXP Frankfurt 1,000 Mbps IPv4 · IPv6
NL-ix: Main — 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 AS202224 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

13 networks seen before AS202224 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS202224 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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