asn.dev

Observed topology

AS24822 OPCNET-HU-AS OPC Networks Kft.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS24822: 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
AS29278Rackhost Zrt.HostingIPv4159
AS6939Hurricane Electric LLCTransitIPv4 IPv641
AS41206United Telecom Zartkoruen Mukodo ReszvenytarsasagUnclassifiedIPv613
AS9002RETN LimitedUnclassifiedIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS212910Oros-Com Ltd.UnclassifiedIPv4183
AS212707KeviWLAN Informatikai Kft.UnclassifiedIPv4 IPv6138
AS213869WiNext Kft.UnclassifiedIPv444

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS29278Rackhost Zrt.HostingIPv4472
AS212910Oros-Com Ltd.UnclassifiedIPv4183
AS212707KeviWLAN Informatikai Kft.UnclassifiedIPv4 IPv6138
AS6939Hurricane Electric LLCTransitIPv4 IPv675
AS213869WiNext Kft.UnclassifiedIPv444
AS41206United Telecom Zartkoruen Mukodo ReszvenytarsasagUnclassifiedIPv627
AS9002RETN LimitedUnclassifiedIPv68

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-04 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.33M 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.