subnet.im

AS47864V-NET B.V.

NetherlandsRegistryRIPE NCCTypeEyeball

As of 11th November 2026, AS47864 (V-NET B.V.), an access network registered in the Netherlands with RIPE NCC, originates 1 IPv4 prefix covering 256 addresses. By IPv4 address space that makes it the 59,976th-largest of the 80,743 networks we see originating IPv4, and the 787th-largest of 1,042 in the Netherlands. It is seen behind 10 upstream networks, most often AS60299 (Mezhdugorodnyaya Mezhdunarodnaya…) and AS1299 (Arelion (fka. Telia Carrier)), 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

1

IPv6 prefixes

0

IPv4 addresses

256

IPv6 /64s

0

Upstream graph

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

Networks observed one and two hops upstream of AS47864 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

57

adjacent networks

Upstreams
1018%
Peers
4681%
Downstreams
12%

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

Prefixes

The largest blocks AS47864 originates, widest first.

Largest prefixes originated by AS47864
PrefixAddressesVisibility
185.217.60.0/2425676/76

Routing health

How AS47864'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%1
  • Invalid0.0%0
  • No ROA0.0%0

Propagation

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

Prefix sizes

IPv4 — 1 prefixes

Recent changes

Announcements that started or stopped since 12th Oct 2026.

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