Network · data from 2026-11-12
AS142192 RRRL NET AS142192
Registry name: RRRLNET-AS-AP - RRRL NET, BD · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS142192, 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.165.158.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 103.165.161.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 45.119.121.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 192.232.62.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 192.232.63.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.94.165.0/24 | Valid | RIR databaseAPNIC | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS142192: AS-142192-RRRLNET-BD. 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 (AS142192 isn't in the set, or no route object for AS142192 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 | AS142192 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-142192-RRRLNET-BD | 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 11 are in fix.csv.
- ROA: origin3
- Route object: none3
- AS-SET: not found1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.165.158.0/24 | ROAs covering it name AS142045, not AS142192. If AS142192 should announce it, add a ROA for AS142192. |
| Route object: none | 103.165.158.0/24 | Route objects for it name AS142045. Add a route object with origin AS142192 in the RIR database for the space. |
| ROA: origin | 103.165.161.0/24 | ROAs covering it name AS142044, not AS142192. If AS142192 should announce it, add a ROA for AS142192. |
| Route object: none | 103.165.161.0/24 | Route objects for it name AS142044. Add a route object with origin AS142192 in the RIR database for the space. |
| ROA: origin | 45.119.121.0/24 | ROAs covering it name AS137579, not AS142192. If AS142192 should announce it, add a ROA for AS142192. |
| Route object: none | 45.119.121.0/24 | Route objects for it name AS137579. Add a route object with origin AS142192 in the RIR database for the space. |
| AS-SET: not found | AS-142192-RRRLNET-BD | PeeringDB names AS-142192-RRRLNET-BD; no IRR database read has it. |
Route objects not announced
Route objects with origin AS142192 whose prefix no peer sees AS142192 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.232.62.0/23 | APNIC | Valid |
| 2001:df6:6d80::/48 | APNIC | Valid |
| 2001:df6:8f40::/48 | APNIC | Valid |
| 2407:4ac0::/32 | APNIC | 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.