bgpreport

Network · data from 2026-11-12

AS137187 WLINK-CDN-AS-AP - WorldLink Communications

Registry name: WLINK-CDN-AS-AP - WorldLink Communications, NP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS137187, 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.
124.41.244.0/22 Invalid: origin Other origin only 2 0%low visibility 2
103.211.150.0/23 Valid RIR databaseAPNIC 671 100% 66
103.211.151.0/24 Valid RIR databaseAPNIC 671 100% 66
169.136.70.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
103.211.150.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

AS137187 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 2 are in fix.csv.

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin124.41.244.0/22ROAs covering it name AS17501, not AS137187. If AS137187 should announce it, add a ROA for AS137187.2 of 673
Route object: none124.41.244.0/22Route objects for it name AS17501. Add a route object with origin AS137187 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS137187 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.