asn.dev

Observed topology

AS206892 RENDSZERINF Rendszerinformatika Zrt.

Unclassified ARIN

Upstreams 4 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 7
Adjacent (IPv6) 5
Upstream graph Who carries AS206892, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS206892 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS206892: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6378
AS9002RETN LimitedUnclassifiedIPv4 IPv6230
AS6939Hurricane Electric LLCTransitIPv4 IPv697
AS33891Core-Backbone GmbHHostingIPv411

Transit

Downstream networks

inferred

Networks for which AS206892 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS210966Data Center Solutions Kft.HostingIPv4 IPv673
AS207107NNG Kft.UnclassifiedIPv462
AS47710Porion-Digital Kft.UnclassifiedIPv439
AS47343Rendszerinformatika Zrt.UnclassifiedIPv634

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS206892 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6494
AS9002RETN LimitedUnclassifiedIPv4 IPv6304
AS6939Hurricane Electric LLCTransitIPv4 IPv6114
AS210966Data Center Solutions Kft.HostingIPv4 IPv673
AS207107NNG Kft.UnclassifiedIPv462
AS47710Porion-Digital Kft.UnclassifiedIPv439
AS47343Rendszerinformatika Zrt.UnclassifiedIPv634
AS33891Core-Backbone GmbHHostingIPv412

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-01 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.48M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.