Network · data from 2026-11-12
AS45894 FPTONLINE-AS-VN - FPT Online JSC
Registry name: FPTONLINE-AS-VN - FPT Online JSC, VN · not in PeeringDB
30IPv4 routes
100.0% RPKI valid · 100.0% with a route object
4IPv6 routes
100.0% RPKI valid · 25.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
3 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
33Route objects not announced
registered with origin AS45894, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS45894, 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.
| 2402:dd40::/36 | Valid | Nonecovered by 2402:dd40::/32 | 636 100% |
| 2402:dd40:1000::/36 | Valid | Nonecovered by 2402:dd40::/32 | 636 100% |
| 2402:dd40:f000::/36 | Valid | Nonecovered by 2402:dd40::/32 | 636 100% |
| 111.65.241.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.65.242.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.65.243.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.65.245.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.65.248.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.65.250.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.65.252.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 111.65.255.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 180.148.128.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.148.129.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.148.130.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.148.131.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.148.132.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.148.133.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.148.134.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.148.135.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.148.136.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.148.137.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.148.138.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.148.139.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.148.140.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.148.141.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.148.142.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 180.148.143.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 111.65.246.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 111.65.249.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 111.65.251.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 111.65.253.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 2001:df0:66::/48 | Valid | RIR databaseAPNIC, RADB | 636 100% |
| 111.65.244.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 2 0%low visibility |
| 111.65.247.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 1 0%low visibility |
AS-SET
AS45894 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 36 are in fix.csv.
- Route object: none3
- Route object: not announced33
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2402:dd40::/36 | No route object for it. A route object for 2402:dd40::/32 with origin AS45894 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45894 in the RIR database for the space. |
| Route object: none | 2402:dd40:1000::/36 | No route object for it. A route object for 2402:dd40::/32 with origin AS45894 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45894 in the RIR database for the space. |
| Route object: none | 2402:dd40:f000::/36 | No route object for it. A route object for 2402:dd40::/32 with origin AS45894 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45894 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS45894 whose prefix no peer sees AS45894 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 111.65.240.0/20 | APNIC, NTTCOM, RADB | Valid |
| 111.65.240.0/21 | APNIC | Valid |
| 111.65.240.0/22 | APNIC | Valid |
| 111.65.240.0/23 | APNIC | Valid |
| 111.65.240.0/24 | APNIC, NTTCOM, RADB | Valid |
| 111.65.242.0/23 | APNIC | Valid |
| 111.65.244.0/22 | APNIC | Valid |
| 111.65.244.0/23 | APNIC | Valid |
| 111.65.246.0/23 | APNIC | Valid |
| 111.65.248.0/21 | APNIC | Valid |
| 111.65.248.0/22 | APNIC | Valid |
| 111.65.248.0/23 | APNIC | Valid |
| 111.65.250.0/23 | APNIC | Valid |
| 111.65.252.0/22 | APNIC | Valid |
| 111.65.252.0/23 | APNIC | Valid |
| 111.65.254.0/23 | APNIC | Valid |
| 111.65.254.0/24 | APNIC, NTTCOM, RADB | Valid |
| 180.148.128.0/20 | APNIC, RADB | Valid |
| 180.148.128.0/21 | APNIC, RADB | Valid |
| 180.148.128.0/22 | APNIC, RADB | Valid |
| 180.148.128.0/23 | APNIC, RADB | Valid |
| 180.148.130.0/23 | APNIC, RADB | Valid |
| 180.148.132.0/22 | APNIC, RADB | Valid |
| 180.148.132.0/23 | APNIC, RADB | Valid |
| 180.148.134.0/23 | APNIC, RADB | Valid |
| 180.148.136.0/21 | APNIC, RADB | Valid |
| 180.148.136.0/22 | APNIC, RADB | Valid |
| 180.148.136.0/23 | APNIC, RADB | Valid |
| 180.148.138.0/23 | APNIC, RADB | Valid |
| 180.148.140.0/22 | APNIC, RADB | Valid |
| 180.148.140.0/23 | APNIC, RADB | Valid |
| 180.148.142.0/23 | APNIC, RADB | Valid |
| 2402:dd40::/32 | APNIC | 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.