Viskan - Issues with Backoffice – Incident details

Incident summary — Brief Backoffice unavailability

Period: 29 September 2026, 11:50–11:55 CEST
Affected services: Viskan Backoffice

Impact
For about five minutes, Backoffice and some related services were slow or unresponsive. No data was lost, and all services recovered fully by 11:55 CEST.

Cause
An unusually high volume of automated image requests from an external crawler caused the incident. Our media service, which resizes and optimizes images on demand, came under heavy load while processing these requests. This load affected the performance of other internal components, including Backoffice, until the requests subsided.

What we have done
We have set resource limits on the media service and guaranteed resource allocations for Backoffice and other critical components. A similar spike in image requests would now be contained within the media service without affecting the rest of the platform.

What we will do

• Introduce rate limits on image requests, so a high volume from a single source cannot overload the media service.

• Limit how many images the media service processes at once, so large bursts are handled gradually instead of all at once.

• Adjust our monitoring and alert thresholds so we detect this type of load pattern before it affects customers.