Observed topology

AS47630 TELEVOIP-AS

Unclassified RIPE NSP

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 8

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47630: 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
AS8220	COLT Technology Services Group Limited	Hosting	IPv4 IPv6	444
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	323
AS2914	NTT America, Inc.	Transit	IPv4 IPv6	244
AS48408	Localitel bvba	Unclassified	IPv4 IPv6	66
AS34019	Hivane Association	Unclassified	IPv4 IPv6	20
AS45049	Mohamed El Bouddunti	Residential	IPv4 IPv6	20
AS48185	team.blue NV	Unclassified	IPv4 IPv6	20

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS211184	Unitix BV	Unclassified	IPv6	33

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS8220	COLT Technology Services Group Limited	Hosting	IPv4 IPv6	462
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	323
AS2914	NTT America, Inc.	Transit	IPv4 IPv6	257
AS48408	Localitel bvba	Unclassified	IPv4 IPv6	68
AS211184	Unitix BV	Unclassified	IPv6	33
AS34019	Hivane Association	Unclassified	IPv4 IPv6	20
AS45049	Mohamed El Bouddunti	Residential	IPv4 IPv6	20
AS48185	team.blue NV	Unclassified	IPv4 IPv6	20

Provenance

Where this comes from

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