bgpreport

Network · data from 2026-11-12

AS200959 Sunflyer Global Experiment Network

Registry name: SUNFLYER-AS Yaoxuan Chen, CN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200959, 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.
2a06:a005:e50::/44 No ROA Other IRR onlyRADB 636 100% 68
2a06:a005:e70::/44 No ROA Other IRR onlyRADB 636 100% 68
2a06:a005:2040::/44 No ROA Other IRR onlyRADB 634 100% 67
2a06:a005:2048::/48 No ROA RIR databaseALTDB, RIPE 635 100% 68
2a0a:6040:6c40::/44 Valid RIR databaseRIPE 636 100% 68
2a0a:6040:e541::/48 Valid RIR databaseALTDB, RIPE 636 100% 68
2a0a:6040:e544::/48 Valid RIR databaseALTDB, RADB, RIPE 636 100% 69
2a0a:6040:e54c::/48 Valid RIR databaseALTDB, RIPE 636 100% 68
2a0e:b107:1a40::/46 Valid RIR databaseALTDB, RADB, RIPE 636 100% 69
2a0a:6040:e543::/48 Valid RIR databaseALTDB, RADB, RIPE 635 100% 68

AS-SET

AS200959'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 19 are in fix.csv.

  • ROA: none4
  • Route object: RIR3
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none2a06:a005:e50::/44No ROA covers it. Add a ROA for AS200959, maxLength 44.636 of 636
Route object: RIR2a06:a005:e50::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2a06:a005:e70::/44No ROA covers it. Add a ROA for AS200959, maxLength 44.636 of 636
Route object: RIR2a06:a005:e70::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2a06:a005:2040::/44No ROA covers it. Add a ROA for AS200959, maxLength 44.634 of 636
Route object: RIR2a06:a005:2040::/44Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2a06:a005:2048::/48No ROA covers it. Add a ROA for AS200959, maxLength 48.635 of 636

Route objects not announced

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

2a06:a005:204c::/46ALTDB, RADBNo ROA
2a0a:6040:6c00::/40RADB, RIPEValid
2a0a:6040:e500::/40ALTDB, RADB, RIPEValid
2a0a:6040:e540::/44RADB, RIPEValid
2a0a:6040:e545::/48RIPEValid
2a0a:6040:e546::/48ALTDB, RADB, RIPEValid
2a0a:6040:e54b::/48ALTDB, RADB, RIPEValid
2a0a:6040:e54d::/48ALTDB, RIPEValid
2a0e:b107:1a40::/44RIPEValid
2a0e:b107:1a44::/46RIPEValid
2a0e:b107:1a48::/46RIPEValid
2a0e:b107:1a4c::/46RIPEValid

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.