subnet.im

AS215577Lucas van Beek

NetherlandsRegistryRIPE NCC

As of 27th September 2026, AS215577 (Lucas van Beek), a network registered in the Netherlands with RIPE NCC, originates 3 IPv6 prefixes. It is seen behind 17 upstream networks, most often AS211588 (Innovation Harbor B.V.) and AS9002 (RETN Limited), and in front of 1 downstream network. Every one of its announcements has a valid RPKI ROA, and none are RPKI-invalid. 100% of its routes reach at least 90% of full-feed peers.

At a glance

IPv4 prefixes

0

IPv6 prefixes

3

IPv4 addresses

0

IPv6 /64s

1.2M

Upstream graph

The networks AS215577 is seen behind, one and two hops out, drawn from real AS paths.

Networks observed one and two hops upstream of AS215577 in real AS paths. A thicker line means more vantage points saw that adjacency, so weight tracks how well attested it is — not how much traffic it carries. Adjacency is an observation; whether it is a transit purchase or a settlement-free peering is an inference, and is labelled as one wherever we show it.

Neighbouring networks

99

adjacent networks

Upstreams
1717%
Peers
8182%
Downstreams
11%

Networks carrying this one's traffic toward the rest of the internet.

Prefixes

The largest blocks AS215577 originates, widest first.

Largest prefixes originated by AS215577
PrefixAddressesVisibility
2a07:54c7:5f00::/441M × /6464/64
2a07:54c7:5f10::/4865.5k × /6464/64
2a07:e345:200::/4865.5k × /6464/64

Routing health

How AS215577's own announcements validate against RPKI and how far they propagate. The same measures for the whole routing table are on the routing table in numbers.

RPKI origin validation

  • Valid100.0%3
  • Invalid0.0%0
  • No ROA0.0%0

Propagation

  • Globally propagated90% of full-feed peers or more100.0%3
  • Partially propagated40% to 90%0.0%0
  • Seen by few peersUnder 40%0.0%0

Prefix sizes

IPv6 — 3 prefixes

  • /441M × /6433.3%1
  • /4865.5k × /6466.7%2

Recent changes

Announcements that started or stopped since 28th Aug 2026.

  • Withdrawn2a07:54c7:5ffe::/4821st Sept 2026

Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.