asn.dev

Observed topology

AS268510 JS INTERNET

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268510: 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
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4 IPv659
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv647
AS52873Softdados TelecomunicacoesUnclassifiedIPv4 IPv646
AS264592ENLACE TELECOMUnclassifiedIPv424
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv410
AS28368SOBRALNET SERVICOS E TELECOMUNICACOES LTDA - MEResidentialIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267319CAROLINE SANTOS DA SILVAUnclassifiedIPv4 IPv6156
AS264592ENLACE TELECOMUnclassifiedIPv4 IPv648

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52873Softdados TelecomunicacoesUnclassifiedIPv4 IPv6324
AS264592ENLACE TELECOMUnclassifiedIPv4 IPv6178
AS267319CAROLINE SANTOS DA SILVAUnclassifiedIPv4 IPv6156
AS61832DB3 SERVICOS DE TELECOMUNICACOES S.AUnclassifiedIPv4 IPv659
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv647
AS28598DB3 SERVICOS DE TELECOMUNICACOES S.AResidentialIPv442
AS28368SOBRALNET SERVICOS E TELECOMUNICACOES LTDA - MEResidentialIPv62

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.