bgpreport

Network · data from 2026-11-12

AS65013

Not in the RIR AS name list · not in PeeringDB

AS65013 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.

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS65013, 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.

187.84.244.0/24 Invalid: origin Other origin only 1 0%low visibility 1
187.84.245.0/24 Invalid: origin Other origin only 1 0%low visibility 1
177.131.8.0/24 Invalid: origin None 0 0%low visibility 1
177.131.9.0/24 Invalid: origin None 0 0%low visibility 1
2804:c90:1300::/42 Invalid: origin Other origin only 0 0%low visibility 1
149.51.236.0/24 No ROA Other origin only 4 1%low visibility 4

AS-SET

AS65013 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 2 are in fix.csv.

  • Bogon origin1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Bogon originAS65013AS65013 is Reserved for Private Use (RFC 6996) in IANA's AS number registries; 6 routes in the global table have it as their origin.

Route objects not announced

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

2607:9bc0:1030::/44ARINValid

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.