AS64563
As of 27th September 2026, AS64563 originates 2 IPv6 prefixes. It is seen behind 2 upstream networks, most often AS64585 and AS23956 (AmberIT Limited), and in front of 1 downstream network. None of its announcements have a valid RPKI ROA; 2 are RPKI-invalid. 0% of its routes reach at least 90% of full-feed peers, and 2 prefixes are also originated by another network.
At a glance
IPv4 prefixes
IPv6 prefixes
IPv4 addresses
IPv6 /64s
Upstream graph
The networks AS64563 is seen behind, one and two hops out, drawn from real AS paths.
Networks observed one and two hops upstream of AS64563 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
6
adjacent networks
- Upstreams
- 233%
- Peers
- 350%
- Downstreams
- 117%
Networks carrying this one's traffic toward the rest of the internet.
| Network | Country | Relationship | Paths | Vantage pts |
|---|---|---|---|---|
| AS64585 | — | Peer | 5 | 3 |
| AS23956AmberIT Limited | Peer | 4 | 2 |
Prefixes
The largest blocks AS64563 originates, widest first.
| Prefix | Addresses | Visibility |
|---|---|---|
| 2405:7600:47c0::/44 | 1M × /64 | 2/64 |
| 2405:7600:47d0::/44 | 1M × /64 | 2/64 |
Routing health
How AS64563'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
- Valid0.0%0
- Invalid100.0%2
- 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%2
Prefix sizes
IPv6 — 2 prefixes
- /441M × /64100.0%2
Recent changes
Announcements that started or stopped since 28th Aug 2026.
- Announced2405:7600:47c0::/4422nd Sept 2026
- Announced2405:7600:47d0::/4422nd Sept 2026
Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.