asn.dev

Observed topology

AS203440 LFTY-AS

Unclassified RIPE

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS203440: 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
AS43140Teleflash GmbHUnclassifiedIPv4132
AS174Cogent Communications, LLCTransitIPv4115
AS6939Hurricane Electric LLCTransitIPv437
AS34549meerfarbig GmbH & Co. KGHostingIPv418
AS47138PLANinterNET GmbHUnclassifiedIPv410
AS6797GlobalConnect ABUnclassifiedIPv46
AS24482SG.GSHostingIPv46
AS33891Core-Backbone GmbHHostingIPv46
AS17639Converge ICT Solutions Inc.UnclassifiedIPv45
AS20485Joint Stock Company TransTeleComUnclassifiedIPv45

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS43140Teleflash GmbHUnclassifiedIPv4233

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS43140Teleflash GmbHUnclassifiedIPv4365
AS174Cogent Communications, LLCTransitIPv4230
AS6939Hurricane Electric LLCTransitIPv474
AS34549meerfarbig GmbH & Co. KGHostingIPv436
AS47138PLANinterNET GmbHUnclassifiedIPv420
AS6797GlobalConnect ABUnclassifiedIPv412
AS24482SG.GSHostingIPv412
AS33891Core-Backbone GmbHHostingIPv412
AS17639Converge ICT Solutions Inc.UnclassifiedIPv410
AS20485Joint Stock Company TransTeleComUnclassifiedIPv410

All 15 adjacent →

Provenance

Where this comes from

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