bgpreport

Network · data from 2026-11-12

AS38616 Worldcall Telecom

Registry name: WORLDCALL-AS-KHI - Worldcall Telecom Limited, PK · PeeringDB

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

Announced routes

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

115.186.0.0/24 Valid RIR databaseAPNIC, RIPE-NONAUTH 672 100% 69

AS-SET

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

  • Route object: not announced12

Route objects not announced

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

111.88.136.0/23RADBNo ROA
111.88.160.0/22RADBNo ROA
111.88.164.0/22RADBNo ROA
111.88.184.0/22RADBNo ROA
111.88.188.0/22RADBNo ROA
111.119.164.0/22RADBNo ROA
115.186.80.0/22RADBNo ROA
202.125.124.0/24RADBNo ROA
203.90.12.0/24RADBNo ROA
203.90.13.0/24RADBNo ROA
203.90.14.0/24RADBNo ROA
203.90.15.0/24RADBNo 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.