Network · data from 2026-11-12
AS402133 NOVOSERVE-LLC-CUSTOMERS-AS - NovoServe LLC
Registry name: NOVOSERVE-LLC-CUSTOMERS-AS - NovoServe LLC, US · not in PeeringDB
18IPv4 routes
66.7% RPKI valid · 44.4% with a route object
0IPv6 routes
2RPKI invalid
2 origin · 0 maxLength
4No ROA
10 with no route object for this origin
10Low visibility
seen by under 10% of full-table peers
10Route objects not announced
registered with origin AS402133, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS402133, 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.
| 172.94.43.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 206.123.142.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 104.250.173.0/24 | No ROA | None | 2 0%low visibility |
| 172.94.47.0/24 | No ROA | None | 2 0%low visibility |
| 192.253.254.0/24 | No ROA | Other origin only | 1 0%low visibility |
| 206.123.141.0/24 | No ROA | None | 1 0%low visibility |
| 188.215.236.0/24 | Valid | Nonecovered by 188.215.236.0/22 | 2 0%low visibility |
| 188.215.237.0/24 | Valid | Other origin onlycovered by 188.215.236.0/22 | 2 0%low visibility |
| 188.215.238.0/24 | Valid | Other origin onlycovered by 188.215.236.0/22 | 2 0%low visibility |
| 188.215.239.0/24 | Valid | Other origin onlycovered by 188.215.236.0/22 | 2 0%low visibility |
| 79.180.252.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 91.143.180.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 79.182.35.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 152.237.237.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 186.241.164.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 151.246.191.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 45.41.54.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 188.214.230.0/24 | Valid | RIR databaseRIPE | 661 98% |
AS-SET
AS402133 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 28 are in fix.csv.
- ROA: origin2
- ROA: none4
- Route object: none10
- Route object: RIR2
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 172.94.43.0/24 | ROAs covering it name AS205960, not AS402133. If AS402133 should announce it, add a ROA for AS402133. |
| Route object: none | 172.94.43.0/24 | Route objects for it name AS205960. Add a route object with origin AS402133 in the RIR database for the space. |
| ROA: origin | 206.123.142.0/24 | ROAs covering it name AS205960, not AS402133. If AS402133 should announce it, add a ROA for AS402133. |
| Route object: none | 206.123.142.0/24 | Route objects for it name AS53356, AS205960. Add a route object with origin AS402133 in the RIR database for the space. |
| ROA: none | 104.250.173.0/24 | No ROA covers it. Add a ROA for AS402133, maxLength 24. |
| Route object: none | 104.250.173.0/24 | No route object for it. Add a route object with origin AS402133 in the RIR database for the space. |
| ROA: none | 172.94.47.0/24 | No ROA covers it. Add a ROA for AS402133, maxLength 24. |
| Route object: none | 172.94.47.0/24 | No route object for it. Add a route object with origin AS402133 in the RIR database for the space. |
| ROA: none | 192.253.254.0/24 | No ROA covers it. Add a ROA for AS402133, maxLength 24. |
| Route object: none | 192.253.254.0/24 | Route objects for it name AS38001. Add a route object with origin AS402133 in the RIR database for the space. |
| ROA: none | 206.123.141.0/24 | No ROA covers it. Add a ROA for AS402133, maxLength 24. |
| Route object: none | 206.123.141.0/24 | No route object for it. Add a route object with origin AS402133 in the RIR database for the space. |
| Route object: none | 188.215.236.0/24 | No route object for it. A route object for 188.215.236.0/22 with origin AS402133 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402133 in the RIR database for the space. |
| Route object: none | 188.215.237.0/24 | Route objects for it name AS4766. A route object for 188.215.236.0/22 with origin AS402133 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402133 in the RIR database for the space. |
| Route object: none | 188.215.238.0/24 | Route objects for it name AS4766. A route object for 188.215.236.0/22 with origin AS402133 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402133 in the RIR database for the space. |
| Route object: none | 188.215.239.0/24 | Route objects for it name AS4766. A route object for 188.215.236.0/22 with origin AS402133 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402133 in the RIR database for the space. |
| Route object: RIR | 79.180.252.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 91.143.180.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS402133 whose prefix no peer sees AS402133 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 62.144.59.0/24 | RADB, RIPE | Valid |
| 107.149.157.0/24 | ARIN, RADB | Valid |
| 146.103.59.0/24 | RADB, RIPE | Valid |
| 148.135.194.0/24 | RADB, RIPE | Valid |
| 167.148.84.0/23 | RADB, RIPE | Valid |
| 167.148.84.0/24 | RIPE | Valid |
| 167.148.85.0/24 | RIPE | Valid |
| 168.222.46.0/24 | RADB, RIPE | Valid |
| 188.215.236.0/22 | RIPE | Valid |
| 2a0f:9400:7900::/40 | RIPE | Invalid: origin |
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.