bgpreport

Network · data from 2026-11-12

AS62529 AS-APEX - Apex Development Group LLC

Registry name: AS-APEX - Apex Development Group LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS62529, 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.
23.134.128.0/24 No ROA Other IRR onlyALTDB, RADB 2 0%low visibility 3
2602:ff12::/36 No ROA Other IRR onlyALTDB, RADB 1 0%low visibility 1

AS-SET

AS62529 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 6 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none23.134.128.0/24No ROA covers it. Add a ROA for AS62529, maxLength 24.2 of 673
Route object: RIR23.134.128.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
ROA: none2602:ff12::/36No ROA covers it. Add a ROA for AS62529, maxLength 36.1 of 636
Route object: RIR2602:ff12::/36Route object only in ALTDB, RADB. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

207.76.170.0/24ALTDBNo ROA
2607:fae0:9000::/36ALTDB, RADBValid

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.