Observed topology

AS51815 TEKNIKBYRAN

Unclassified APNIC

Upstreams 1 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51815: 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
AS3399	Obenet AB	Unclassified	IPv4 IPv6	1,200

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS57131	IP Osteraker AB	Unclassified	IPv4	406
AS60582	Winther Wireless AB	Unclassified	IPv4	285
AS60662	DataCom Group Nordic AB	Unclassified	IPv4	171
AS56700	Osterakers Kommun	Unclassified	IPv4 IPv6	90
AS60184	OCTN Networks AB	Unclassified	IPv4	57
AS39648	DataCom Group Nordic AB	Unclassified	IPv6	7

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3399	Obenet AB	Unclassified	IPv4 IPv6	2,273
AS57131	IP Osteraker AB	Unclassified	IPv4	406
AS60582	Winther Wireless AB	Unclassified	IPv4	285
AS60662	DataCom Group Nordic AB	Unclassified	IPv4	228
AS56700	Osterakers Kommun	Unclassified	IPv4 IPv6	90
AS60184	OCTN Networks AB	Unclassified	IPv4	57
AS39648	DataCom Group Nordic AB	Unclassified	IPv6	7

Provenance

Where this comes from

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