Network · data from 2026-11-12
AS23437 INFINITY-FL - Infinity Broadband
Registry name: INFINITY-FL - Infinity Broadband, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23437, 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.
| 38.95.21.0/24 | No ROA | None | 670 100% |
| 2607:49c0:40::/43 | No ROA | RIR databaseARIN | 2 0%low visibility |
| 2607:49c0::/42 | Valid | RIR databaseARIN | 605 95% |
AS-SET
AS23437 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 8 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.95.21.0/24 | No ROA covers it. Add a ROA for AS23437, maxLength 24. |
| Route object: none | 38.95.21.0/24 | No route object for it. Add a route object with origin AS23437 in the RIR database for the space. |
| ROA: none | 2607:49c0:40::/43 | No ROA covers it. Add a ROA for AS23437, maxLength 43. |
Route objects not announced
Route objects with origin AS23437 whose prefix no peer sees AS23437 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.153.184.0/24 | ARIN | Valid |
| 64.62.192.0/24 | ARIN | Invalid: origin |
| 184.105.14.0/23 | ARIN | Invalid: origin |
| 2001:470:2f1::/48 | ARIN | Invalid: origin |
| 2001:470:3a5::/48 | ARIN | Invalid: origin |
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.