Network · data from 2026-11-12
AS16437 INFINITY-BROADBAND-LTD - Infinity Broadband Ltd
Registry name: INFINITY-BROADBAND-LTD - Infinity Broadband Ltd, KY · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16437, 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.
| 2606:f580::/32 | No ROA | Other IRR onlyRADB | 605 95% |
| 162.247.222.0/23 | Valid | Nonecovered by 162.247.220.0/22 | 673 100% |
| 156.236.83.0/24 | Valid | Nonecovered by 156.236.80.0/22 | 672 100% |
| 156.236.82.0/24 | Valid | Nonecovered by 156.236.80.0/22 | 2 0%low visibility |
| 23.188.0.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 161.199.132.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 162.247.220.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 192.160.250.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 208.88.244.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 154.81.208.0/21 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 154.81.212.0/22 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 154.81.216.0/22 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 156.236.80.0/22 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 154.81.208.0/22 | Valid | RIR databaseAFRINIC, RADB | 2 0%low visibility |
AS-SET
AS16437 isn't in PeeringDB, where networks name their 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 13 are in fix.csv.
- ROA: none1
- Route object: none3
- Route object: RIR5
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2606:f580::/32 | No ROA covers it. Add a ROA for AS16437, maxLength 32. |
| Route object: RIR | 2606:f580::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 162.247.222.0/23 | No route object for it. A route object for 162.247.220.0/22 with origin AS16437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16437 in the RIR database for the space. |
| Route object: none | 156.236.83.0/24 | No route object for it. A route object for 156.236.80.0/22 with origin AS16437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16437 in the RIR database for the space. |
| Route object: none | 156.236.82.0/24 | No route object for it. A route object for 156.236.80.0/22 with origin AS16437 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16437 in the RIR database for the space. |
| Route object: RIR | 23.188.0.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 161.199.132.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 162.247.220.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.160.250.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS16437 whose prefix no peer sees AS16437 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 12.191.52.0/24 | RADB | No ROA |
| 23.188.0.0/23 | RADB | No ROA |
| 159.29.224.0/20 | RADB | No ROA |
| 162.247.220.0/22 | 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.