Network · data from 2026-11-12
AS46555 T2OE-1
Registry name: RSOE-NA - TAKE-TWO INTERACTIVE SOFTWARE, INC., US · PeeringDB
22IPv4 routes
100.0% RPKI valid · 9.1% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
20 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
3Route objects not announced
registered with origin AS46555, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS46555, 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.
| 164.153.136.0/23 | Valid | Nonecovered by 164.153.136.0/22 | 673 100% |
| 164.153.138.0/23 | Valid | Nonecovered by 164.153.136.0/22 | 673 100% |
| 192.81.240.0/22 | Valid | Nonecovered by 192.81.240.0/21 | 673 100% |
| 192.81.240.0/24 | Valid | Nonecovered by 192.81.240.0/21 | 673 100% |
| 192.81.244.0/22 | Valid | Nonecovered by 192.81.240.0/21 | 673 100% |
| 104.255.104.0/24 | Valid | Nonecovered by 104.255.104.0/22 | 672 100% |
| 104.255.107.0/24 | Valid | Nonecovered by 104.255.104.0/22 | 672 100% |
| 164.153.136.0/24 | Valid | Nonecovered by 164.153.136.0/22 | 672 100% |
| 164.153.137.0/24 | Valid | Nonecovered by 164.153.136.0/22 | 672 100% |
| 164.153.138.0/24 | Valid | Nonecovered by 164.153.136.0/22 | 672 100% |
| 164.153.139.0/24 | Valid | Nonecovered by 164.153.136.0/22 | 672 100% |
| 192.81.241.0/24 | Valid | Nonecovered by 192.81.240.0/21 | 672 100% |
| 192.81.242.0/24 | Valid | Nonecovered by 192.81.240.0/21 | 672 100% |
| 192.81.243.0/24 | Valid | Nonecovered by 192.81.240.0/21 | 672 100% |
| 192.81.244.0/24 | Valid | Nonecovered by 192.81.240.0/21 | 672 100% |
| 192.81.245.0/24 | Valid | Nonecovered by 192.81.240.0/21 | 672 100% |
| 192.81.246.0/24 | Valid | Nonecovered by 192.81.240.0/21 | 672 100% |
| 192.81.247.0/24 | Valid | Other origin onlycovered by 192.81.240.0/21 | 672 100% |
| 104.255.105.0/24 | Valid | Nonecovered by 104.255.104.0/22 | 670 100% |
| 104.255.106.0/24 | Valid | Nonecovered by 104.255.104.0/22 | 670 100% |
| 198.133.210.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 104.255.104.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
AS-SET
AS46555's PeeringDB record names no 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 24 are in fix.csv.
- Route object: none20
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 164.153.136.0/23 | No route object for it. A route object for 164.153.136.0/22 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 164.153.138.0/23 | No route object for it. A route object for 164.153.136.0/22 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 192.81.240.0/22 | No route object for it. A route object for 192.81.240.0/21 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 192.81.240.0/24 | No route object for it. A route object for 192.81.240.0/21 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 192.81.244.0/22 | No route object for it. A route object for 192.81.240.0/21 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 104.255.104.0/24 | No route object for it. A route object for 104.255.104.0/22 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 104.255.107.0/24 | No route object for it. A route object for 104.255.104.0/22 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 164.153.136.0/24 | No route object for it. A route object for 164.153.136.0/22 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 164.153.137.0/24 | No route object for it. A route object for 164.153.136.0/22 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 164.153.138.0/24 | No route object for it. A route object for 164.153.136.0/22 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 164.153.139.0/24 | No route object for it. A route object for 164.153.136.0/22 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 192.81.241.0/24 | No route object for it. A route object for 192.81.240.0/21 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 192.81.242.0/24 | No route object for it. A route object for 192.81.240.0/21 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 192.81.243.0/24 | No route object for it. A route object for 192.81.240.0/21 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 192.81.244.0/24 | No route object for it. A route object for 192.81.240.0/21 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 192.81.245.0/24 | No route object for it. A route object for 192.81.240.0/21 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 192.81.246.0/24 | No route object for it. A route object for 192.81.240.0/21 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 192.81.247.0/24 | Route objects for it name AS395856. A route object for 192.81.240.0/21 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 104.255.105.0/24 | No route object for it. A route object for 104.255.104.0/22 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: none | 104.255.106.0/24 | No route object for it. A route object for 104.255.104.0/22 with origin AS46555 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46555 in the RIR database for the space. |
| Route object: RIR | 198.133.210.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS46555 whose prefix no peer sees AS46555 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 164.153.136.0/22 | ARIN | Valid |
| 192.81.240.0/21 | ARIN, RADB | Valid |
| 2620:11b:c000::/44 | 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.