bgpreport

Network · data from 2026-11-12

AS131275 Logon Broadband Pakistan

Registry name: LBPL-AS-AP - Logon Broadband Pvt. Limited, PK · PeeringDB

20IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
0Route objects not announced registered with origin AS131275, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS131275, 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.
103.79.16.0/24 Valid RIR databaseAPNIC 673 100% 66
103.79.18.0/24 Valid RIR databaseAPNIC 673 100% 66
103.121.120.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.121.121.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.203.89.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
111.92.151.0/24 Valid RIR databaseAPNIC 673 100% 67
111.92.152.0/24 Valid RIR databaseAPNIC 673 100% 67
111.92.153.0/24 Valid RIR databaseAPNIC 673 100% 67
111.92.154.0/24 Valid RIR databaseAPNIC 673 100% 67
122.50.1.0/24 Valid RIR databaseAPNIC 673 100% 66
151.123.236.0/24 Valid RIR databaseAPNIC 673 100% 66
151.123.237.0/24 Valid RIR databaseAPNIC 673 100% 66
151.123.238.0/24 Valid RIR databaseAPNIC 673 100% 66
151.123.239.0/24 Valid RIR databaseAPNIC 673 100% 66
151.158.214.0/24 Valid RIR databaseAPNIC 673 100% 66
151.158.215.0/24 Valid RIR databaseAPNIC 673 100% 66
103.203.88.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
223.29.232.0/24 Valid RIR databaseAPNIC 672 100% 67
223.29.233.0/24 Valid RIR databaseAPNIC 672 100% 67
223.29.234.0/24 Valid RIR databaseAPNIC 672 100% 67
2400:9c60::/32 Valid RIR databaseAPNIC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS131275: AS131275:AS-LOGON-BROADBAND. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS131275 isn't in the set, or no route object for AS131275 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS131275 in itNot covered
AS131275:AS-LOGON-BROADBAND In no IRR database read today.

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

  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
AS-SET: not foundAS131275:AS-LOGON-BROADBANDPeeringDB names AS131275:AS-LOGON-BROADBAND; no IRR database read has it.

Route objects not announced

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