Resolved after 2 hours 2 minutes, affecting Website Editor and Website Hosting (EU) and 1 more, on September 15, 2026.
Between 07:05 and 10:23 CEST, some visitors and customers experienced errors on our hosting platform. The trigger was a very large, short-lived attack of automated requests against our infrastructure, which our protection systems absorbed. As a side effect of that attack, our rate-limiting component began to wrongly reject a portion of legitimate requests with a 429 ("Too Many Requests") response, even though those requests were well within normal limits. Affected users mostly saw pages loading without styling or images, and the website editor sometimes failed to load. Websites, content and customer data were not affected, and no systems were accessed. Our team identified the affected component and restarted it at 10:23 CEST, which immediately restored normal request handling. We have since fully reconstructed the sequence of events from our logs and understand the root cause. We are reconfiguring the protection layer so that attack traffic can no longer interfere with how legitimate visitors are handled. We apologize for the disruption to you and your visitors.
Affected components
Update timeline
- investigating Sep 15, 2026, 08:55 AM UTC
We are currently investigating an increased rate of errors while accessing our infrastructure
- resolved Sep 15, 2026, 10:57 AM UTC
Between 07:05 and 10:23 CEST, some visitors and customers experienced errors on our hosting platform. The trigger was a very large, short-lived attack of automated requests against our infrastructure, which our protection systems absorbed. As a side effect of that attack, our rate-limiting component began to wrongly reject a portion of legitimate requests with a 429 ("Too Many Requests") response, even though those requests were well within normal limits. Affected users mostly saw pages loading without styling or images, and the website editor sometimes failed to load. Websites, content and customer data were not affected, and no systems were accessed. Our team identified the affected component and restarted it at 10:23 CEST, which immediately restored normal request handling. We have since fully reconstructed the sequence of events from our logs and understand the root cause. We are reconfiguring the protection layer so that attack traffic can no longer interfere with how legitimate visitors are handled. We apologize for the disruption to you and your visitors.
Your product runs on more than Sitejet
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services