Network · data from 2026-11-12
AS6394 DATA-BROADCASTING - Intercontinental Exchange, Inc.
Registry name: DATA-BROADCASTING - Intercontinental Exchange, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS6394, 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.
| 156.48.10.0/24 | No ROA | Other origin only | 672 100% |
| 156.48.11.0/24 | No ROA | Other origin only | 672 100% |
AS-SET
AS6394 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 12 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 156.48.10.0/24 | No ROA covers it. Add a ROA for AS6394, maxLength 24. |
| Route object: none | 156.48.10.0/24 | Route objects for it name AS23763. Add a route object with origin AS6394 in the RIR database for the space. |
| ROA: none | 156.48.11.0/24 | No ROA covers it. Add a ROA for AS6394, maxLength 24. |
| Route object: none | 156.48.11.0/24 | Route objects for it name AS23763. Add a route object with origin AS6394 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS6394 whose prefix no peer sees AS6394 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.101.150.0/23 | RADB | No ROA |
| 198.184.171.0/24 | RADB | No ROA |
| 198.190.10.0/24 | RADB | No ROA |
| 199.217.8.0/22 | RADB | No ROA |
| 199.217.12.0/24 | RADB | No ROA |
| 199.217.14.0/23 | RADB | No ROA |
| 208.240.76.0/23 | RADB | No ROA |
| 216.23.224.0/21 | 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.