bgpreport

Network · data from 2026-11-12

AS154086 Liberty Telecommunication Private Limited

Registry name: LIBERTY-AS-AP - Liberty Telecommunication Private Limited, PK · PeeringDB

2IPv4 routes 50.0% RPKI valid · 50.0% 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 AS154086, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS154086, 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.33.239.0/24 Invalid: origin Other origin only 2 0%low visibility 2
192.188.87.0/24 Valid RIR databaseAPNIC 673 100% 68

AS-SET

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

  • ROA: origin1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin203.33.239.0/24ROAs covering it name AS834, not AS154086. If AS154086 should announce it, add a ROA for AS154086.2 of 673
Route object: none203.33.239.0/24Route objects for it name AS834. Add a route object with origin AS154086 in the RIR database for the space.2 of 673

Route objects not announced

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

192.188.86.0/24APNIC, RADBValid

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.