bgpreport

Network · data from 2026-11-12

AS203560 REGFISH-AS regfish GmbH

Registry name: REGFISH-AS regfish GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS203560, 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.8.170.0/24 Valid Nonecovered by 185.8.168.0/22 672 100% 67
185.8.169.0/24 Valid Nonecovered by 185.8.168.0/22 671 100% 67
185.8.168.0/24 Valid Nonecovered by 185.8.168.0/22 2 0%low visibility 2
178.21.144.0/24 Valid Other IRR onlyRADB 672 100% 66
178.21.145.0/24 Valid Other IRR onlyRADB 672 100% 66
178.21.146.0/24 Valid Other IRR onlyRADB 672 100% 66
2a02:2c0::/48 Valid Other IRR onlyRADB 635 100% 68
2a02:2c0:1::/48 Valid Other IRR onlyRADB 635 100% 68
2a02:2c0:2::/48 Valid Other IRR onlyRADB 635 100% 68

AS-SET

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

  • Route object: none3
  • Route object: RIR6
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none185.8.170.0/24No route object for it. A route object for 185.8.168.0/22 with origin AS203560 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203560 in the RIR database for the space.672 of 673
Route object: none185.8.169.0/24No route object for it. A route object for 185.8.168.0/22 with origin AS203560 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203560 in the RIR database for the space.671 of 673
Route object: none185.8.168.0/24No route object for it. A route object for 185.8.168.0/22 with origin AS203560 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203560 in the RIR database for the space.2 of 673
Route object: RIR178.21.144.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR178.21.145.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR178.21.146.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2a02:2c0::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2a02:2c0:1::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2a02:2c0:2::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

178.21.147.0/24RADBNo ROA
185.8.168.0/22RIPENo ROA
2a02:2c0:3::/48RADBNo ROA
2a02:2c0:10::/48RIPEValid
2a02:2c0:11::/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.