Network · data from 2026-11-12
AS402631 FLIPTHEORY - FlipTheory
Registry name: FLIPTHEORY - FlipTheory, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS402631, 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.174.134.0/24 | Valid | Nonecovered by 206.174.134.0/23 | 669 99% |
| 206.174.135.0/24 | Valid | Nonecovered by 206.174.134.0/23 | 669 99% |
| 206.174.156.0/24 | Valid | Nonecovered by 206.174.156.0/22 | 669 99% |
| 206.174.157.0/24 | Valid | Nonecovered by 206.174.156.0/22 | 669 99% |
| 206.174.158.0/24 | Valid | Nonecovered by 206.174.156.0/22 | 669 99% |
| 206.174.159.0/24 | Valid | Nonecovered by 206.174.156.0/22 | 669 99% |
| 156.9.12.0/24 | Valid | RIR databaseARIN | 669 99% |
| 156.9.13.0/24 | Valid | RIR databaseARIN | 669 99% |
| 156.9.14.0/24 | Valid | RIR databaseARIN | 669 99% |
| 156.9.15.0/24 | Valid | RIR databaseARIN | 669 99% |
| 206.174.152.0/24 | Valid | RIR databaseARIN | 669 99% |
| 206.174.153.0/24 | Valid | RIR databaseARIN | 669 99% |
AS-SET
AS402631 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 10 are in fix.csv.
- Route object: none6
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 206.174.134.0/24 | No route object for it. A route object for 206.174.134.0/23 with origin AS402631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402631 in the RIR database for the space. |
| Route object: none | 206.174.135.0/24 | No route object for it. A route object for 206.174.134.0/23 with origin AS402631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402631 in the RIR database for the space. |
| Route object: none | 206.174.156.0/24 | No route object for it. A route object for 206.174.156.0/22 with origin AS402631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402631 in the RIR database for the space. |
| Route object: none | 206.174.157.0/24 | No route object for it. A route object for 206.174.156.0/22 with origin AS402631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402631 in the RIR database for the space. |
| Route object: none | 206.174.158.0/24 | No route object for it. A route object for 206.174.156.0/22 with origin AS402631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402631 in the RIR database for the space. |
| Route object: none | 206.174.159.0/24 | No route object for it. A route object for 206.174.156.0/22 with origin AS402631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402631 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS402631 whose prefix no peer sees AS402631 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 156.9.12.0/22 | ARIN | Valid |
| 206.174.134.0/23 | ARIN | Valid |
| 206.174.152.0/23 | ARIN, RADB | Valid |
| 206.174.156.0/22 | ARIN | 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.