bgpreport

Network · data from 2026-11-12

AS210041 LCBlue Network

Registry name: WALS5H-AS Licheng MAO, CN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS210041, 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.
44.31.81.0/24 No ROA Other IRR onlyRADB 671 100% 66
2406:840:9006::/48 Valid RIR databaseAPNIC 636 100% 69
2406:840:9002::/48 Valid RIR databaseAPNIC 635 100% 68
2406:840:9003::/48 Valid RIR databaseAPNIC 635 100% 68
2406:840:9005::/48 Valid RIR databaseAPNIC 635 100% 68
2a0e:aa07:e030::/48 Valid RIR databaseRADB, RIPE 634 100% 67
2a0e:b107:272::/48 Valid RIR databaseRADB, RIPE 634 100% 68
2406:840:9000::/44 Valid RIR databaseAPNIC 633 100% 68
2406:840:9000::/48 Valid RIR databaseAPNIC 633 100% 68
2406:840:9001::/48 Valid RIR databaseAPNIC 633 100% 68
2406:840:9004::/48 Valid RIR databaseAPNIC 633 100% 68

AS-SET

AS210041'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 25 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced23
ChangePrefix or setDetailFull-table peers
ROA: none44.31.81.0/24No ROA covers it. Add a ROA for AS210041, maxLength 24.671 of 673
Route object: RIR44.31.81.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

2406:840:9000::/45APNICValid
2406:840:9000::/46APNICValid
2406:840:9000::/47APNICValid
2406:840:9002::/47APNICValid
2406:840:9004::/46APNICValid
2406:840:9004::/47APNICValid
2406:840:9006::/47APNICValid
2406:840:9007::/48APNICValid
2406:840:9008::/45APNICValid
2406:840:9008::/46APNICValid
2406:840:9008::/47APNICValid
2406:840:9008::/48APNICValid
2406:840:9009::/48APNICValid
2406:840:900a::/47APNICValid
2406:840:900a::/48APNICValid
2406:840:900b::/48APNICValid
2406:840:900c::/46APNICValid
2406:840:900c::/47APNICValid
2406:840:900c::/48APNICValid
2406:840:900d::/48APNICValid
2406:840:900e::/47APNICValid
2406:840:900e::/48APNICValid
2406:840:900f::/48APNICValid

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.