bgpreport

Network · data from 2026-11-12

AS218867 SYZ-AS Sun Youzhi

Registry name: SYZ-AS Sun Youzhi, CN · not in PeeringDB

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

Announced routes

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

2a0f:1180::/30 Invalid: origin None 1 0%low visibility 1
2a0f:1184::/30 Invalid: origin None 1 0%low visibility 1
2a0d:88c4::/30 No ROA None 3 0%low visibility 3
2a0d:88c0::/30 No ROA None 1 0%low visibility 1

AS-SET

AS218867 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 9 are in fix.csv.

  • ROA: origin2
  • ROA: none2
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin2a0f:1180::/30ROAs covering it name AS54694, AS197200, AS197210, AS219100, AS219476, AS401163, not AS218867. If AS218867 should announce it, add a ROA for AS218867.1 of 636
Route object: none2a0f:1180::/30No route object for it. Add a route object with origin AS218867 in the RIR database for the space.1 of 636
ROA: origin2a0f:1184::/30ROAs covering it name AS54694, AS197200, AS197210, AS219100, AS219476, AS401163, not AS218867. If AS218867 should announce it, add a ROA for AS218867.1 of 636
Route object: none2a0f:1184::/30No route object for it. Add a route object with origin AS218867 in the RIR database for the space.1 of 636
ROA: none2a0d:88c4::/30No ROA covers it. Add a ROA for AS218867, maxLength 30.3 of 636
Route object: none2a0d:88c4::/30No route object for it. Add a route object with origin AS218867 in the RIR database for the space.3 of 636
ROA: none2a0d:88c0::/30No ROA covers it. Add a ROA for AS218867, maxLength 30.1 of 636
Route object: none2a0d:88c0::/30No route object for it. Add a route object with origin AS218867 in the RIR database for the space.1 of 636

Route objects not announced

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

2a0a:d687:ff05::/48RIPEValid

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.