asn.dev

Observed topology

AS262416 AS262416 - KASPER, GOBBI E SOARES LTDA

Hosting RIPE

Upstreams 6 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 3
Upstream graph Who carries AS262416, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS262416 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262416: 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
AS28283Adylnet TelecomResidentialIPv4311
AS28146MHNET TELECOMResidentialIPv4 IPv6224
AS16735ALGAR TELECOM S/AUnclassifiedIPv432
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv416
AS6939Hurricane Electric LLCTransitIPv615
AS24482SG.GSHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS269592Adoro Monitoramento LtdaUnclassifiedIPv4122
AS265923DEFLEX TELECOM EIRELI - MEResidentialIPv423

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28146MHNET TELECOMResidentialIPv4 IPv6369
AS28283Adylnet TelecomResidentialIPv4311
AS269592Adoro Monitoramento LtdaUnclassifiedIPv4122
AS16735ALGAR TELECOM S/AUnclassifiedIPv432
AS265923DEFLEX TELECOM EIRELI - MEResidentialIPv423
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv416
AS6939Hurricane Electric LLCTransitIPv615
AS24482SG.GSHostingIPv61

Provenance

Where this comes from

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