AS206604RIPE NCC ASN block
As of 27th September 2026, AS206604 (RIPE NCC ASN block), a network registered in Ukraine with RIPE NCC, originates 1 IPv6 prefix. It is seen behind 2 upstream networks, most often AS8772 (NetAssist LLC) and AS29632 (Netassist International EOOD). 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
IPv6 prefixes
IPv4 addresses
IPv6 /64s
Upstream graph
The networks AS206604 is seen behind, one and two hops out, drawn from real AS paths.
Networks observed one and two hops upstream of AS206604 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
4
adjacent networks
- Upstreams
- 250%
- Peers
- 250%
- Downstreams
- 00%
Networks carrying this one's traffic toward the rest of the internet.
| Network | Country | Relationship | Paths | Vantage pts |
|---|---|---|---|---|
| AS8772NetAssist LLC | Peer | 35 | 35 | |
| AS29632Netassist International EOOD | Peer | 29 | 29 |
Prefixes
The largest blocks AS206604 originates, widest first.
| Prefix | Addresses | Visibility |
|---|---|---|
| 2a0f:b240:6900::/40 | 16.8M × /64 | 64/64 |
Routing health
How AS206604'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
IPv6 — 1 prefixes
- /4016.8M × /64100.0%1
Recent changes
Announcements that started or stopped since 28th Aug 2026.
- Announced2a0f:b240:6900::/4022nd Sept 2026
- Withdrawn2a0f:b240:69ed::/4821st Sept 2026
Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.