Network · data from 2026-11-12
AS46974 SERVAXNET - ServaxNet, LLC
Registry name: SERVAXNET - ServaxNet, LLC, US · not in PeeringDB
19IPv4 routes
63.2% RPKI valid · 0.0% with a route object
2IPv6 routes
0.0% RPKI valid · 0.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
9No ROA
21 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
4Route objects not announced
registered with origin AS46974, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS46974, 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.
| 162.255.224.0/23 | No ROA | Nonecovered by 162.255.224.0/22 | 673 100% |
| 162.255.225.0/24 | No ROA | Nonecovered by 162.255.224.0/22 | 673 100% |
| 162.255.226.0/24 | No ROA | Nonecovered by 162.255.224.0/22 | 673 100% |
| 162.255.227.0/24 | No ROA | Nonecovered by 162.255.224.0/22 | 673 100% |
| 72.4.88.0/24 | No ROA | Nonecovered by 72.4.88.0/21 | 672 100% |
| 72.4.90.0/24 | No ROA | Nonecovered by 72.4.88.0/21 | 672 100% |
| 72.4.91.0/24 | No ROA | Nonecovered by 72.4.88.0/21 | 672 100% |
| 2602:ff1a::/36 | No ROA | None | 605 95% |
| 2602:ff1a:501::/48 | No ROA | None | 605 95% |
| 204.141.164.0/24 | Valid | None | 673 100% |
| 204.141.165.0/24 | Valid | None | 673 100% |
| 204.141.166.0/24 | Valid | None | 673 100% |
| 204.141.167.0/24 | Valid | None | 673 100% |
| 204.141.168.0/24 | Valid | Nonecovered by 204.141.168.0/22 | 673 100% |
| 204.141.169.0/24 | Valid | Nonecovered by 204.141.168.0/22 | 673 100% |
| 204.141.170.0/24 | Valid | Nonecovered by 204.141.168.0/22 | 673 100% |
| 204.141.171.0/24 | Valid | Nonecovered by 204.141.168.0/22 | 673 100% |
| 204.141.180.0/24 | Valid | None | 673 100% |
| 204.141.181.0/24 | Valid | None | 673 100% |
| 204.141.182.0/24 | Valid | None | 673 100% |
| 204.141.183.0/24 | Valid | None | 673 100% |
AS-SET
AS46974 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 34 are in fix.csv.
- ROA: none9
- Route object: none21
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 162.255.224.0/23 | No ROA covers it. Add a ROA for AS46974, maxLength 23. |
| Route object: none | 162.255.224.0/23 | No route object for it. A route object for 162.255.224.0/22 with origin AS46974 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46974 in the RIR database for the space. |
| ROA: none | 162.255.225.0/24 | No ROA covers it. Add a ROA for AS46974, maxLength 24. |
| Route object: none | 162.255.225.0/24 | No route object for it. A route object for 162.255.224.0/22 with origin AS46974 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46974 in the RIR database for the space. |
| ROA: none | 162.255.226.0/24 | No ROA covers it. Add a ROA for AS46974, maxLength 24. |
| Route object: none | 162.255.226.0/24 | No route object for it. A route object for 162.255.224.0/22 with origin AS46974 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46974 in the RIR database for the space. |
| ROA: none | 162.255.227.0/24 | No ROA covers it. Add a ROA for AS46974, maxLength 24. |
| Route object: none | 162.255.227.0/24 | No route object for it. A route object for 162.255.224.0/22 with origin AS46974 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46974 in the RIR database for the space. |
| ROA: none | 72.4.88.0/24 | No ROA covers it. Add a ROA for AS46974, maxLength 24. |
| Route object: none | 72.4.88.0/24 | No route object for it. A route object for 72.4.88.0/21 with origin AS46974 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46974 in the RIR database for the space. |
| ROA: none | 72.4.90.0/24 | No ROA covers it. Add a ROA for AS46974, maxLength 24. |
| Route object: none | 72.4.90.0/24 | No route object for it. A route object for 72.4.88.0/21 with origin AS46974 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46974 in the RIR database for the space. |
| ROA: none | 72.4.91.0/24 | No ROA covers it. Add a ROA for AS46974, maxLength 24. |
| Route object: none | 72.4.91.0/24 | No route object for it. A route object for 72.4.88.0/21 with origin AS46974 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46974 in the RIR database for the space. |
| ROA: none | 2602:ff1a::/36 | No ROA covers it. Add a ROA for AS46974, maxLength 36. |
| Route object: none | 2602:ff1a::/36 | No route object for it. Add a route object with origin AS46974 in the RIR database for the space. |
| ROA: none | 2602:ff1a:501::/48 | No ROA covers it. Add a ROA for AS46974, maxLength 48. |
| Route object: none | 2602:ff1a:501::/48 | No route object for it. Add a route object with origin AS46974 in the RIR database for the space. |
| Route object: none | 204.141.164.0/24 | No route object for it. Add a route object with origin AS46974 in the RIR database for the space. |
| Route object: none | 204.141.165.0/24 | No route object for it. Add a route object with origin AS46974 in the RIR database for the space. |
| Route object: none | 204.141.166.0/24 | No route object for it. Add a route object with origin AS46974 in the RIR database for the space. |
| Route object: none | 204.141.167.0/24 | No route object for it. Add a route object with origin AS46974 in the RIR database for the space. |
| Route object: none | 204.141.168.0/24 | No route object for it. A route object for 204.141.168.0/22 with origin AS46974 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46974 in the RIR database for the space. |
| Route object: none | 204.141.169.0/24 | No route object for it. A route object for 204.141.168.0/22 with origin AS46974 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46974 in the RIR database for the space. |
| Route object: none | 204.141.170.0/24 | No route object for it. A route object for 204.141.168.0/22 with origin AS46974 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46974 in the RIR database for the space. |
| Route object: none | 204.141.171.0/24 | No route object for it. A route object for 204.141.168.0/22 with origin AS46974 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46974 in the RIR database for the space. |
| Route object: none | 204.141.180.0/24 | No route object for it. Add a route object with origin AS46974 in the RIR database for the space. |
| Route object: none | 204.141.181.0/24 | No route object for it. Add a route object with origin AS46974 in the RIR database for the space. |
| Route object: none | 204.141.182.0/24 | No route object for it. Add a route object with origin AS46974 in the RIR database for the space. |
| Route object: none | 204.141.183.0/24 | No route object for it. Add a route object with origin AS46974 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS46974 whose prefix no peer sees AS46974 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 72.4.88.0/21 | ARIN | No ROA |
| 162.255.224.0/21 | NTTCOM | No ROA |
| 162.255.224.0/22 | ARIN, RADB | No ROA |
| 204.141.168.0/22 | NTTCOM | 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.