bgpreport

Network · data from 2026-11-12

AS214996 netcup netcup GmbH

Registry name: netcup netcup GmbH, DE · not in PeeringDB

24IPv4 routes 100.0% RPKI valid · 95.8% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS214996, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS214996, 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.
152.53.208.0/22 Valid Nonecovered by 152.53.208.0/20 673 100% 67
62.83.48.0/24 Valid RIR databaseRIPE 673 100% 67
62.83.60.0/22 Valid RIR databaseRIPE 673 100% 67
62.83.64.0/22 Valid RIR databaseRIPE 673 100% 67
152.53.31.0/24 Valid RIR databaseRIPE 673 100% 67
152.53.36.0/22 Valid RIR databaseRIPE 673 100% 67
152.53.52.0/22 Valid RIR databaseRIPE 673 100% 67
152.53.68.0/24 Valid RIR databaseRIPE 673 100% 67
152.53.80.0/22 Valid RIR databaseRIPE 673 100% 67
152.53.88.0/22 Valid RIR databaseRIPE 673 100% 67
152.53.164.0/22 Valid RIR databaseRIPE 673 100% 67
152.53.168.0/22 Valid RIR databaseRIPE 673 100% 67
152.53.192.0/22 Valid RIR databaseRIPE 673 100% 67
152.53.201.0/24 Valid RIR databaseRIPE 673 100% 67
152.53.208.0/20 Valid RIR databaseRIPE 673 100% 67
152.53.212.0/24 Valid RIR databaseRIPE 673 100% 67
152.53.240.0/22 Valid RIR databaseRIPE 673 100% 67
159.195.12.0/22 Valid RIR databaseRIPE 673 100% 67
159.195.16.0/22 Valid RIR databaseRIPE 673 100% 67
159.195.107.0/24 Valid RIR databaseRIPE 673 100% 67
159.195.232.0/22 Valid RIR databaseRIPE 673 100% 67
159.195.236.0/22 Valid RIR databaseRIPE 673 100% 67
159.195.91.0/24 Valid RIR databaseRIPE 671 100% 67
159.195.92.0/22 Valid RIR databaseRIPE 671 100% 67
2a0a:4cc0:120::/43 Valid RIR databaseRIPE 636 100% 67
2a0a:4cc0:101::/48 Valid RIR databaseRIPE 635 100% 67
2a0a:4cc0:2000::/43 Valid RIR databaseRIPE 635 100% 67

AS-SET

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

  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none152.53.208.0/22No route object for it. A route object for 152.53.208.0/20 with origin AS214996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214996 in the RIR database for the space.673 of 673

Route objects not announced

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

152.53.192.0/20RIPEValid
2a0a:4cc0:2000::/48RIPEValid

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.