Network · data from 2026-11-12
AS141372 Logitech Cable
Registry name: LOGITECH-AS-AP - Logitech Cable (Private) Limited, PK · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS141372, 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.
| 111.92.158.0/24 | Invalid: origin | Other origin only | 134 20% |
| 103.157.201.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 111.92.159.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.157.200.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
AS-SET
PeeringDB's irr_as_set for AS141372: AS141372:AS-PEERS. 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 (AS141372 isn't in the set, or no route object for AS141372 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.
| Name | Database | ASNs | Sets | AS141372 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS141372:AS-PEERS | 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 5 are in fix.csv.
- ROA: origin1
- Route object: none1
- AS-SET: not found1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 111.92.158.0/24 | ROAs covering it name AS45814, not AS141372. If AS141372 should announce it, add a ROA for AS141372. |
| Route object: none | 111.92.158.0/24 | Route objects for it name AS45814. Add a route object with origin AS141372 in the RIR database for the space. |
| AS-SET: not found | AS141372:AS-PEERS | PeeringDB names AS141372:AS-PEERS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS141372 whose prefix no peer sees AS141372 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.157.200.0/23 | APNIC | Valid |
| 154.208.56.0/24 | RADB | Valid |
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.