Observed topology
AS274672 INOVANOC SOLUCOES EM SUPORTE LTDA
Unclassified LACNIC
Transit
Upstream networks
Networks observed carrying traffic for AS274672: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS28188 | Net Ltda. | Unclassified | IPv6 | 66 |
| AS263903 | TELECOM | Unclassified | IPv6 | 37 |
| AS273666 | E FARIAS LTDA ME | Unclassified | IPv6 | 37 |
| AS264997 | Telecom Ltda | Unclassified | IPv6 | 36 |
| AS266009 | SOLUCOES TECNOLOGICAS LTDA | Unclassified | IPv6 | 36 |
| AS263290 | DIGITAL SERVICOS EM COMUNICACAO LTDA | Unclassified | IPv6 | 34 |
| AS272510 | Net Provedor Ltda | Unclassified | IPv6 | 34 |
| AS271529 | TELECOM.IP LTDA ME | Hosting | IPv6 | 31 |
| AS14840 | Telecom | Unclassified | IPv6 | 28 |
| AS268568 | TELECOM SOCIEDADE LIMITADA | Unclassified | IPv6 | 28 |
Transit
Downstream networks
Networks for which AS274672 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS274672 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS28188 | Net Ltda. | Unclassified | IPv6 | 102 |
| AS263903 | TELECOM | Unclassified | IPv6 | 74 |
| AS266009 | SOLUCOES TECNOLOGICAS LTDA | Unclassified | IPv6 | 72 |
| AS268267 | TELECOMUNICACOES LTDA | Unclassified | IPv4 IPv6 | 66 |
| AS53014 | Provedor de Internet Ltda | Unclassified | IPv4 IPv6 | 63 |
| AS273666 | E FARIAS LTDA ME | Unclassified | IPv6 | 37 |
| AS274371 | SILVA DE SOUSA | Unclassified | IPv6 | 37 |
| AS264997 | Telecom Ltda | Unclassified | IPv6 | 36 |
| AS263290 | DIGITAL SERVICOS EM COMUNICACAO LTDA | Unclassified | IPv6 | 34 |
| AS272510 | Net Provedor Ltda | Unclassified | IPv6 | 34 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.