Network · data from 2026-11-12
AS25607 IBW Communications
Registry name: AS25607 - IBW Communications, NI · PeeringDB
24IPv4 routes
100.0% RPKI valid · 29.2% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
17 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
6Route objects not announced
registered with origin AS25607, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS25607, 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.
| 161.0.32.0/22 | Valid | Nonecovered by 161.0.32.0/19 | 671 100% |
| 161.0.36.0/22 | Valid | Nonecovered by 161.0.32.0/19 | 671 100% |
| 161.0.48.0/22 | Valid | Nonecovered by 161.0.32.0/19 | 671 100% |
| 161.0.52.0/23 | Valid | Nonecovered by 161.0.32.0/19 | 671 100% |
| 161.0.55.0/24 | Valid | Nonecovered by 161.0.32.0/19 | 671 100% |
| 161.0.56.0/23 | Valid | Nonecovered by 161.0.32.0/19 | 671 100% |
| 191.103.118.0/23 | Valid | Nonecovered by 191.103.112.0/20 | 671 100% |
| 191.103.122.0/23 | Valid | Nonecovered by 191.103.112.0/20 | 671 100% |
| 190.106.52.0/22 | Valid | Nonecovered by 190.106.48.0/20 | 670 100% |
| 190.106.58.0/23 | Valid | Nonecovered by 190.106.56.0/21 | 670 100% |
| 190.106.60.0/24 | Valid | Nonecovered by 190.106.56.0/21 | 670 100% |
| 200.85.162.0/23 | Valid | Nonecovered by 200.85.160.0/20 | 670 100% |
| 200.85.168.0/22 | Valid | Nonecovered by 200.85.160.0/20 | 670 100% |
| 200.85.172.0/22 | Valid | Nonecovered by 200.85.160.0/20 | 670 100% |
| 191.103.116.0/24 | Valid | Nonecovered by 191.103.112.0/20 | 661 98% |
| 165.98.130.0/24 | Valid | None | 653 97% |
| 165.98.100.0/24 | Valid | Other origin only | 44 7%low visibility |
| 165.98.224.0/24 | Valid | Other IRR onlyRADB | 660 98% |
| 165.98.247.0/24 | Valid | Other IRR onlyRADB | 660 98% |
| 165.98.228.0/24 | Valid | Other IRR onlyRADB | 654 97% |
| 161.0.32.0/19 | Valid | RIR databaseLACNIC, RADB | 662 98% |
| 191.103.112.0/20 | Valid | RIR databaseLACNIC, RADB | 662 98% |
| 190.106.48.0/20 | Valid | RIR databaseLACNIC, RADB | 661 98% |
| 200.85.160.0/20 | Valid | RIR databaseLACNIC | 661 98% |
| 2803:800::/32 | Valid | RIR databaseLACNIC, RADB | 631 99% |
AS-SET
AS25607'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 26 are in fix.csv.
- Route object: none17
- Route object: RIR3
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 161.0.32.0/22 | No route object for it. A route object for 161.0.32.0/19 with origin AS25607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: none | 161.0.36.0/22 | No route object for it. A route object for 161.0.32.0/19 with origin AS25607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: none | 161.0.48.0/22 | No route object for it. A route object for 161.0.32.0/19 with origin AS25607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: none | 161.0.52.0/23 | No route object for it. A route object for 161.0.32.0/19 with origin AS25607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: none | 161.0.55.0/24 | No route object for it. A route object for 161.0.32.0/19 with origin AS25607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: none | 161.0.56.0/23 | No route object for it. A route object for 161.0.32.0/19 with origin AS25607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: none | 191.103.118.0/23 | No route object for it. A route object for 191.103.112.0/20 with origin AS25607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: none | 191.103.122.0/23 | No route object for it. A route object for 191.103.112.0/20 with origin AS25607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: none | 190.106.52.0/22 | No route object for it. A route object for 190.106.48.0/20 with origin AS25607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: none | 190.106.58.0/23 | No route object for it. A route object for 190.106.56.0/21 with origin AS25607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: none | 190.106.60.0/24 | No route object for it. A route object for 190.106.56.0/21 with origin AS25607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: none | 200.85.162.0/23 | No route object for it. A route object for 200.85.160.0/20 with origin AS25607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: none | 200.85.168.0/22 | No route object for it. A route object for 200.85.160.0/20 with origin AS25607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: none | 200.85.172.0/22 | No route object for it. A route object for 200.85.160.0/20 with origin AS25607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: none | 191.103.116.0/24 | No route object for it. A route object for 191.103.112.0/20 with origin AS25607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: none | 165.98.130.0/24 | No route object for it. Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: none | 165.98.100.0/24 | Route objects for it name AS267797. Add a route object with origin AS25607 in the RIR database for the space. |
| Route object: RIR | 165.98.224.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 165.98.247.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 165.98.228.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS25607 whose prefix no peer sees AS25607 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 165.98.52.0/22 | RADB | No ROA |
| 165.98.68.0/22 | RADB | No ROA |
| 165.98.72.0/22 | RADB | No ROA |
| 165.98.140.0/22 | RADB | No ROA |
| 190.106.56.0/21 | RADB | Valid |
| 192.136.46.0/24 | RADB | 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.