asn.dev

Observed topology

AS8319 NETHINKS-AS NETHINKS GmbH

Unclassified RIPE

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS8319: 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
AS33891Core-Backbone GmbHHostingIPv4 IPv6357
AS34309Link11 GmbHUnclassifiedIPv4186
AS6939Hurricane Electric LLCTransitIPv4 IPv6104
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv626
AS21385Trusted Network GmbHUnclassifiedIPv418
AS24482SG.GSHostingIPv4 IPv610
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv610
AS212024Marc SchmittUnclassifiedIPv4 IPv610
AS6797GlobalConnect ABUnclassifiedIPv48
AS8551Bezeq International Ltd.UnclassifiedIPv48

All 17 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44018active logistics GmbHUnclassifiedIPv480
AS47432Klinikum Fulda gAGUnclassifiedIPv459
AS30787Jumo GmbH & Co. KGUnclassifiedIPv440

Adjacency

Adjacent networks

All 21

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

ASNetworkTypeFamiliesPaths seen
AS33891Core-Backbone GmbHHostingIPv4 IPv6472
AS34309Link11 GmbHUnclassifiedIPv4230
AS6939Hurricane Electric LLCTransitIPv4 IPv6104
AS44018active logistics GmbHUnclassifiedIPv480
AS47432Klinikum Fulda gAGUnclassifiedIPv459
AS30787Jumo GmbH & Co. KGUnclassifiedIPv440
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv635
AS21385Trusted Network GmbHUnclassifiedIPv420
AS24482SG.GSHostingIPv4 IPv613
AS212024Marc SchmittUnclassifiedIPv4 IPv613

All 21 adjacent →

Provenance

Where this comes from

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