Observed topology

AS47292 SENTIA Sentia Denmark A/S

Unclassified RIPE

Upstreams 4 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 6

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47292: 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
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	3,067
AS6797	GlobalConnect AB	Unclassified	IPv4 IPv6	2,266
AS31027	GlobalConnect A/S	Unclassified	IPv4 IPv6	1,047
AS205491	Stichting NBIP-NaWas	Unclassified	IPv4	59

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS198622	Adform A/S	Unclassified	IPv4 IPv6	228
AS197861	Frej Mau Rye	Unclassified	IPv6	124
AS206749	Scalepoint A/S	Unclassified	IPv4	104
AS59626	Conscia Danmark A/S	Unclassified	IPv4 IPv6	90
AS208357	Bredbaandsforeningen Primanet	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	3,342
AS6797	GlobalConnect AB	Unclassified	IPv4 IPv6	2,530
AS31027	GlobalConnect A/S	Unclassified	IPv4 IPv6	1,113
AS198622	Adform A/S	Unclassified	IPv4 IPv6	228
AS197861	Frej Mau Rye	Unclassified	IPv6	124
AS206749	Scalepoint A/S	Unclassified	IPv4	104
AS59626	Conscia Danmark A/S	Unclassified	IPv4 IPv6	90
AS205491	Stichting NBIP-NaWas	Unclassified	IPv4	59
AS208357	Bredbaandsforeningen Primanet	Unclassified	IPv4	59

Provenance

Where this comes from

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