bgpreport

Network · data from 2026-11-12

AS132124 ICTA-LK - Information and Communication Technology Agency of Sri Lanka

Registry name: ICTA-LK - Information and Communication Technology Agency of Sri Lanka, LK · not in PeeringDB

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

Announced routes

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

220.247.225.0/24 Invalid: origin Other origin only 57 8%low visibility 33
43.224.124.0/22 Valid Other IRR onlyRADB 673 100% 66
103.11.32.0/22 Valid Other IRR onlyRADB 673 100% 66

AS-SET

AS132124 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 5 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin220.247.225.0/24ROAs covering it name AS9329, not AS132124. If AS132124 should announce it, add a ROA for AS132124.57 of 673
Route object: none220.247.225.0/24Route objects for it name AS9329. Add a route object with origin AS132124 in the RIR database for the space.57 of 673
Route object: RIR43.224.124.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.11.32.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

2402:cb00::/32RADBValid

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.