Network · data from 2026-11-12
AS398947 CABLE COLOR (AS398947)
Registry name: CABLECOLOR-MIA-01 - CABLE COLOR LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS398947, 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.252.192.0/22 | Valid | Other IRR onlyRADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS398947: RADB::AS398947:AS-CUSTOMERS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS398947 isn't in the set, or no route object for AS398947 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS398947 in it | Not covered |
|---|---|---|---|---|---|
| RADB::AS398947:AS-CUSTOMERS | RADB | 65 | 6 | Yes | 0 |
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 4 are in fix.csv.
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 38.252.192.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS398947 whose prefix no peer sees AS398947 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.252.188.0/24 | RADB | No ROA |
| 190.92.53.0/24 | LACNIC | Valid |
| 2800:b10:200::/48 | LACNIC | Valid |
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.