subnet.im

AS64712

As of 10th November 2026, AS64712 originates 1 IPv6 prefix. It is seen behind 1 upstream network, most often AS64905. None of its announcements have a valid RPKI ROA; 1 is 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

65.5k

Upstream graph

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

AS64712Toward the internet core
Upstream graph for AS64712: 2 neighbouring networks observed beyond it across 2 levels. The same networks are listed in the tables below.AS64712This networkAS64905AS45609Bharti Airtel Ltd…

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

3

adjacent networks

Upstreams
133%
Peers
267%
Downstreams
00%

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

Upstreams of AS64712
NetworkCountryRelationshipPathsVantage pts
AS64905—Peer11

Prefixes

The largest blocks AS64712 originates, widest first.

Largest prefixes originated by AS64712
PrefixAddressesVisibility
2401:4900:ab76::/4865.5k × /641/63

Routing health

How AS64712'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%1
  • 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

  • /4865.5k × /64100.0%1

Recent changes

Announcements that started or stopped since 11th Oct 2026.

6 announced and 12 withdrawn in all; the most recent are shown.

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