asn.dev

Observed topology

AS266435 THE FIBER INTERNET BANDA LARGA

Upstreams 27 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 29
Adjacent (IPv6) 9

Transit

Upstream networks

inferred

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 IPv6346
AS3356Level 3 Parent, LLCTransitIPv4 IPv654
AS37468Angola CablesUnclassifiedIPv4 IPv641
AS34549meerfarbig GmbH & Co. KGHostingIPv424
AS33891Core-Backbone GmbHHostingIPv412
AS50304Blix Solutions ASUnclassifiedIPv412
AS57463NetIX Communications JSCUnclassifiedIPv410
AS267613ELETRONET S.A.UnclassifiedIPv48
AS37100SEACOM LimitedUnclassifiedIPv46
AS12552GlobalConnect ABUnclassifiedIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS48362Stadtwerke FeldkirchResidentialIPv46
AS1103SURF B.V.UnclassifiedIPv46
AS12779IT.Gate S.p.A.UnclassifiedIPv46
AS50300CustodianDC LimitedUnclassifiedIPv46
AS24482SG.GSHostingIPv46
AS3741Dimension DataUnclassifiedIPv46
AS3216PJSC "Vimpelcom"MobileIPv44
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv44
AS17639Converge ICT Solutions Inc.UnclassifiedIPv44
AS22652Videotron LteeResidentialIPv44
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv63
AS1836green.ch AGResidentialIPv42
AS34019Hivane AssociationUnclassifiedIPv42
AS32097WholeSale Internet, Inc.HostingIPv42
AS20485Joint Stock Company TransTeleComUnclassifiedIPv42
AS212024Marc SchmittUnclassifiedIPv42

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.

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 IPv677
AS270930NIVEL 3 TELECOM LTDAUnclassifiedIPv461

Adjacency

Adjacent networks

38 shown

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6426
AS3356Level 3 Parent, LLCTransitIPv4 IPv6149
AS266403Bom Link Net Trindade GOUnclassifiedIPv4 IPv677
AS267568R. C. F. TELECOM LTDA MEHostingIPv665
AS270930NIVEL 3 TELECOM LTDAUnclassifiedIPv461
AS37468Angola CablesUnclassifiedIPv4 IPv656
AS34549meerfarbig GmbH & Co. KGHostingIPv424
AS50304Blix Solutions ASUnclassifiedIPv412
AS57463NetIX Communications JSCUnclassifiedIPv412
AS33891Core-Backbone GmbHHostingIPv412
AS24482SG.GSHostingIPv4 IPv69
AS1103SURF B.V.UnclassifiedIPv4 IPv69
AS267613ELETRONET S.A.UnclassifiedIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS37100SEACOM LimitedUnclassifiedIPv46
AS48362Stadtwerke FeldkirchResidentialIPv46
AS12552GlobalConnect ABUnclassifiedIPv46
AS50300CustodianDC LimitedUnclassifiedIPv46
AS3741Dimension DataUnclassifiedIPv46
AS12779IT.Gate S.p.A.UnclassifiedIPv46
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv65
AS22652Videotron LteeResidentialIPv44
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv44
AS3216PJSC "Vimpelcom"MobileIPv44
AS17639Converge ICT Solutions Inc.UnclassifiedIPv44
AS32097WholeSale Internet, Inc.HostingIPv42
AS212024Marc SchmittUnclassifiedIPv42
AS20485Joint Stock Company TransTeleComUnclassifiedIPv42
AS34019Hivane AssociationUnclassifiedIPv42
AS1836green.ch AGResidentialIPv42
AS213241TECHIT.BE SRLResidentialIPv61

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.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS266435, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 11 exchanges across 6 countries and 3 regions.

ExchangeLocationTheir addressMember ports
IX.br (PTT.br) São PauloSão Paulo, Brazil187.16.213.1482,690
DE-CIX FrankfurtFrankfurt, Germany80.81.194.1431,073
LINX LON1London, United Kingdom195.66.228.91925
IX.br (PTT.br) FortalezaFortaleza, Brazil45.68.74.220920
AMS-IX AmsterdamAmsterdam, Netherlands80.249.215.5894
DE-CIX New YorkNew York, United States206.82.104.147279
IX.br (PTT.br) BrasíliaBrasília, Brazil45.184.144.163279
Equinix Internet Exchange MiamiMiami, United States198.32.242.105175
IX.br (PTT.br) GoiâniaGoiânia, Brazil200.192.111.6273
DE-CIX LisbonLisbon, Portugal185.1.131.6463
Equinix-LA(former Paix) retiredLos Angeles, United States198.32.242.105

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.