asn.dev

Observed topology

AS216129 GuardNetwork-AS SEBEK sp. z o.o

Unclassified RIPE

Upstreams 8 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 5
Upstream graph Who carries AS216129, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS216129 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS216129: 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.

ASNetworkTypeFamiliesPaths seen
AS60068Datacamp LimitedHostingIPv4 IPv6774
AS48729ServerKing B.V.UnclassifiedIPv4 IPv6414
AS59796StormWall s.r.o.UnclassifiedIPv4174
AS201814MEVSPACE sp. z o.o.HostingIPv4 IPv6101
AS204957ROUTE 95 LLCUnclassifiedIPv4 IPv699
AS50979ROUTE 95 LLCUnclassifiedIPv4 IPv691
AS44901Belcloud LTDHostingIPv460
AS43298Storm Networks LLCUnclassifiedIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213633SEBEK sp. z o.oUnclassifiedIPv421

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS60068Datacamp LimitedHostingIPv4 IPv6795
AS48729ServerKing B.V.UnclassifiedIPv4 IPv6414
AS59796StormWall s.r.o.UnclassifiedIPv4174
AS201814MEVSPACE sp. z o.o.HostingIPv4 IPv6101
AS204957ROUTE 95 LLCUnclassifiedIPv4 IPv699
AS50979ROUTE 95 LLCUnclassifiedIPv4 IPv691
AS44901Belcloud LTDHostingIPv460
AS213633SEBEK sp. z o.oUnclassifiedIPv421
AS43298Storm Networks LLCUnclassifiedIPv46

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.