asn.dev

Observed topology

AS263283 AS263283 - JGNET - J G DE OLIVEIRA MATOS & CIA LTDA

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263283: 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
AS264200R DE MELO NEVES CONEX - MEResidentialIPv4 IPv6190
AS266009T2WEB SOLUCOES TECNOLOGICAS LTDAUnclassifiedIPv4 IPv693
AS267475Lig TelecomResidentialIPv4 IPv668
AS264221ONLINE NORTE TELECOM LTDAUnclassifiedIPv459
AS262606MICROTELL SCM LTDAResidentialIPv457
AS269180VIPNET ConexaoResidentialIPv444
AS269646G4 Telecom FibraResidentialIPv421
AS4230CLARO S.A.ResidentialIPv48
AS61884OLLA COMUNICACAO LTDAUnclassifiedIPv47

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS264200R DE MELO NEVES CONEX - MEResidentialIPv4 IPv6190
AS266009T2WEB SOLUCOES TECNOLOGICAS LTDAUnclassifiedIPv4 IPv693
AS267475Lig TelecomResidentialIPv4 IPv668
AS264221ONLINE NORTE TELECOM LTDAUnclassifiedIPv459
AS262606MICROTELL SCM LTDAResidentialIPv457
AS269180VIPNET ConexaoResidentialIPv444
AS269646G4 Telecom FibraResidentialIPv421
AS4230CLARO S.A.ResidentialIPv48
AS61884OLLA COMUNICACAO LTDAUnclassifiedIPv47

Provenance

Where this comes from

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