asn.dev

Observed topology

AS43140 TELEFLASH-AS

Unclassified RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS43140: 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
AS203440linefinity GmbHUnclassifiedIPv4153
AS5405Inter.link GmbHUnclassifiedIPv4137
AS6939Hurricane Electric LLCTransitIPv420
AS34549meerfarbig GmbH & Co. KGHostingIPv415
AS17639Converge ICT Solutions Inc.UnclassifiedIPv45
AS20485Joint Stock Company TransTeleComUnclassifiedIPv45
AS24482SG.GSHostingIPv45
AS34019Hivane AssociationUnclassifiedIPv45
AS37721Virtual Technologies & SolutionsResidentialIPv45
AS48362Stadtwerke FeldkirchResidentialIPv45

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS203440linefinity GmbHUnclassifiedIPv4207

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS203440linefinity GmbHUnclassifiedIPv4360
AS5405Inter.link GmbHUnclassifiedIPv4274
AS6939Hurricane Electric LLCTransitIPv440
AS34549meerfarbig GmbH & Co. KGHostingIPv430
AS17639Converge ICT Solutions Inc.UnclassifiedIPv410
AS20485Joint Stock Company TransTeleComUnclassifiedIPv410
AS24482SG.GSHostingIPv410
AS34019Hivane AssociationUnclassifiedIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv410
AS48362Stadtwerke FeldkirchResidentialIPv410

All 11 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.