asn.dev

Observed topology

AS262404 JC SERVICOS DE INTERNET LTDA

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS262404: 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 IPv6212
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6148
AS262462Aranet PlayUnclassifiedIPv4 IPv679
AS35280F5 Networks SARLHostingIPv69
AS24482SG.GSHostingIPv4 IPv65
AS37721Virtual Technologies & SolutionsResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267650JCL TELECOMUNICACOES EIRELI - EPPUnclassifiedIPv4 IPv6264
AS267983L V SERVICOS DE TELECOMUNICACOES EIRELIUnclassifiedIPv4 IPv695

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6376
AS267650JCL TELECOMUNICACOES EIRELI - EPPUnclassifiedIPv4 IPv6264
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6252
AS262462Aranet PlayUnclassifiedIPv4 IPv6142
AS267983L V SERVICOS DE TELECOMUNICACOES EIRELIUnclassifiedIPv4 IPv695
AS24482SG.GSHostingIPv4 IPv617
AS35280F5 Networks SARLHostingIPv617
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv69

Provenance

Where this comes from

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