Network · data from 2026-11-12
AS198969 Magna-Pars-Internet-Technologies-AS NovoServe B.V.
Registry name: Magna-Pars-Internet-Technologies-AS NovoServe B.V., NL · not in PeeringDB
38IPv4 routes
65.8% RPKI valid · 65.8% with a route object
0IPv6 routes
13RPKI invalid
13 origin · 0 maxLength
0No ROA
13 with no route object for this origin
16Low visibility
seen by under 10% of full-table peers
7Route objects not announced
registered with origin AS198969, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS198969, 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.
| 45.93.32.0/22 | Invalid: origin | Other origin only | 4 1%low visibility |
| 93.119.232.0/24 | Invalid: origin | None | 2 0%low visibility |
| 94.192.128.0/24 | Invalid: origin | None | 2 0%low visibility |
| 94.192.129.0/24 | Invalid: origin | None | 2 0%low visibility |
| 94.192.130.0/24 | Invalid: origin | None | 2 0%low visibility |
| 94.192.131.0/24 | Invalid: origin | None | 2 0%low visibility |
| 94.192.132.0/24 | Invalid: origin | None | 2 0%low visibility |
| 94.192.133.0/24 | Invalid: origin | None | 2 0%low visibility |
| 154.83.177.0/24 | Invalid: origin | RIR databaseAFRINIC | 2 0%low visibility |
| 154.83.178.0/24 | Invalid: origin | RIR databaseAFRINIC | 2 0%low visibility |
| 154.83.179.0/24 | Invalid: origin | RIR databaseAFRINIC | 2 0%low visibility |
| 154.83.180.0/24 | Invalid: origin | RIR databaseAFRINIC | 2 0%low visibility |
| 154.83.181.0/24 | Invalid: origin | RIR databaseAFRINIC | 2 0%low visibility |
| 141.0.196.0/24 | Valid | Nonecovered by 141.0.196.0/22 | 673 100% |
| 141.0.197.0/24 | Valid | Nonecovered by 141.0.196.0/22 | 673 100% |
| 45.88.16.0/22 | Valid | None | 3 0%low visibility |
| 37.220.32.0/21 | Valid | None | 2 0%low visibility |
| 45.82.44.0/22 | Valid | None | 2 0%low visibility |
| 46.34.22.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 13.141.3.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 13.141.56.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 85.204.177.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.208.96.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 189.12.129.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 189.12.189.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 194.242.135.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 195.21.149.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 200.180.169.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 213.209.158.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.216.241.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 45.6.46.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.118.47.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 94.118.103.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 96.62.97.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 108.186.102.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 141.11.145.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 151.241.108.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 185.213.241.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
AS-SET
AS198969 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: origin13
- Route object: none13
- Route object: RIR1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 45.93.32.0/22 | ROAs covering it name AS24875, not AS198969. If AS198969 should announce it, add a ROA for AS198969. |
| Route object: none | 45.93.32.0/22 | Route objects for it name AS24875. Add a route object with origin AS198969 in the RIR database for the space. |
| ROA: origin | 93.119.232.0/24 | ROAs covering it name AS213705, not AS198969. If AS198969 should announce it, add a ROA for AS198969. |
| Route object: none | 93.119.232.0/24 | No route object for it. Add a route object with origin AS198969 in the RIR database for the space. |
| ROA: origin | 94.192.128.0/24 | ROAs covering it name AS834, not AS198969. If AS198969 should announce it, add a ROA for AS198969. |
| Route object: none | 94.192.128.0/24 | No route object for it. Add a route object with origin AS198969 in the RIR database for the space. |
| ROA: origin | 94.192.129.0/24 | ROAs covering it name AS834, not AS198969. If AS198969 should announce it, add a ROA for AS198969. |
| Route object: none | 94.192.129.0/24 | No route object for it. Add a route object with origin AS198969 in the RIR database for the space. |
| ROA: origin | 94.192.130.0/24 | ROAs covering it name AS834, not AS198969. If AS198969 should announce it, add a ROA for AS198969. |
| Route object: none | 94.192.130.0/24 | No route object for it. Add a route object with origin AS198969 in the RIR database for the space. |
| ROA: origin | 94.192.131.0/24 | ROAs covering it name AS834, not AS198969. If AS198969 should announce it, add a ROA for AS198969. |
| Route object: none | 94.192.131.0/24 | No route object for it. Add a route object with origin AS198969 in the RIR database for the space. |
| ROA: origin | 94.192.132.0/24 | ROAs covering it name AS834, not AS198969. If AS198969 should announce it, add a ROA for AS198969. |
| Route object: none | 94.192.132.0/24 | No route object for it. Add a route object with origin AS198969 in the RIR database for the space. |
| ROA: origin | 94.192.133.0/24 | ROAs covering it name AS834, not AS198969. If AS198969 should announce it, add a ROA for AS198969. |
| Route object: none | 94.192.133.0/24 | No route object for it. Add a route object with origin AS198969 in the RIR database for the space. |
| ROA: origin | 154.83.177.0/24 | ROAs covering it name AS17561, not AS198969. If AS198969 should announce it, add a ROA for AS198969. |
| ROA: origin | 154.83.178.0/24 | ROAs covering it name AS17561, not AS198969. If AS198969 should announce it, add a ROA for AS198969. |
| ROA: origin | 154.83.179.0/24 | ROAs covering it name AS17561, not AS198969. If AS198969 should announce it, add a ROA for AS198969. |
| ROA: origin | 154.83.180.0/24 | ROAs covering it name AS17561, not AS198969. If AS198969 should announce it, add a ROA for AS198969. |
| ROA: origin | 154.83.181.0/24 | ROAs covering it name AS17561, not AS198969. If AS198969 should announce it, add a ROA for AS198969. |
| Route object: none | 141.0.196.0/24 | No route object for it. A route object for 141.0.196.0/22 with origin AS198969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198969 in the RIR database for the space. |
| Route object: none | 141.0.197.0/24 | No route object for it. A route object for 141.0.196.0/22 with origin AS198969 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198969 in the RIR database for the space. |
| Route object: none | 45.88.16.0/22 | No route object for it. Add a route object with origin AS198969 in the RIR database for the space. |
| Route object: none | 37.220.32.0/21 | No route object for it. Add a route object with origin AS198969 in the RIR database for the space. |
| Route object: none | 45.82.44.0/22 | No route object for it. Add a route object with origin AS198969 in the RIR database for the space. |
| Route object: RIR | 46.34.22.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS198969 whose prefix no peer sees AS198969 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 86.110.34.0/24 | RADB, RIPE | Valid |
| 119.59.129.0/24 | APNIC | Invalid: origin |
| 119.59.131.0/24 | APNIC | Invalid: origin |
| 141.0.196.0/22 | RADB, RIPE | Valid |
| 212.189.108.0/23 | RADB, RIPE | Valid |
| 212.189.108.0/24 | RIPE | Valid |
| 212.189.109.0/24 | 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.