Skip to main content

AS204254

HUEBEL-AS

NevaKee.de

Registry

Authoritative registration data

AS number
204254
Name
HUEBEL-AS
Organisation
NevaKee.de
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

5

Total announced

5

Announced prefixes

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

Prefixes announced by AS204254
2a07:6fc6::/32 IPv6 /32 RPKI valid
2001:67c:754::/48 IPv6 /48 RPKI valid
2001:67c:758::/48 IPv6 /48 not checked
2001:67c:75c::/48 IPv6 /48 RPKI valid
2a00:f826:a::/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 AS204254
Address families
KleyReX: Peering LAN 100 Mbps IPv6
LOCIX FRANKFURT: Peering LAN 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 AS204254 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS204254 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 113 750
v6
AS34549 MEER-AS 90 587
v6
AS25091 IP-Max 3 25
v6
AS48646 STEFAN6 1 5
v6
AS401753 BIXCE 1 5
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS204254 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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