Skip to main content

AS61421

KRIEGER

Rogier Krieger / vNode.net

Registry

Authoritative registration data

AS number
61421
Name
KRIEGER
Organisation
Rogier Krieger / vNode.net
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS61421
149.245.254.0/23 IPv4 /23 not checked
2a0f:9207:24::/48 IPv6 /48 RPKI valid

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 AS61421
Address families
AMS-IX 1,000 Mbps IPv4 · IPv6
Clue-IX 1,000 Mbps IPv4 · IPv6
EVIX: Peering LAN 1,000 Mbps IPv4 · IPv6
Frys-IX 10,000 Mbps 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 AS61421 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS61421 in AS paths

Observed upstreams
Families
AS8283 COLOCLUE-AS 281 479
v4 v6
AS6939 HURRICANE 157 218
v4 v6
AS211509 RUDAKI-AS 2 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS61421 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS37989 DCS1PTELTD-AS-AP 1 1
v6
AS58057 SECUREBIT 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.