bgpreport

Network · data from 2026-11-12

AS43155 SW-BIELEFELD-AS Stadtwerke Bielefeld GmbH

Registry name: SW-BIELEFELD-AS Stadtwerke Bielefeld GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS43155, 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.
2a06:1080:0:1::/64 No ROA Nonecovered by 2a06:1080::/29 1 0%low visibility 2
2a06:1080:0:2::/64 No ROA Nonecovered by 2a06:1080::/29 1 0%low visibility 2
2a06:1080:0:117::/64 No ROA Nonecovered by 2a06:1080::/29 1 0%low visibility 2
91.194.108.0/23 No ROA RIR databaseRIPE 673 100% 66
185.99.52.0/22 No ROA RIR databaseRIPE 673 100% 66
185.99.55.0/24 No ROA RIR databaseRIPE 673 100% 66
2a06:1080::/29 No ROA RIR databaseRIPE 634 100% 67

AS-SET

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

  • ROA: none7
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none2a06:1080:0:1::/64No ROA covers it. Add a ROA for AS43155, maxLength 64.1 of 636
Route object: none2a06:1080:0:1::/64No route object for it. A route object for 2a06:1080::/29 with origin AS43155 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS43155 in the RIR database for the space.1 of 636
ROA: none2a06:1080:0:2::/64No ROA covers it. Add a ROA for AS43155, maxLength 64.1 of 636
Route object: none2a06:1080:0:2::/64No route object for it. A route object for 2a06:1080::/29 with origin AS43155 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS43155 in the RIR database for the space.1 of 636
ROA: none2a06:1080:0:117::/64No ROA covers it. Add a ROA for AS43155, maxLength 64.1 of 636
Route object: none2a06:1080:0:117::/64No route object for it. A route object for 2a06:1080::/29 with origin AS43155 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS43155 in the RIR database for the space.1 of 636
ROA: none91.194.108.0/23No ROA covers it. Add a ROA for AS43155, maxLength 23.673 of 673
ROA: none185.99.52.0/22No ROA covers it. Add a ROA for AS43155, maxLength 22.673 of 673
ROA: none185.99.55.0/24No ROA covers it. Add a ROA for AS43155, maxLength 24.673 of 673
ROA: none2a06:1080::/29No ROA covers it. Add a ROA for AS43155, maxLength 29.634 of 636

Route objects not announced

Every route object with origin AS43155 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.