bgpreport

Network · data from 2026-11-12

AS138644 FASTMOS2-AS-AP

Registry name: FASTMOS2-AS-AP - FASTMOS CO., LIMITED, HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS138644, 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.
191.124.140.0/22 No ROA RIR databaseAPNIC 1 0%low visibility 1
191.124.144.0/20 No ROA RIR databaseAPNIC 1 0%low visibility 1
191.124.160.0/19 No ROA RIR databaseAPNIC 1 0%low visibility 1
191.124.192.0/18 No ROA RIR databaseAPNIC 1 0%low visibility 1

AS-SET

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

  • ROA: none4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none191.124.140.0/22No ROA covers it. Add a ROA for AS138644, maxLength 22.1 of 673
ROA: none191.124.144.0/20No ROA covers it. Add a ROA for AS138644, maxLength 20.1 of 673
ROA: none191.124.160.0/19No ROA covers it. Add a ROA for AS138644, maxLength 19.1 of 673
ROA: none191.124.192.0/18No ROA covers it. Add a ROA for AS138644, maxLength 18.1 of 673

Route objects not announced

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

162.4.40.0/24APNICInvalid: origin
162.4.41.0/24APNICInvalid: origin
191.124.0.0/16RADBNo 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.