asn.dev

Observed topology

AS61623 Vellon Servicos de Comunicacao Mult e Digitais

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61623: 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
AS266520TELECOMResidentialIPv4 IPv6352
AS53427TGLOBAL NETWORKSUnclassifiedIPv4 IPv694
AS26615SAMobileIPv4 IPv634

Transit

Downstream networks

All 28

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

ASNetworkTypeFamiliesPaths seen
AS262492TELEINFORMATICA EIRELIUnclassifiedIPv4 IPv6551
AS266520TELECOMResidentialIPv4 IPv6195
AS267102INTERNETUnclassifiedIPv4 IPv6127
AS263320TelecomUnclassifiedIPv4 IPv656
AS266911TelecomUnclassifiedIPv4 IPv653
AS274514TELECOM PROVEDOR DE INTERNET LTDAUnclassifiedIPv4 IPv651
AS264578MEUnclassifiedIPv4 IPv645
AS272637TELECOMUnclassifiedIPv4 IPv641
AS271695PROVEDOR & SERVICOS DE INTERNET LTDAUnclassifiedIPv4 IPv639
AS272419LTDAUnclassifiedIPv435

Adjacency

Adjacent networks

All 30

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

ASNetworkTypeFamiliesPaths seen
AS53427TGLOBAL NETWORKSUnclassifiedIPv4 IPv61,398
AS262492TELEINFORMATICA EIRELIUnclassifiedIPv4 IPv6567
AS266520TELECOMResidentialIPv4 IPv6547
AS267102INTERNETUnclassifiedIPv4 IPv6127
AS26615SAMobileIPv4 IPv6126
AS263320TelecomUnclassifiedIPv4 IPv656
AS264578MEUnclassifiedIPv4 IPv653
AS266911TelecomUnclassifiedIPv4 IPv653
AS274514TELECOM PROVEDOR DE INTERNET LTDAUnclassifiedIPv4 IPv651
AS272637TELECOMUnclassifiedIPv4 IPv641

Provenance

Where this comes from

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