Network · data from 2026-11-12
AS399864 FLIXOUT - Flixout
Registry name: FLIXOUT - Flixout, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS399864, 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.
| 206.168.56.0/22 | Invalid: origin | RIR databaseARIN | 0 0%low visibility |
| 216.238.56.0/22 | No ROA | Other origin only | 2 0%low visibility |
| 207.167.112.0/22 | No ROA | RIR databaseARIN | 2 0%low visibility |
AS-SET
AS399864 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 5 are in fix.csv.
- ROA: origin1
- ROA: none2
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 206.168.56.0/22 | ROAs covering it name AS6079, not AS399864. If AS399864 should announce it, add a ROA for AS399864. |
| ROA: none | 216.238.56.0/22 | No ROA covers it. Add a ROA for AS399864, maxLength 22. |
| Route object: none | 216.238.56.0/22 | Route objects for it name AS834. Add a route object with origin AS399864 in the RIR database for the space. |
| ROA: none | 207.167.112.0/22 | No ROA covers it. Add a ROA for AS399864, maxLength 22. |
Route objects not announced
Route objects with origin AS399864 whose prefix no peer sees AS399864 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.41.20.0/22 | ARIN | 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.