asn.dev

Observed topology

AS14026 Nucleo de Inf. e Coord. do Ponto BR - NIC.

Upstreams 6 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 5
Adjacent (IPv6) 4

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS14026: 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 IPv6134
AS21574Century Telecom LtdaUnclassifiedIPv666
AS35280F5 Networks SARLHostingIPv4 IPv66
AS57463NetIX Communications JSCUnclassifiedIPv45
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv42

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 AS14026 was observed as the last hop before the origin, meaning it appears to provide them transit.

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

9 shown

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6134
AS21574Century Telecom LtdaUnclassifiedIPv666
AS35280F5 Networks SARLHostingIPv4 IPv66
AS57463NetIX Communications JSCUnclassifiedIPv45
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv42

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 AS14026, 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 35 exchanges across 1 country and 1 region.

ExchangeLocationTheir addressMember ports
IX.br (PTT.br) São PauloSão Paulo, Brazil187.16.216.562,690
IX.br (PTT.br) FortalezaFortaleza, Brazil45.68.72.3920
IX.br (PTT.br) Porto AlegrePorto Alegre, Brazil177.52.38.22347
IX.br (PTT.br) BrasíliaBrasília, Brazil45.184.144.50279
IX.br (PTT.br) CuritibaCuritiba, Brazil45.184.146.22244
IX.br (PTT.br) SalvadorSalvador, Brazil200.219.145.4206
IX.br (PTT.br) RecifeRecife, Brazil200.219.147.10204
IX.br (PTT.br) FlorianópolisFlorianópolis, Brazil200.219.141.8149
IX.br (PTT.br) Belo HorizonteBelo Horizonte, Brazil200.219.139.251120
IX.br (PTT.br) VitóriaVitória, Brazil187.16.194.3106
IX.br (PTT.br) GoiâniaGoiânia, Brazil200.192.111.1473
IX.br (PTT.br) São LuísSão Luís, Brazil45.227.0.4972
IX.br (PTT.br) MaringáMaringá, Brazil187.16.201.4670
IX.br (PTT.br) ManausManaus, Brazil187.16.198.1069
IX.br (PTT.br) BelémBelém, Brazil187.16.195.1062
IX.br (PTT.br) TeresinaTeresina, Brazil200.219.138.1662
IX.br (PTT.br) AracajuAracaju, Brazil200.219.130.1059
IX.br (PTT.br) CuiabáCuiabá, Brazil187.16.203.1059
IX.br (PTT.br) NatalNatal, Brazil187.16.196.1053
IX.br (PTT.br) Campina GrandeCampina Grande, Brazil200.192.109.2552
IX.br (PTT.br) CampinasCampinas, Brazil200.192.108.2551
IX.br (PTT.br) CascavelCascavel, Brazil45.227.3.1050
IX.br (PTT.br) Campo GrandeCampo Gande, Brazil45.227.2.348
IX.br (PTT.br) Feira de SantanaFeira De Santana, Brazil200.219.131.148
IX.br (PTT.br) LondrinaLondrina, Brazil200.219.144.1846
IX.br (PTT.br) MaceióMaceió, Brazil45.227.1.1045
IX.br (PTT.br) João PessoaJoão Pessoa, Brazil187.16.193.4343
IX.br (PTT.br) Foz do IguaçuFoz do Iguaçu, Brazil187.16.204.1033
IX.br (PTT.br) LajeadoLajeado, Brazil187.16.202.1231
IX.br (PTT.br) São José do Rio PretoSão José do Rio Preto, Brazil187.16.199.1028
IX.br (PTT.br) Porto VelhoPorto Velho, Brazil187.16.200.124
IX.br (PTT.br) Boa VistaBoa Vista, Brazil200.219.146.516
IX.br (PTT.br) Caxias do SulCaxias do Sul, Brazil187.16.197.1016
IX.br (PTT.br) Santa MariaSanta Maria, Brazil187.16.205.1012
IX.br (PTT.br) CaruaruCaruaru, Brazil200.219.140.710

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-08 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,137 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.