bgpreport

Network · data from 2026-11-12

AS138984 SLT-NW2 - Sri Lanka Telecom Ltd

Registry name: SLT-NW2 - Sri Lanka Telecom Ltd, LK · not in PeeringDB

4IPv4 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
52Route objects not announced registered with origin AS138984, seen from no peer

Announced routes

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

203.96.160.0/22 Valid RIR databaseAPNIC, RADB 673 100% 66
203.96.160.0/23 Valid RIR databaseAPNIC 673 100% 66
112.134.56.0/22 Valid RIR databaseAPNIC 672 100% 67
112.134.60.0/22 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS138984 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 52 are in fix.csv.

  • Route object: not announced52

Route objects not announced

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

112.134.16.0/20APNICValid
112.134.16.0/21APNICValid
112.134.16.0/22APNICValid
112.134.16.0/23APNICValid
112.134.16.0/24APNICValid
112.134.17.0/24APNICValid
112.134.18.0/23APNICValid
112.134.18.0/24APNICValid
112.134.19.0/24APNICValid
112.134.20.0/22APNICValid
112.134.20.0/23APNICValid
112.134.20.0/24APNICValid
112.134.21.0/24APNICValid
112.134.22.0/23APNICValid
112.134.22.0/24APNICValid
112.134.23.0/24APNICValid
112.134.24.0/21APNICValid
112.134.24.0/22APNICValid
112.134.24.0/23APNICValid
112.134.24.0/24APNICValid
112.134.25.0/24APNICValid
112.134.26.0/23APNICValid
112.134.26.0/24APNICValid
112.134.27.0/24APNICValid
112.134.28.0/22APNICValid
112.134.28.0/23APNICValid
112.134.28.0/24APNICValid
112.134.29.0/24APNICValid
112.134.30.0/23APNICValid
112.134.30.0/24APNICValid
112.134.31.0/24APNICValid
112.134.56.0/21APNICValid
112.134.56.0/23APNICValid
112.134.56.0/24APNICValid
112.134.57.0/24APNICValid
112.134.58.0/23APNICValid
112.134.58.0/24APNICValid
112.134.59.0/24APNICValid
112.134.60.0/23APNICValid
112.134.60.0/24APNICValid
112.134.61.0/24APNICValid
112.134.62.0/23APNICValid
112.134.62.0/24APNICValid
112.134.63.0/24APNICValid
203.96.160.0/24APNICValid
203.96.161.0/24APNICValid
203.96.162.0/23APNICValid
203.96.162.0/24APNICValid
203.96.163.0/24APNICValid
2402:d000:10c0::/43APNICValid
2402:d000:10e0::/44APNICValid
2402:d000:10f0::/44APNICValid

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.