Observed topology

AS264637 Blue Consulting Group, S. A.

Residential AFRINIC Cable/DSL/ISP

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 4

Upstream graph Who carries AS264637, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS264637 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264637: 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.

AS	Network	Type	Families	Paths seen
AS22869	CABLECOLOR S.A.	Unclassified	IPv4	465
AS52468	UFINET PANAMA S.A.	Unclassified	IPv4 IPv6	158
AS23520	Columbus Networks USA, Inc.	Residential	IPv4	66

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS266688	Blue Consulting Group, S. A.	Unclassified	IPv4	240
AS270036	NORTVCOM, SOCIEDAD ANONIMA	Unclassified	IPv4 IPv6	150
AS269923	IHA Futura, S.A.	Unclassified	IPv4 IPv6	33

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS22869	CABLECOLOR S.A.	Unclassified	IPv4 IPv6	752
AS52468	UFINET PANAMA S.A.	Unclassified	IPv4 IPv6	294
AS266688	Blue Consulting Group, S. A.	Unclassified	IPv4	240
AS270036	NORTVCOM, SOCIEDAD ANONIMA	Unclassified	IPv4 IPv6	150
AS23520	Columbus Networks USA, Inc.	Residential	IPv4	66
AS269923	IHA Futura, S.A.	Unclassified	IPv4 IPv6	33

Provenance

Where this comes from

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