bgpreport

Network · data from 2026-11-12

AS202373 Stadtwerke Rostock

Registry name: Stadtwerke-Rostock Stadtwerke Rostock AG, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202373, 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.
84.38.77.0/24 Valid Nonecovered by 84.38.76.0/23 672 100% 66
194.34.156.0/24 Valid Nonecovered by 194.34.156.0/22 672 100% 66
194.34.157.0/24 Valid Nonecovered by 194.34.156.0/22 672 100% 66
194.34.158.0/24 Valid Nonecovered by 194.34.156.0/22 672 100% 66
194.34.159.0/24 Valid Nonecovered by 194.34.156.0/22 672 100% 66
194.55.97.0/24 Valid Nonecovered by 194.55.96.0/22 672 100% 66
194.55.98.0/24 Valid Nonecovered by 194.55.96.0/22 672 100% 66
84.38.76.0/23 Valid RIR databaseRIPE 672 100% 66
194.34.156.0/22 Valid RIR databaseRIPE 672 100% 66
194.55.96.0/22 Valid RIR databaseRIPE 672 100% 66
2a0c:cac0::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

AS202373's PeeringDB record names no 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 7 are in fix.csv.

  • Route object: none7
ChangePrefix or setDetailFull-table peers
Route object: none84.38.77.0/24No route object for it. A route object for 84.38.76.0/23 with origin AS202373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202373 in the RIR database for the space.672 of 673
Route object: none194.34.156.0/24No route object for it. A route object for 194.34.156.0/22 with origin AS202373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202373 in the RIR database for the space.672 of 673
Route object: none194.34.157.0/24No route object for it. A route object for 194.34.156.0/22 with origin AS202373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202373 in the RIR database for the space.672 of 673
Route object: none194.34.158.0/24No route object for it. A route object for 194.34.156.0/22 with origin AS202373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202373 in the RIR database for the space.672 of 673
Route object: none194.34.159.0/24No route object for it. A route object for 194.34.156.0/22 with origin AS202373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202373 in the RIR database for the space.672 of 673
Route object: none194.55.97.0/24No route object for it. A route object for 194.55.96.0/22 with origin AS202373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202373 in the RIR database for the space.672 of 673
Route object: none194.55.98.0/24No route object for it. A route object for 194.55.96.0/22 with origin AS202373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202373 in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS202373 is announced.

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.