bgpreport

Network · data from 2026-11-12

AS216411 GZ_REMITTANCE GZ REMITTANCE (CHINA) INDUSTRY LIMITED

Registry name: GZ_REMITTANCE GZ REMITTANCE (CHINA) INDUSTRY LIMITED, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS216411, 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.
103.101.204.0/23 Invalid: origin Other origin only 2 0%low visibility 2
103.101.204.0/24 Invalid: origin Other origin only 1 0%low visibility 1
103.101.205.0/24 Invalid: origin Other origin only 1 0%low visibility 1
115.42.60.0/24 Valid RIR databaseAPNIC 671 100% 67
178.236.46.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS216411 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: origin3
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: origin103.101.204.0/23ROAs covering it name AS154602, not AS216411. If AS216411 should announce it, add a ROA for AS216411.2 of 673
Route object: none103.101.204.0/23Route objects for it name AS154602. Add a route object with origin AS216411 in the RIR database for the space.2 of 673
ROA: origin103.101.204.0/24ROAs covering it name AS154602, not AS216411. If AS216411 should announce it, add a ROA for AS216411.1 of 673
Route object: none103.101.204.0/24Route objects for it name AS154602. Add a route object with origin AS216411 in the RIR database for the space.1 of 673
ROA: origin103.101.205.0/24ROAs covering it name AS154602, not AS216411. If AS216411 should announce it, add a ROA for AS216411.1 of 673
Route object: none103.101.205.0/24Route objects for it name AS154602. Add a route object with origin AS216411 in the RIR database for the space.1 of 673

Route objects not announced

Every route object with origin AS216411 is announced.

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.