Shopware - Notice history

Customers may have experienced temporary unavailability when accessing multiple shops. During the incident, affected shops returned HTTP 503 errors while AWS performed scheduled maintenance on the underlying database infrastructure.

Because the affected databases used a single instance, the maintenance temporarily interrupted database connectivity and caused the affected application pods to become unavailable.

Timing
September 27, 2026, 23:45–23:48 UTC (September 28, 2026, 01:45–01:48 CEST)

Resolution
The AWS maintenance was completed, after which the affected databases and application pods recovered automatically. All services have been restored, and no further impact has been observed.

Follow-up improvement
We plan to strengthen database redundancy for live applications to improve resilience and reduce the potential impact of similar maintenance activities in the future.

We are currently addressing an issue affecting background task processing for some PaaS Native shops.

The issue was introduced by a recent change to worker auto-scaling, which can cause scheduled tasks to remain locked for several minutes and delay their processing.

We have identified the cause and are rolling out a fix. The update has been successfully tested, and we expect it to be fully deployed within approximately 30 minutes.

We will provide another update once the fix has been rolled out.

Impact: Some PaaS Native shops may experience delays in scheduled and background task processing.

We're experiencing an elevated level of application/connection errors and are currently looking into the issue.

This incident has been resolved.

Problem: Only 4 services are visible in the service registry in a new environment, and the remaining services are not showing up.

Impact: In new environments, users could only see 4 services in the service registry, and the remaining services could not be installed or accessed.

We are currently experiencing an elevated level of errors on the Shopware PaaS Native platform for building images.

Our team is actively investigating the issue and working to restore full service as quickly as possible.
We will provide updates as soon as more information becomes available.