Network · data from 2026-11-12
AS777 UNSPECIFIED
Registry name: UNSPECIFIED - IDDQD-AS, EU · PeeringDB
17IPv4 routes
0.0% RPKI valid · 58.8% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
17No ROA
7 with no route object for this origin
7Low visibility
seen by under 10% of full-table peers
1Route objects not announced
registered with origin AS777, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS777, 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.
| 132.166.0.0/16 | No ROA | Nonecovered by 132.166.0.0/15 | 1 0%low visibility |
| 132.167.0.0/16 | No ROA | Nonecovered by 132.166.0.0/15 | 1 0%low visibility |
| 132.167.130.0/24 | No ROA | Nonecovered by 132.166.0.0/15 | 1 0%low visibility |
| 132.167.131.0/24 | No ROA | Nonecovered by 132.166.0.0/15 | 1 0%low visibility |
| 132.167.132.0/24 | No ROA | Nonecovered by 132.166.0.0/15 | 1 0%low visibility |
| 132.168.0.0/16 | No ROA | Nonecovered by 132.168.0.0/15 | 1 0%low visibility |
| 132.169.0.0/16 | No ROA | Nonecovered by 132.168.0.0/15 | 1 0%low visibility |
| 132.165.0.0/16 | No ROA | RIR databaseRIPE | 672 100% |
| 192.33.158.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.54.143.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.54.205.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.54.206.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.54.207.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.54.208.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.54.209.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 192.93.124.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 132.168.0.0/15 | No ROA | RIR databaseRIPE | 657 98% |
AS-SET
AS777'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 25 are in fix.csv.
- ROA: none17
- Route object: none7
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 132.166.0.0/16 | No ROA covers it. Add a ROA for AS777, maxLength 16. |
| Route object: none | 132.166.0.0/16 | No route object for it. A route object for 132.166.0.0/15 with origin AS777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS777 in the RIR database for the space. |
| ROA: none | 132.167.0.0/16 | No ROA covers it. Add a ROA for AS777, maxLength 16. |
| Route object: none | 132.167.0.0/16 | No route object for it. A route object for 132.166.0.0/15 with origin AS777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS777 in the RIR database for the space. |
| ROA: none | 132.167.130.0/24 | No ROA covers it. Add a ROA for AS777, maxLength 24. |
| Route object: none | 132.167.130.0/24 | No route object for it. A route object for 132.166.0.0/15 with origin AS777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS777 in the RIR database for the space. |
| ROA: none | 132.167.131.0/24 | No ROA covers it. Add a ROA for AS777, maxLength 24. |
| Route object: none | 132.167.131.0/24 | No route object for it. A route object for 132.166.0.0/15 with origin AS777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS777 in the RIR database for the space. |
| ROA: none | 132.167.132.0/24 | No ROA covers it. Add a ROA for AS777, maxLength 24. |
| Route object: none | 132.167.132.0/24 | No route object for it. A route object for 132.166.0.0/15 with origin AS777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS777 in the RIR database for the space. |
| ROA: none | 132.168.0.0/16 | No ROA covers it. Add a ROA for AS777, maxLength 16. |
| Route object: none | 132.168.0.0/16 | No route object for it. A route object for 132.168.0.0/15 with origin AS777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS777 in the RIR database for the space. |
| ROA: none | 132.169.0.0/16 | No ROA covers it. Add a ROA for AS777, maxLength 16. |
| Route object: none | 132.169.0.0/16 | No route object for it. A route object for 132.168.0.0/15 with origin AS777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS777 in the RIR database for the space. |
| ROA: none | 132.165.0.0/16 | No ROA covers it. Add a ROA for AS777, maxLength 16. |
| ROA: none | 192.33.158.0/24 | No ROA covers it. Add a ROA for AS777, maxLength 24. |
| ROA: none | 192.54.143.0/24 | No ROA covers it. Add a ROA for AS777, maxLength 24. |
| ROA: none | 192.54.205.0/24 | No ROA covers it. Add a ROA for AS777, maxLength 24. |
| ROA: none | 192.54.206.0/24 | No ROA covers it. Add a ROA for AS777, maxLength 24. |
| ROA: none | 192.54.207.0/24 | No ROA covers it. Add a ROA for AS777, maxLength 24. |
| ROA: none | 192.54.208.0/24 | No ROA covers it. Add a ROA for AS777, maxLength 24. |
| ROA: none | 192.54.209.0/24 | No ROA covers it. Add a ROA for AS777, maxLength 24. |
| ROA: none | 192.93.124.0/24 | No ROA covers it. Add a ROA for AS777, maxLength 24. |
| ROA: none | 132.168.0.0/15 | No ROA covers it. Add a ROA for AS777, maxLength 15. |
Route objects not announced
Route objects with origin AS777 whose prefix no peer sees AS777 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 132.166.0.0/15 | RIPE | No ROA |
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.