asn.dev

Observed topology

AS262832 Infotechnet Informatica e Assistencia Tecnica Ltda

Upstreams 6 carry this network
Downstreams 7 this network carries
Adjacent (IPv4) 13
Adjacent (IPv6) 5

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262832: 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
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv4282
AS53087TELY Ltda.ResidentialIPv4 IPv6127
AS24482SG.GSHostingIPv4 IPv616
AS35280F5 Networks SARLHostingIPv4 IPv616
AS57463NetIX Communications JSCUnclassifiedIPv414
AS37721Virtual Technologies & SolutionsResidentialIPv414

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

ASNetworkTypeFamiliesPaths seen
AS265024Radio Ativo Servicos de Internet LTDAUnclassifiedIPv4219
AS262338IKNET INTERNET KARIRI LTDAResidentialIPv4187
AS28188Pronto Net Ltda.UnclassifiedIPv4 IPv699
AS263866RADIONET TELECOM LTDAUnclassifiedIPv4 IPv669
AS275741LIGEIRA TELECOMUNICACOES LTDAUnclassifiedIPv462
AS271680STAFF DIGITAL INTERNET BANDA LARGA EIRELIUnclassifiedIPv462
AS263592FRANCISCO MARQUES VIEIRA GONCALVES MEUnclassifiedIPv44

Adjacency

Adjacent networks

18 shown

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

ASNetworkTypeFamiliesPaths seen
AS53087TELY Ltda.ResidentialIPv4 IPv6793
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv4282
AS265024Radio Ativo Servicos de Internet LTDAUnclassifiedIPv4219
AS262338IKNET INTERNET KARIRI LTDAResidentialIPv4187
AS28188Pronto Net Ltda.UnclassifiedIPv4 IPv699
AS263866RADIONET TELECOM LTDAUnclassifiedIPv4 IPv669
AS271680STAFF DIGITAL INTERNET BANDA LARGA EIRELIUnclassifiedIPv462
AS275741LIGEIRA TELECOMUNICACOES LTDAUnclassifiedIPv462
AS24482SG.GSHostingIPv4 IPv635
AS57463NetIX Communications JSCUnclassifiedIPv428
AS35280F5 Networks SARLHostingIPv4 IPv618
AS37721Virtual Technologies & SolutionsResidentialIPv415
AS263592FRANCISCO MARQUES VIEIRA GONCALVES MEUnclassifiedIPv44

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

ExchangeLocationTheir addressMember ports
IX.br (PTT.br) São PauloSão Paulo, Brazil187.16.210.1652,690
IX.br (PTT.br) FortalezaFortaleza, Brazil45.68.73.228920

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.