Observed topology

AS44869 FIBIA-P-S

Unclassified RIPE

Upstreams 1 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS44869: 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
AS31027	GlobalConnect A/S	Unclassified	IPv4 IPv6	741

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS204274	AURA Fiber A/S	Unclassified	IPv4 IPv6	328
AS203646	Energi Fyn Bredbaand A/S	Unclassified	IPv4 IPv6	151
AS43337	SB service og LollandsNet	Unclassified	IPv4	118
AS208327	Toke Hoiland-Jorgensen	Unclassified	IPv4	118
AS209327	Thomas Steen Rasmussen trading as tyktech	Unclassified	IPv4 IPv6	92
AS35637	WAOO A/S	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS31027	GlobalConnect A/S	Unclassified	IPv4 IPv6	1,666
AS204274	AURA Fiber A/S	Unclassified	IPv4 IPv6	387
AS203646	Energi Fyn Bredbaand A/S	Unclassified	IPv4 IPv6	151
AS43337	SB service og LollandsNet	Unclassified	IPv4	118
AS208327	Toke Hoiland-Jorgensen	Unclassified	IPv4	118
AS209327	Thomas Steen Rasmussen trading as tyktech	Unclassified	IPv4 IPv6	92
AS35637	WAOO A/S	Unclassified	IPv4	59

Provenance

Where this comes from

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