asn.dev

Observed topology

AS264827 WIRCOM S.P.A.

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264827: 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
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6273

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS273953TV COLOMBIA DIGITAL SASUnclassifiedIPv4 IPv6381
AS270065CHILE TV CABLE S.A.UnclassifiedIPv4175
AS263728Wimux EIRLUnclassifiedIPv4140
AS271778INVERSIONES EN TECNOLOGIA PULSO SPAUnclassifiedIPv459
AS266891SERVICIOS E INVERSIONES VILLASOLIS LTDA.UnclassifiedIPv458
AS269942ASOCIACION COMUNITARIA TELEBOYACAUnclassifiedIPv458
AS274940WIRCOM COLOMBIA SASUnclassifiedIPv633

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv61,177
AS273953TV COLOMBIA DIGITAL SASUnclassifiedIPv4 IPv6381
AS270065CHILE TV CABLE S.A.UnclassifiedIPv4175
AS263728Wimux EIRLUnclassifiedIPv4140
AS271778INVERSIONES EN TECNOLOGIA PULSO SPAUnclassifiedIPv459
AS266891SERVICIOS E INVERSIONES VILLASOLIS LTDA.UnclassifiedIPv458
AS269942ASOCIACION COMUNITARIA TELEBOYACAUnclassifiedIPv458
AS274940WIRCOM COLOMBIA SASUnclassifiedIPv633

Provenance

Where this comes from

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