asn.dev

Observed topology

AS28919 STWKUFSTEIN-AS Fischergries 2

Residential RIPE

Upstreams 21 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 18
Adjacent (IPv6) 12
Upstream graph Who carries AS28919, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS28919 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS28919: 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
AS21013eww agUnclassifiedIPv4 IPv6766
AS8412T-Mobile Austria GmbHResidentialIPv4 IPv6183
AS6939Hurricane Electric LLCTransitIPv4167
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv665
AS24482SG.GSHostingIPv4 IPv625
AS34019Hivane AssociationUnclassifiedIPv4 IPv625
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv625
AS3303Swisscom (Schweiz) AGResidentialIPv420
AS6797GlobalConnect ABUnclassifiedIPv420
AS20485Joint Stock Company TransTeleComUnclassifiedIPv420

All 21 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS199931Kommunalbetriebe Hopfgarten GmbHUnclassifiedIPv4312

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS21013eww agUnclassifiedIPv4 IPv6970
AS199931Kommunalbetriebe Hopfgarten GmbHUnclassifiedIPv4312
AS6939Hurricane Electric LLCTransitIPv4203
AS8412T-Mobile Austria GmbHResidentialIPv4 IPv6183
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv683
AS24482SG.GSHostingIPv4 IPv631
AS34019Hivane AssociationUnclassifiedIPv4 IPv631
AS3303Swisscom (Schweiz) AGResidentialIPv426
AS6797GlobalConnect ABUnclassifiedIPv426
AS20485Joint Stock Company TransTeleComUnclassifiedIPv426

All 22 adjacent →

Provenance

Where this comes from

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