bgpreport

Network · data from 2026-11-12

AS329542 MAGE

Registry name: MAGE - MAGE, CD · PeeringDB

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

Announced routes

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

2c0f:60c0::/34 No ROA None 363 57% 64
2c0f:60c0:4000::/34 No ROA None 363 57% 64
2c0f:60c0:8000::/34 No ROA None 363 57% 64
2c0f:60c0:c000::/34 No ROA None 363 57% 64
102.205.208.0/24 No ROA RIR databaseAFRINIC, RADB 672 100% 67
102.205.210.0/24 No ROA RIR databaseAFRINIC, RADB 672 100% 67
102.205.211.0/24 No ROA RIR databaseAFRINIC, RADB 672 100% 67

AS-SET

AS329542's PeeringDB record names no 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 13 are in fix.csv.

  • ROA: none7
  • Route object: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2c0f:60c0::/34No ROA covers it. Add a ROA for AS329542, maxLength 34.363 of 636
Route object: none2c0f:60c0::/34No route object for it. Add a route object with origin AS329542 in the RIR database for the space.363 of 636
ROA: none2c0f:60c0:4000::/34No ROA covers it. Add a ROA for AS329542, maxLength 34.363 of 636
Route object: none2c0f:60c0:4000::/34No route object for it. Add a route object with origin AS329542 in the RIR database for the space.363 of 636
ROA: none2c0f:60c0:8000::/34No ROA covers it. Add a ROA for AS329542, maxLength 34.363 of 636
Route object: none2c0f:60c0:8000::/34No route object for it. Add a route object with origin AS329542 in the RIR database for the space.363 of 636
ROA: none2c0f:60c0:c000::/34No ROA covers it. Add a ROA for AS329542, maxLength 34.363 of 636
Route object: none2c0f:60c0:c000::/34No route object for it. Add a route object with origin AS329542 in the RIR database for the space.363 of 636
ROA: none102.205.208.0/24No ROA covers it. Add a ROA for AS329542, maxLength 24.672 of 673
ROA: none102.205.210.0/24No ROA covers it. Add a ROA for AS329542, maxLength 24.672 of 673
ROA: none102.205.211.0/24No ROA covers it. Add a ROA for AS329542, maxLength 24.672 of 673

Route objects not announced

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

102.205.208.0/22AFRINICNo ROA
102.205.209.0/24AFRINIC, RADBNo ROA

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.