asn.dev

Observed topology

AS266435 THE FIBER INTERNET BANDA LARGA

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

All 31

Networks observed carrying traffic for AS266435: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6387
AS3356Level 3 Parent, LLCTransitIPv4 IPv6139
AS52573Une Telecom LtdaResidentialIPv4 IPv632
AS37468Angola CablesUnclassifiedIPv4 IPv627
AS34549meerfarbig GmbH & Co. KGHostingIPv421
AS50304Blix Solutions ASUnclassifiedIPv414
AS33891Core-Backbone GmbHHostingIPv410
AS1103SURF B.V.UnclassifiedIPv47
AS3741Dimension DataUnclassifiedIPv47
AS12552GlobalConnect ABUnclassifiedIPv47

All 31 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS266403Bom Link Net Trindade GOUnclassifiedIPv4 IPv693
AS270930NIVEL 3 TELECOM LTDAUnclassifiedIPv461

Adjacency

Adjacent networks

All 35

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6444
AS3356Level 3 Parent, LLCTransitIPv4 IPv6319
AS267568R. C. F. TELECOM LTDA MEHostingIPv4 IPv6201
AS37468Angola CablesUnclassifiedIPv4 IPv6125
AS266403Bom Link Net Trindade GOUnclassifiedIPv4 IPv693
AS270930NIVEL 3 TELECOM LTDAUnclassifiedIPv461
AS52573Une Telecom LtdaResidentialIPv4 IPv632
AS34549meerfarbig GmbH & Co. KGHostingIPv421
AS50304Blix Solutions ASUnclassifiedIPv414
AS1103SURF B.V.UnclassifiedIPv4 IPv613

All 35 adjacent →

Provenance

Where this comes from

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