asn.dev

Observed topology

AS197889 MICROSYSTEM

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS197889: 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
AS41206United Telecom Zartkoruen Mukodo ReszvenytarsasagUnclassifiedIPv4 IPv6448
AS12301One Hungary Ltd.UnclassifiedIPv4 IPv6373
AS6939Hurricane Electric LLCTransitIPv4 IPv6217
AS39679JZT Informatikai Kft.HostingIPv419
AS29657Last-Mile Ltd.ResidentialIPv412
AS8447A1 Telekom Austria AGResidentialIPv46
AS33891Core-Backbone GmbHHostingIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS211326Incom Technologies Kft.UnclassifiedIPv4118
AS15985Pipenet Informatics and Securities Bt.UnclassifiedIPv459
AS207349Opennetworks Kft.UnclassifiedIPv415

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS41206United Telecom Zartkoruen Mukodo ReszvenytarsasagUnclassifiedIPv4 IPv6571
AS12301One Hungary Ltd.UnclassifiedIPv4 IPv6416
AS6939Hurricane Electric LLCTransitIPv4 IPv6239
AS211326Incom Technologies Kft.UnclassifiedIPv4118
AS15985Pipenet Informatics and Securities Bt.UnclassifiedIPv459
AS39679JZT Informatikai Kft.HostingIPv419
AS207349Opennetworks Kft.UnclassifiedIPv415
AS29657Last-Mile Ltd.ResidentialIPv412
AS33891Core-Backbone GmbHHostingIPv48
AS8447A1 Telekom Austria AGResidentialIPv46

Provenance

Where this comes from

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