Observed topology

AS263947 VirtualSpace Telecom

Unclassified APNIC

Upstreams 5 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS263947: 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
AS61745	NBS TELECOM	Unclassified	IPv4 IPv6	118
AS263661	BRASIL DIGITAL SERVICOS DE INFORMATICA E COMERCIO	Residential	IPv4	68
AS267589	SH TELECOM LTDA	Unclassified	IPv4	60
AS267424	BR364 SERVICOS DE TELECOMUNICACOES LTDA	Unclassified	IPv4	34
AS266337	MARLON LIMA GOMES ME	Unclassified	IPv6	33

Transit

Downstream networks

inferred

Networks for which AS263947 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 AS263947 in a routing path, in either direction.

AS	Network	Type	Families	Paths seen
AS61745	NBS TELECOM	Unclassified	IPv4 IPv6	118
AS263661	BRASIL DIGITAL SERVICOS DE INFORMATICA E COMERCIO	Residential	IPv4	68
AS267589	SH TELECOM LTDA	Unclassified	IPv4	60
AS267424	BR364 SERVICOS DE TELECOMUNICACOES LTDA	Unclassified	IPv4	34
AS266337	MARLON LIMA GOMES ME	Unclassified	IPv6	33

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.