bgpreport

Network · data from 2026-11-12

AS13128 IT-Dienstleistungszentrum Berlin

Registry name: LIT-BERLIN-AS IT-Dienstleistungszentrum Berlin, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13128, 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.

2a02:1022::/32 No ROA RIR databaseRIPE 635 100% 68
141.15.0.0/16 Valid RIR databaseRIPE 670 100% 67

AS-SET

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

  • ROA: none1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none2a02:1022::/32No ROA covers it. Add a ROA for AS13128, maxLength 32.635 of 636

Route objects not announced

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

141.15.10.0/24RIPEInvalid: maxLength
141.15.11.0/24RIPEInvalid: maxLength
141.15.12.0/24RIPEInvalid: maxLength
141.15.28.0/23RIPEInvalid: maxLength
141.15.30.0/23RIPEInvalid: maxLength
141.15.32.0/23RIPEInvalid: maxLength
141.15.34.0/24RIPEInvalid: maxLength
141.15.35.0/24RIPEInvalid: maxLength
141.15.65.0/24RIPEInvalid: maxLength
141.15.101.0/24RIPEInvalid: maxLength
141.15.254.0/24RIPEInvalid: maxLength
2a02:1023::/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.