bgpreport

Network · data from 2026-11-12

AS64513

Not in the RIR AS name list · not in PeeringDB

AS64513 is Reserved for Private Use (RFC 6996) in IANA's AS number registries. The routes below have it as their origin anyway, as seen by the collectors' peers.

25IPv4 routes 0.0% RPKI valid · 0.0% with a route object
1IPv6 routes 0.0% RPKI valid · 0.0% with a route object
6RPKI invalid 6 origin · 0 maxLength
20No ROA 26 with no route object for this origin
26Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS64513, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS64513, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

41.155.117.0/24 Invalid: origin None 23 3%low visibility 18
103.88.139.0/24 Invalid: origin Other origin only 6 1%low visibility 5
217.151.205.32/32 Invalid: origin None 1 0%low visibility 1
217.151.205.48/32 Invalid: origin None 1 0%low visibility 1
103.87.238.0/24 Invalid: origin Other origin only 0 0%low visibility 1
2406:9d40:100::/48 Invalid: origin None 0 0%low visibility 1
100.65.32.0/20 bogon No ROA None 1 0%low visibility 1
102.176.95.0/24 No ROA Other origin only 51 8%low visibility 31
102.176.92.0/24 No ROA Other origin only 48 7%low visibility 29
102.176.102.0/24 No ROA Other origin only 18 3%low visibility 10
102.176.65.0/24 No ROA Other origin only 15 2%low visibility 9
102.176.77.0/24 No ROA Other origin only 8 1%low visibility 4
102.176.78.0/24 No ROA Other origin only 8 1%low visibility 4
197.251.240.0/24 No ROA Other origin only 8 1%low visibility 4
62.150.101.0/24 No ROA Other origin only 1 0%low visibility 1
66.110.194.0/23 No ROA Other origin only 1 0%low visibility 1
74.81.168.0/24 No ROA Other origin only 1 0%low visibility 1
74.81.190.0/24 No ROA Other origin only 1 0%low visibility 1
166.98.10.0/24 No ROA None 1 0%low visibility 1
199.182.56.0/24 No ROA Other origin only 1 0%low visibility 1
199.182.57.0/24 No ROA Other origin only 1 0%low visibility 1
199.182.58.0/24 No ROA Other origin only 1 0%low visibility 1
199.182.59.0/24 No ROA Other origin only 1 0%low visibility 1
204.27.160.0/24 No ROA Other origin only 1 0%low visibility 1
208.97.29.0/24 No ROA Other origin only 1 0%low visibility 1
213.189.82.0/24 No ROA Other origin only 1 0%low visibility 1

AS-SET

AS64513 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 3 are in fix.csv.

  • Bogon origin1
  • Bogon prefix1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Bogon originAS64513AS64513 is Reserved for Private Use (RFC 6996) in IANA's AS number registries; 26 routes in the global table have it as their origin.
Bogon prefix100.65.32.0/20In IANA's special-purpose registry: Shared Address Space (RFC 6598).1 of 673

Route objects not announced

Route objects with origin AS64513 whose prefix no peer sees AS64513 announce. Many are kept on purpose (backup routes, space announced only in some places).

43.231.31.0/24APNICValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.