bgpreport

Network · data from 2026-11-12

AS13541 SIEMENS-DISW-WIV-B-ORW - Siemens Industry Software Inc.

Registry name: SIEMENS-DISW-WIV-B-ORW - Siemens Industry Software Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13541, 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.
134.86.0.0/16 No ROA None 668 99% 67
2620:107:f000::/40 No ROA None 636 100% 67
192.94.38.0/23 No ROA Other IRR onlyALTDB 673 100% 67
137.202.0.0/16 No ROA Other IRR onlyALTDB 668 99% 67
147.34.0.0/16 No ROA Other IRR onlyALTDB 668 99% 67
139.181.12.0/22 No ROA RIR databaseARIN 673 100% 67
139.181.17.0/24 No ROA RIR databaseARIN 673 100% 67
192.94.36.0/24 No ROA RIR databaseARIN 673 100% 67

AS-SET

AS13541 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 15 are in fix.csv.

  • ROA: none8
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none134.86.0.0/16No ROA covers it. Add a ROA for AS13541, maxLength 16.668 of 673
Route object: none134.86.0.0/16No route object for it. Add a route object with origin AS13541 in the RIR database for the space.668 of 673
ROA: none2620:107:f000::/40No ROA covers it. Add a ROA for AS13541, maxLength 40.636 of 636
Route object: none2620:107:f000::/40No route object for it. Add a route object with origin AS13541 in the RIR database for the space.636 of 636
ROA: none192.94.38.0/23No ROA covers it. Add a ROA for AS13541, maxLength 23.673 of 673
Route object: RIR192.94.38.0/23Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none137.202.0.0/16No ROA covers it. Add a ROA for AS13541, maxLength 16.668 of 673
Route object: RIR137.202.0.0/16Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none147.34.0.0/16No ROA covers it. Add a ROA for AS13541, maxLength 16.668 of 673
Route object: RIR147.34.0.0/16Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none139.181.12.0/22No ROA covers it. Add a ROA for AS13541, maxLength 22.673 of 673
ROA: none139.181.17.0/24No ROA covers it. Add a ROA for AS13541, maxLength 24.673 of 673
ROA: none192.94.36.0/24No ROA covers it. Add a ROA for AS13541, maxLength 24.673 of 673

Route objects not announced

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

192.94.38.0/24ARINNo ROA
192.94.39.0/24ARINNo 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.