bgpreport

Network · data from 2026-11-12

AS24875 NovoServe B.V.

Registry name: NOVOSERVE-AS NovoServe B.V., NL · PeeringDB

37IPv4 routes 21.6% RPKI valid · 16.2% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
25RPKI invalid 24 origin · 1 maxLength
4No ROA 31 with no route object for this origin
29Low visibility seen by under 10% of full-table peers
25Route objects not announced registered with origin AS24875, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS24875, 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.8.179.186/32 Invalid: origin None 2 0%low visibility 9
45.141.61.162/32 Invalid: origin None 2 0%low visibility 9
45.159.93.108/32 Invalid: origin None 2 0%low visibility 9
45.159.95.217/32 Invalid: origin None 2 0%low visibility 9
46.249.105.132/32 Invalid: origin Nonecovered by 46.249.105.0/24 2 0%low visibility 9
46.249.105.176/32 Invalid: origin Nonecovered by 46.249.105.0/24 2 0%low visibility 9
46.249.105.186/32 Invalid: origin Nonecovered by 46.249.105.0/24 2 0%low visibility 9
46.249.105.205/32 Invalid: origin Nonecovered by 46.249.105.0/24 2 0%low visibility 9
46.249.105.211/32 Invalid: origin Nonecovered by 46.249.105.0/24 2 0%low visibility 9
46.249.105.215/32 Invalid: origin Nonecovered by 46.249.105.0/24 2 0%low visibility 9
46.249.105.246/32 Invalid: origin Nonecovered by 46.249.105.0/24 2 0%low visibility 9
46.249.105.253/32 Invalid: origin Nonecovered by 46.249.105.0/24 2 0%low visibility 9
94.124.78.86/32 Invalid: origin None 2 0%low visibility 9
95.134.201.181/32 Invalid: origin None 2 0%low visibility 9
95.134.201.185/32 Invalid: origin None 2 0%low visibility 9
149.57.53.17/32 Invalid: origin None 2 0%low visibility 9
154.16.180.215/32 Invalid: origin Nonecovered by 154.16.180.0/24 2 0%low visibility 9
185.224.217.216/32 Invalid: origin None 2 0%low visibility 9
191.96.100.65/32 Invalid: origin None 2 0%low visibility 9
194.87.251.145/32 Invalid: origin None 2 0%low visibility 9
194.87.251.146/32 Invalid: origin None 2 0%low visibility 9
212.18.115.226/32 Invalid: origin Nonecovered by 212.18.115.0/24 2 0%low visibility 9
213.220.62.78/32 Invalid: origin None 2 0%low visibility 9
217.60.253.25/32 Invalid: origin None 2 0%low visibility 9
89.105.204.95/32 Invalid: maxLength Nonecovered by 89.105.192.0/20 2 0%low visibility 10
154.6.42.5/32 No ROA None 4 1%low visibility 10
154.6.42.22/32 No ROA None 4 1%low visibility 10
154.6.42.207/32 No ROA None 4 1%low visibility 10
154.6.42.216/32 No ROA None 4 1%low visibility 10
185.147.13.0/24 Valid Nonecovered by 185.147.12.0/22 673 100% 66
185.147.14.0/23 Valid Nonecovered by 185.147.12.0/22 673 100% 66
45.129.176.0/22 Valid RIR databaseRIPE 673 100% 66
46.182.108.0/24 Valid RIR databaseRIPE 673 100% 66
80.89.224.0/20 Valid RIR databaseRIPE 673 100% 66
89.105.192.0/19 Valid RIR databaseRIPE 673 100% 66
185.80.232.0/22 Valid RIR databaseRIPE 673 100% 66
2.58.21.0/24 Valid RIR databaseRIPE 672 100% 66
2001:968::/29 Valid RIR databaseRIPE 635 100% 67
2a00:11f8::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS24875: RIPE::AS-NOVOSERVE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS24875 isn't in the set, or no route object for AS24875 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS24875 in itNot covered
RIPE::AS-NOVOSERVE RIPElists itself further down 122132,808 Yes 29

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 85 are in fix.csv.

  • ROA: origin24
  • ROA: maxLength1
  • ROA: none4
  • Route object: none31
  • Route object: not announced25
ChangePrefix or setDetailFull-table peers
ROA: origin45.8.179.186/32ROAs covering it name AS199458, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none45.8.179.186/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin45.141.61.162/32ROAs covering it name AS208518, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none45.141.61.162/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin45.159.93.108/32ROAs covering it name AS133150, AS199458, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none45.159.93.108/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin45.159.95.217/32ROAs covering it name AS133150, AS199458, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none45.159.95.217/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin46.249.105.132/32ROAs covering it name AS142019, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none46.249.105.132/32No route object for it. A route object for 46.249.105.0/24 with origin AS24875 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin46.249.105.176/32ROAs covering it name AS142019, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none46.249.105.176/32No route object for it. A route object for 46.249.105.0/24 with origin AS24875 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin46.249.105.186/32ROAs covering it name AS142019, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none46.249.105.186/32No route object for it. A route object for 46.249.105.0/24 with origin AS24875 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin46.249.105.205/32ROAs covering it name AS142019, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none46.249.105.205/32No route object for it. A route object for 46.249.105.0/24 with origin AS24875 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin46.249.105.211/32ROAs covering it name AS142019, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none46.249.105.211/32No route object for it. A route object for 46.249.105.0/24 with origin AS24875 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin46.249.105.215/32ROAs covering it name AS142019, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none46.249.105.215/32No route object for it. A route object for 46.249.105.0/24 with origin AS24875 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin46.249.105.246/32ROAs covering it name AS142019, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none46.249.105.246/32No route object for it. A route object for 46.249.105.0/24 with origin AS24875 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin46.249.105.253/32ROAs covering it name AS142019, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none46.249.105.253/32No route object for it. A route object for 46.249.105.0/24 with origin AS24875 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin94.124.78.86/32ROAs covering it name AS204601, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none94.124.78.86/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin95.134.201.181/32ROAs covering it name AS211484, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none95.134.201.181/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin95.134.201.185/32ROAs covering it name AS211484, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none95.134.201.185/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin149.57.53.17/32ROAs covering it name AS199458, AS218437, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none149.57.53.17/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin154.16.180.215/32ROAs covering it name AS211484, AS215224, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none154.16.180.215/32No route object for it. A route object for 154.16.180.0/24 with origin AS24875 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin185.224.217.216/32ROAs covering it name AS203436, AS215224, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none185.224.217.216/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin191.96.100.65/32ROAs covering it name AS211484, AS215224, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none191.96.100.65/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin194.87.251.145/32ROAs covering it name AS215821, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none194.87.251.145/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin194.87.251.146/32ROAs covering it name AS215821, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none194.87.251.146/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin212.18.115.226/32ROAs covering it name AS211484, AS215224, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none212.18.115.226/32No route object for it. A route object for 212.18.115.0/24 with origin AS24875 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin213.220.62.78/32ROAs covering it name AS133150, AS133153, AS213918, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none213.220.62.78/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: origin217.60.253.25/32ROAs covering it name AS213385, AS215224, AS215304, not AS24875. If AS24875 should announce it, add a ROA for AS24875.2 of 673
Route object: none217.60.253.25/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: maxLength89.105.204.95/32ROA 89.105.192.0/19 AS24875 has maxLength 19; ROA 89.105.192.0/20 AS24875 has maxLength 20; the route is a /32. Raise the maxLength, or add a ROA for 89.105.204.95/32.2 of 673
Route object: none89.105.204.95/32No route object for it. A route object for 89.105.192.0/20 with origin AS24875 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24875 in the RIR database for the space.2 of 673
ROA: none154.6.42.5/32No ROA covers it. Add a ROA for AS24875, maxLength 32.4 of 673
Route object: none154.6.42.5/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.4 of 673
ROA: none154.6.42.22/32No ROA covers it. Add a ROA for AS24875, maxLength 32.4 of 673
Route object: none154.6.42.22/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.4 of 673
ROA: none154.6.42.207/32No ROA covers it. Add a ROA for AS24875, maxLength 32.4 of 673
Route object: none154.6.42.207/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.4 of 673
ROA: none154.6.42.216/32No ROA covers it. Add a ROA for AS24875, maxLength 32.4 of 673
Route object: none154.6.42.216/32No route object for it. Add a route object with origin AS24875 in the RIR database for the space.4 of 673
Route object: none185.147.13.0/24No route object for it. A route object for 185.147.12.0/22 with origin AS24875 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24875 in the RIR database for the space.673 of 673
Route object: none185.147.14.0/23No route object for it. A route object for 185.147.12.0/22 with origin AS24875 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24875 in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS24875 whose prefix no peer sees AS24875 announce. Many are kept on purpose (backup routes, space announced only in some places).

2.58.22.0/24RIPENo ROA
45.93.17.0/24RIPEInvalid: origin
45.93.32.0/22RIPEValid
45.155.225.0/24RIPEInvalid: origin
46.249.104.0/24RIPEInvalid: origin
46.249.105.0/24RIPEInvalid: origin
46.249.106.0/24RIPEInvalid: origin
80.89.230.0/23RIPEValid
80.89.232.0/23RIPEValid
82.39.175.0/24RADB, RIPEValid
89.105.192.0/20RIPEValid
89.105.208.0/20RIPEValid
154.16.180.0/24AFRINICInvalid: origin
156.249.18.0/32AFRINICInvalid: origin
172.82.179.0/24ARINInvalid: origin
185.80.232.0/23RIPEValid
185.80.234.0/23RIPEValid
185.147.12.0/22RIPEValid
185.245.3.0/24RIPEValid
195.238.121.0/24RIPEInvalid: origin
212.18.115.0/24RIPEInvalid: origin
2001:968::/32RIPEValid
2a00:11f8::/32RIPEValid
2a07:5440::/29RIPEValid
2a07:5440::/32RIPEValid

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.