Network · data from 2026-11-12
AS201000 JS Whizzy Internet
Registry name: WHIZZY-FTTX Js Whizzy Internet Limited, IE · PeeringDB
39IPv4 routes
100.0% RPKI valid · 12.8% with a route object
6IPv6 routes
100.0% RPKI valid · 33.3% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
38 with no route object for this origin
7Low visibility
seen by under 10% of full-table peers
5Route objects not announced
registered with origin AS201000, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS201000, 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.
| 79.143.192.0/20 | Valid | None | 673 100% |
| 79.143.193.0/24 | Valid | Nonecovered by 79.143.192.0/22 | 673 100% |
| 79.143.194.0/24 | Valid | Nonecovered by 79.143.192.0/22 | 673 100% |
| 79.143.197.0/24 | Valid | Nonecovered by 79.143.196.0/22 | 673 100% |
| 79.143.198.0/24 | Valid | Nonecovered by 79.143.196.0/22 | 673 100% |
| 79.143.200.0/24 | Valid | Nonecovered by 79.143.200.0/22 | 673 100% |
| 79.143.201.0/24 | Valid | Nonecovered by 79.143.200.0/22 | 673 100% |
| 79.143.202.0/24 | Valid | Nonecovered by 79.143.200.0/22 | 673 100% |
| 79.143.203.0/24 | Valid | Nonecovered by 79.143.200.0/22 | 673 100% |
| 79.143.204.0/24 | Valid | Nonecovered by 79.143.204.0/22 | 673 100% |
| 79.143.205.0/24 | Valid | Nonecovered by 79.143.204.0/22 | 673 100% |
| 79.143.206.0/24 | Valid | Nonecovered by 79.143.204.0/22 | 673 100% |
| 91.245.244.0/24 | Valid | Nonecovered by 91.245.244.0/22 | 673 100% |
| 91.245.245.0/24 | Valid | Nonecovered by 91.245.244.0/22 | 673 100% |
| 91.245.246.0/23 | Valid | Nonecovered by 91.245.244.0/22 | 673 100% |
| 185.89.73.0/24 | Valid | Nonecovered by 185.89.72.0/22 | 673 100% |
| 185.89.75.0/24 | Valid | Nonecovered by 185.89.72.0/22 | 673 100% |
| 185.211.252.0/23 | Valid | Nonecovered by 185.211.252.0/22 | 673 100% |
| 185.211.254.0/24 | Valid | Nonecovered by 185.211.252.0/22 | 673 100% |
| 185.211.255.0/24 | Valid | Nonecovered by 185.211.252.0/22 | 673 100% |
| 185.237.148.0/24 | Valid | Nonecovered by 185.237.148.0/22 | 673 100% |
| 185.237.149.0/24 | Valid | Nonecovered by 185.237.148.0/22 | 673 100% |
| 185.237.150.0/24 | Valid | Nonecovered by 185.237.148.0/22 | 673 100% |
| 185.237.151.0/24 | Valid | Nonecovered by 185.237.148.0/22 | 673 100% |
| 45.156.120.0/24 | Valid | Nonecovered by 45.156.120.0/22 | 672 100% |
| 45.156.121.0/24 | Valid | Nonecovered by 45.156.120.0/22 | 672 100% |
| 45.156.122.0/24 | Valid | Nonecovered by 45.156.120.0/22 | 672 100% |
| 45.156.123.0/24 | Valid | Nonecovered by 45.156.120.0/22 | 672 100% |
| 2a03:8260:804a::/48 | Valid | Nonecovered by 2a03:8260::/32 | 635 100% |
| 2a03:8260:804b::/48 | Valid | Nonecovered by 2a03:8260::/32 | 635 100% |
| 2a03:8260:804f::/48 | Valid | Nonecovered by 2a03:8260::/32 | 635 100% |
| 2a03:8260:807d::/48 | Valid | Nonecovered by 2a03:8260::/32 | 635 100% |
| 79.143.192.0/24 | Valid | Nonecovered by 79.143.192.0/22 | 2 0%low visibility |
| 79.143.195.0/24 | Valid | Nonecovered by 79.143.192.0/22 | 2 0%low visibility |
| 79.143.196.0/24 | Valid | Nonecovered by 79.143.196.0/22 | 2 0%low visibility |
| 79.143.199.0/24 | Valid | Nonecovered by 79.143.196.0/22 | 2 0%low visibility |
| 79.143.207.0/24 | Valid | Nonecovered by 79.143.204.0/22 | 2 0%low visibility |
| 185.89.72.0/24 | Valid | Nonecovered by 185.89.72.0/22 | 2 0%low visibility |
| 45.156.120.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 91.245.244.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.89.72.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.237.148.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 2a03:8260::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a03:8260:807b::/48 | Valid | RIR databaseRIPE | 635 100% |
| 185.211.252.0/22 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS201000'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 43 are in fix.csv.
- Route object: none38
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 79.143.192.0/20 | No route object for it. Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 79.143.193.0/24 | No route object for it. A route object for 79.143.192.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 79.143.194.0/24 | No route object for it. A route object for 79.143.192.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 79.143.197.0/24 | No route object for it. A route object for 79.143.196.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 79.143.198.0/24 | No route object for it. A route object for 79.143.196.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 79.143.200.0/24 | No route object for it. A route object for 79.143.200.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 79.143.201.0/24 | No route object for it. A route object for 79.143.200.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 79.143.202.0/24 | No route object for it. A route object for 79.143.200.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 79.143.203.0/24 | No route object for it. A route object for 79.143.200.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 79.143.204.0/24 | No route object for it. A route object for 79.143.204.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 79.143.205.0/24 | No route object for it. A route object for 79.143.204.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 79.143.206.0/24 | No route object for it. A route object for 79.143.204.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 91.245.244.0/24 | No route object for it. A route object for 91.245.244.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 91.245.245.0/24 | No route object for it. A route object for 91.245.244.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 91.245.246.0/23 | No route object for it. A route object for 91.245.244.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 185.89.73.0/24 | No route object for it. A route object for 185.89.72.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 185.89.75.0/24 | No route object for it. A route object for 185.89.72.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 185.211.252.0/23 | No route object for it. A route object for 185.211.252.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 185.211.254.0/24 | No route object for it. A route object for 185.211.252.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 185.211.255.0/24 | No route object for it. A route object for 185.211.252.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 185.237.148.0/24 | No route object for it. A route object for 185.237.148.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 185.237.149.0/24 | No route object for it. A route object for 185.237.148.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 185.237.150.0/24 | No route object for it. A route object for 185.237.148.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 185.237.151.0/24 | No route object for it. A route object for 185.237.148.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 45.156.120.0/24 | No route object for it. A route object for 45.156.120.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 45.156.121.0/24 | No route object for it. A route object for 45.156.120.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 45.156.122.0/24 | No route object for it. A route object for 45.156.120.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 45.156.123.0/24 | No route object for it. A route object for 45.156.120.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 2a03:8260:804a::/48 | No route object for it. A route object for 2a03:8260::/32 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 2a03:8260:804b::/48 | No route object for it. A route object for 2a03:8260::/32 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 2a03:8260:804f::/48 | No route object for it. A route object for 2a03:8260::/32 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 2a03:8260:807d::/48 | No route object for it. A route object for 2a03:8260::/32 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 79.143.192.0/24 | No route object for it. A route object for 79.143.192.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 79.143.195.0/24 | No route object for it. A route object for 79.143.192.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 79.143.196.0/24 | No route object for it. A route object for 79.143.196.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 79.143.199.0/24 | No route object for it. A route object for 79.143.196.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 79.143.207.0/24 | No route object for it. A route object for 79.143.204.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
| Route object: none | 185.89.72.0/24 | No route object for it. A route object for 185.89.72.0/22 with origin AS201000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201000 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS201000 whose prefix no peer sees AS201000 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 79.143.192.0/22 | RIPE | Valid |
| 79.143.196.0/22 | RIPE | Valid |
| 79.143.200.0/22 | RIPE | Valid |
| 79.143.204.0/22 | RIPE | Valid |
| 2a03:8260:807a::/48 | RIPE | 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.