bgpreport

Network · data from 2026-11-12

AS61303 NETWAYS NETWAYS GmbH

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

7IPv4 routes 0.0% RPKI valid · 85.7% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
8No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS61303, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS61303, 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.11.255.255/32 No ROA Nonecovered by 185.11.252.0/22 5 1%low visibility 3
91.198.2.0/24 No ROA RIR databaseRIPE 673 100% 66
185.11.252.0/22 No ROA RIR databaseRIPE 673 100% 66
185.233.188.0/23 No ROA RIR databaseRIPE 673 100% 66
185.233.190.0/23 No ROA RIR databaseRIPE 673 100% 66
193.142.157.0/24 No ROA RIR databaseRIPE 673 100% 66
194.0.135.0/24 No ROA RIR databaseRIPE 673 100% 66
2a02:ed80::/29 No ROA RIR databaseRIPE 634 100% 67

AS-SET

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

  • ROA: none8
  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none185.11.255.255/32No ROA covers it. Add a ROA for AS61303, maxLength 32.5 of 673
Route object: none185.11.255.255/32No route object for it. A route object for 185.11.252.0/22 with origin AS61303 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS61303 in the RIR database for the space.5 of 673
ROA: none91.198.2.0/24No ROA covers it. Add a ROA for AS61303, maxLength 24.673 of 673
ROA: none185.11.252.0/22No ROA covers it. Add a ROA for AS61303, maxLength 22.673 of 673
ROA: none185.233.188.0/23No ROA covers it. Add a ROA for AS61303, maxLength 23.673 of 673
ROA: none185.233.190.0/23No ROA covers it. Add a ROA for AS61303, maxLength 23.673 of 673
ROA: none193.142.157.0/24No ROA covers it. Add a ROA for AS61303, maxLength 24.673 of 673
ROA: none194.0.135.0/24No ROA covers it. Add a ROA for AS61303, maxLength 24.673 of 673
ROA: none2a02:ed80::/29No ROA covers it. Add a ROA for AS61303, maxLength 29.634 of 636

Route objects not announced

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

31.31.92.0/22RIPENo ROA
31.31.92.0/23RIPENo ROA
31.31.94.0/23RIPENo ROA
185.233.188.0/22RIPENo ROA

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.