bgpreport

Network · data from 2026-11-12

AS15854 DXC-AS15854 EntServ Deutschland GmbH

Registry name: DXC-AS15854 EntServ Deutschland GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS15854, 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.
195.203.156.0/22 Invalid: maxLength Other origin onlycovered by 195.203.128.0/17 115 17% 43
170.56.0.0/16 No ROA Other IRR onlyRADB, RIPE-NONAUTH 672 100% 67
139.27.0.0/16 No ROA RIR databaseRADB, RIPE 672 100% 67
149.206.0.0/16 No ROA RIR databaseRADB, RIPE 672 100% 67
149.211.0.0/16 No ROA RIR databaseRADB, RIPE 672 100% 67
149.250.0.0/16 Valid RIR databaseRADB, RIPE 673 100% 67
192.109.236.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
195.203.0.0/17 Valid RIR databaseRADB, RIPE 673 100% 67
195.203.128.0/17 Valid RIR databaseRADB, RIPE 673 100% 67
195.203.152.0/23 Valid RIR databaseRADB, RIPE 672 100% 67
217.27.0.0/23 Valid RIR databaseRADB, RIPE 672 100% 67
217.27.2.0/23 Valid RIR databaseRADB, RIPE 672 100% 67

AS-SET

AS15854 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: maxLength1
  • ROA: none4
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength195.203.156.0/22ROA 195.203.128.0/17 AS15854 has maxLength 17; the route is a /22. Raise the maxLength, or add a ROA for 195.203.156.0/22.115 of 673
Route object: none195.203.156.0/22Route objects for it name AS3360. A route object for 195.203.128.0/17 with origin AS15854 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15854 in the RIR database for the space.115 of 673
ROA: none170.56.0.0/16No ROA covers it. Add a ROA for AS15854, maxLength 16.672 of 673
Route object: RIR170.56.0.0/16Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.672 of 673
ROA: none139.27.0.0/16No ROA covers it. Add a ROA for AS15854, maxLength 16.672 of 673
ROA: none149.206.0.0/16No ROA covers it. Add a ROA for AS15854, maxLength 16.672 of 673
ROA: none149.211.0.0/16No ROA covers it. Add a ROA for AS15854, maxLength 16.672 of 673

Route objects not announced

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

168.87.32.0/23RIPE-NONAUTHNo ROA
170.56.0.0/17RIPE-NONAUTHNo ROA
2a03:5000::/32RIPENo 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.