Network · data from 2026-11-12
AS198983 TornadoDatacenter
Registry name: TornadoDatacenter Joseph Hofmann trading as 'Tornado Datacenter GmbH & Co. KG', DE · PeeringDB
18IPv4 routes
100.0% RPKI valid · 27.8% with a route object
2IPv6 routes
100.0% RPKI valid · 50.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
14 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
3Route objects not announced
registered with origin AS198983, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS198983, 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.
| 104.194.140.0/24 | Valid | Nonecovered by 104.194.140.0/22 | 673 100% |
| 104.194.141.0/24 | Valid | Nonecovered by 104.194.140.0/22 | 673 100% |
| 104.194.142.0/24 | Valid | Nonecovered by 104.194.140.0/22 | 673 100% |
| 104.194.143.0/24 | Valid | Nonecovered by 104.194.140.0/22 | 673 100% |
| 104.194.144.0/24 | Valid | Nonecovered by 104.194.144.0/21 | 673 100% |
| 104.194.145.0/24 | Valid | Nonecovered by 104.194.144.0/21 | 673 100% |
| 104.194.146.0/24 | Valid | Nonecovered by 104.194.144.0/21 | 673 100% |
| 104.194.147.0/24 | Valid | Nonecovered by 104.194.144.0/21 | 673 100% |
| 104.194.148.0/24 | Valid | Nonecovered by 104.194.144.0/21 | 673 100% |
| 104.194.149.0/24 | Valid | Nonecovered by 104.194.144.0/21 | 673 100% |
| 104.194.150.0/24 | Valid | Nonecovered by 104.194.144.0/21 | 673 100% |
| 104.194.151.0/24 | Valid | Nonecovered by 104.194.144.0/21 | 673 100% |
| 172.86.124.0/24 | Valid | Other origin only | 673 100% |
| 2602:fa59:1::/48 | Valid | None | 636 100% |
| 45.61.152.0/22 | Valid | RIR databaseARIN | 673 100% |
| 104.194.128.0/22 | Valid | RIR databaseARIN | 673 100% |
| 153.75.88.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 160.20.145.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 167.88.162.0/24 | Valid | RIR databaseARIN | 673 100% |
| 2a0e:b540:ffa1::/48 | Valid | RIR databaseRIPE | 630 99% |
AS-SET
AS198983'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 17 are in fix.csv.
- Route object: none14
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 104.194.140.0/24 | No route object for it. A route object for 104.194.140.0/22 with origin AS198983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198983 in the RIR database for the space. |
| Route object: none | 104.194.141.0/24 | No route object for it. A route object for 104.194.140.0/22 with origin AS198983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198983 in the RIR database for the space. |
| Route object: none | 104.194.142.0/24 | No route object for it. A route object for 104.194.140.0/22 with origin AS198983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198983 in the RIR database for the space. |
| Route object: none | 104.194.143.0/24 | No route object for it. A route object for 104.194.140.0/22 with origin AS198983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198983 in the RIR database for the space. |
| Route object: none | 104.194.144.0/24 | No route object for it. A route object for 104.194.144.0/21 with origin AS198983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198983 in the RIR database for the space. |
| Route object: none | 104.194.145.0/24 | No route object for it. A route object for 104.194.144.0/21 with origin AS198983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198983 in the RIR database for the space. |
| Route object: none | 104.194.146.0/24 | No route object for it. A route object for 104.194.144.0/21 with origin AS198983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198983 in the RIR database for the space. |
| Route object: none | 104.194.147.0/24 | No route object for it. A route object for 104.194.144.0/21 with origin AS198983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198983 in the RIR database for the space. |
| Route object: none | 104.194.148.0/24 | No route object for it. A route object for 104.194.144.0/21 with origin AS198983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198983 in the RIR database for the space. |
| Route object: none | 104.194.149.0/24 | No route object for it. A route object for 104.194.144.0/21 with origin AS198983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198983 in the RIR database for the space. |
| Route object: none | 104.194.150.0/24 | No route object for it. A route object for 104.194.144.0/21 with origin AS198983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198983 in the RIR database for the space. |
| Route object: none | 104.194.151.0/24 | No route object for it. A route object for 104.194.144.0/21 with origin AS198983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198983 in the RIR database for the space. |
| Route object: none | 172.86.124.0/24 | Route objects for it name AS14956. Add a route object with origin AS198983 in the RIR database for the space. |
| Route object: none | 2602:fa59:1::/48 | No route object for it. Add a route object with origin AS198983 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS198983 whose prefix no peer sees AS198983 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 104.194.140.0/22 | ARIN | Valid |
| 104.194.144.0/21 | ARIN | Valid |
| 144.172.77.0/24 | ARIN | Invalid: origin |
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.