asn.dev

Observed topology

AS61818 Miriam dos Santos Oliveira ME

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61818: 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
AS267647RODOLFO TREVIZAM FERMINO DE OLIVEIRA - EPPUnclassifiedIPv6357
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6318
AS28667VERO S.AResidentialIPv4 IPv6125
AS274532NET TVM SERVICOS DE INTERNET LTDAUnclassifiedIPv4 IPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267647RODOLFO TREVIZAM FERMINO DE OLIVEIRA - EPPUnclassifiedIPv4 IPv6323
AS269267ProLink Internet FibraUnclassifiedIPv4145
AS274532NET TVM SERVICOS DE INTERNET LTDAUnclassifiedIPv62

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS267647RODOLFO TREVIZAM FERMINO DE OLIVEIRA - EPPUnclassifiedIPv4 IPv6680
AS28667VERO S.AResidentialIPv4 IPv6487
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6426
AS269267ProLink Internet FibraUnclassifiedIPv4145
AS274532NET TVM SERVICOS DE INTERNET LTDAUnclassifiedIPv4 IPv65

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 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.