Network · data from 2026-11-12
AS48614 ITSOFT-AS ITSOFT LLC
Registry name: ITSOFT-AS ITSOFT LLC, RU · not in PeeringDB
28IPv4 routes
53.6% RPKI valid · 71.4% with a route object
4IPv6 routes
75.0% RPKI valid · 100.0% with a route object
4RPKI invalid
0 origin · 4 maxLength
10No ROA
8 with no route object for this origin
8Low visibility
seen by under 10% of full-table peers
2Route objects not announced
registered with origin AS48614, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS48614, 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.
| 185.185.58.250/32 | Invalid: maxLength | Nonecovered by 185.185.56.0/22 | 2 0%low visibility |
| 212.192.24.22/32 | Invalid: maxLength | Nonecovered by 212.192.24.0/22 | 2 0%low visibility |
| 212.192.24.139/32 | Invalid: maxLength | Nonecovered by 212.192.24.0/22 | 2 0%low visibility |
| 212.192.27.11/32 | Invalid: maxLength | Nonecovered by 212.192.24.0/22 | 2 0%low visibility |
| 37.230.141.3/32 | No ROA | Nonecovered by 37.230.141.0/24 | 5 1%low visibility |
| 37.230.141.21/32 | No ROA | Nonecovered by 37.230.141.0/24 | 5 1%low visibility |
| 45.15.253.8/32 | No ROA | Nonecovered by 45.15.253.0/24 | 5 1%low visibility |
| 94.79.54.124/32 | No ROA | Nonecovered by 94.79.54.0/23 | 5 1%low visibility |
| 37.230.141.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 45.15.253.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 94.79.19.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 94.79.54.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 213.79.122.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2a03:5a00:3e::/48 | No ROA | RIR databaseRIPE | 636 100% |
| 168.113.166.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 45.67.212.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 45.93.203.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 166.1.70.0/23 | Valid | RIR databaseARIN | 671 100% |
| 185.185.56.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 193.106.92.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 193.107.232.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 194.87.112.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 194.156.124.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 195.93.180.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 195.133.68.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 212.192.24.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 193.106.92.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 193.107.232.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 193.107.234.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 2a0b:4880::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0b:4880:1::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0b:4880:2::/48 | Valid | RIR databaseRIPE | 330 52% |
AS-SET
AS48614 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 24 are in fix.csv.
- ROA: maxLength4
- ROA: none10
- Route object: none8
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 185.185.58.250/32 | ROA 185.185.56.0/22 AS48614 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 185.185.58.250/32. |
| Route object: none | 185.185.58.250/32 | No route object for it. A route object for 185.185.56.0/22 with origin AS48614 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS48614 in the RIR database for the space. |
| ROA: maxLength | 212.192.24.22/32 | ROA 212.192.24.0/22 AS48614 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 212.192.24.22/32. |
| Route object: none | 212.192.24.22/32 | No route object for it. A route object for 212.192.24.0/22 with origin AS48614 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS48614 in the RIR database for the space. |
| ROA: maxLength | 212.192.24.139/32 | ROA 212.192.24.0/22 AS48614 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 212.192.24.139/32. |
| Route object: none | 212.192.24.139/32 | No route object for it. A route object for 212.192.24.0/22 with origin AS48614 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS48614 in the RIR database for the space. |
| ROA: maxLength | 212.192.27.11/32 | ROA 212.192.24.0/22 AS48614 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 212.192.27.11/32. |
| Route object: none | 212.192.27.11/32 | No route object for it. A route object for 212.192.24.0/22 with origin AS48614 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS48614 in the RIR database for the space. |
| ROA: none | 37.230.141.3/32 | No ROA covers it. Add a ROA for AS48614, maxLength 32. |
| Route object: none | 37.230.141.3/32 | No route object for it. A route object for 37.230.141.0/24 with origin AS48614 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS48614 in the RIR database for the space. |
| ROA: none | 37.230.141.21/32 | No ROA covers it. Add a ROA for AS48614, maxLength 32. |
| Route object: none | 37.230.141.21/32 | No route object for it. A route object for 37.230.141.0/24 with origin AS48614 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS48614 in the RIR database for the space. |
| ROA: none | 45.15.253.8/32 | No ROA covers it. Add a ROA for AS48614, maxLength 32. |
| Route object: none | 45.15.253.8/32 | No route object for it. A route object for 45.15.253.0/24 with origin AS48614 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS48614 in the RIR database for the space. |
| ROA: none | 94.79.54.124/32 | No ROA covers it. Add a ROA for AS48614, maxLength 32. |
| Route object: none | 94.79.54.124/32 | No route object for it. A route object for 94.79.54.0/23 with origin AS48614 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS48614 in the RIR database for the space. |
| ROA: none | 37.230.141.0/24 | No ROA covers it. Add a ROA for AS48614, maxLength 24. |
| ROA: none | 45.15.253.0/24 | No ROA covers it. Add a ROA for AS48614, maxLength 24. |
| ROA: none | 94.79.19.0/24 | No ROA covers it. Add a ROA for AS48614, maxLength 24. |
| ROA: none | 94.79.54.0/23 | No ROA covers it. Add a ROA for AS48614, maxLength 23. |
| ROA: none | 213.79.122.0/24 | No ROA covers it. Add a ROA for AS48614, maxLength 24. |
| ROA: none | 2a03:5a00:3e::/48 | No ROA covers it. Add a ROA for AS48614, maxLength 48. |
Route objects not announced
Route objects with origin AS48614 whose prefix no peer sees AS48614 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.105.214.0/24 | RIPE | No ROA |
| 5.105.215.0/24 | RIPE | No ROA |
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.