Network · data from 2026-11-12
AS19263 CBAD-NET - Cincinnati Bell Any Distance, Inc.
Registry name: CBAD-NET - Cincinnati Bell Any Distance, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS19263, 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.
| 74.83.178.0/24 | Invalid: origin | None | 28 4%low visibility |
| 216.68.22.0/24 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS19263 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 3 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 74.83.178.0/24 | ROAs covering it name AS6181, not AS19263. If AS19263 should announce it, add a ROA for AS19263. |
| Route object: none | 74.83.178.0/24 | No route object for it. Add a route object with origin AS19263 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS19263 whose prefix no peer sees AS19263 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.250.88.0/22 | ALTDB | 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.