subnet.im

AS210233Pixinko SARL

BelgiumRegistryRIPE NCC

As of 27th September 2026, AS210233 (Pixinko SARL), a network registered in Belgium with RIPE NCC, originates 1 IPv6 prefix. It is seen behind 10 upstream networks, most often AS8298 (IPng Networks GmbH) and AS25091 (IP-Max SA), and in front of 4 downstream networks. Every one of its announcements has a valid RPKI ROA, and none are RPKI-invalid. 0% of its routes reach at least 90% of full-feed peers, and 1 prefix is also originated by another network.

At a glance

IPv4 prefixes

0

IPv6 prefixes

1

IPv4 addresses

0

IPv6 /64s

1M

Upstream graph

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

AS210233Toward the internet core

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

51

adjacent networks

Upstreams
1020%
Peers
3773%
Downstreams
48%

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

Prefixes

The largest blocks AS210233 originates, widest first.

Largest prefixes originated by AS210233
PrefixAddressesVisibility
2a0c:b641:870::/441M × /6410/64

Routing health

How AS210233'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 more0.0%0
  • Partially propagated40% to 90%0.0%0
  • Seen by few peersUnder 40%100.0%1

Prefix sizes

IPv6 — 1 prefixes

  • /441M × /64100.0%1

Recent changes

Announcements that started or stopped since 28th Aug 2026.

No announcement by AS210233 started or stopped in this period.

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