Sitejet Outage History

Started Sep 15, 2026, 08:55 AM UTC· resolved Sep 15, 2026, 10:57 AM UTC

1. investigating Sep 15, 2026, 08:55 AM UTC

   We are currently investigating an increased rate of errors while accessing our infrastructure

2. 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.

Read the full incident report →

Started Jun 01, 2026, 10:00 AM UTC· resolved Jun 01, 2026, 01:00 PM UTC

1. resolved Jun 01, 2026, 10:00 AM UTC

   During a scheduled urgent security update to the mail server software, a core mail delivery component failed to restart cleanly after the update. Outbound mail delivery was disrupted for approximately 3 hours. Meanwhile, all mail services are fully operational again.

Read the full incident report →

Started Apr 12, 2026, 01:32 PM UTC· resolved Apr 12, 2026, 01:41 PM UTC

1. resolved Apr 12, 2026, 12:30 PM UTC

   During the time frame of 2:32 PM to 2:41 PM CET, we experienced failures in some writing database operations. This failure had a direct impact on the functionality of the app, resulting in errors for users like saving changes in the Website Builder. The issue has been resolved. During this time, all websites were still reachable.

Read the full incident report →

Started Mar 10, 2026, 01:13 PM UTC· resolved Mar 10, 2026, 05:48 PM UTC

1. investigating Mar 10, 2026, 01:13 PM UTC

   We have identified an issue affecting the creation and modification of website content. Users experience errors when saving changes to their websites. The root cause has been identified. We are actively working on a fix that will expand capacity. We will provide updates during the process.

2. identified Mar 10, 2026, 03:44 PM UTC

   The issue has been identified and a fix is being implemented.

3. resolved Mar 10, 2026, 05:48 PM UTC

   This incident has been resolved

Read the full incident report →

Started Dec 04, 2025, 12:55 PM UTC· resolved Dec 04, 2025, 01:14 PM UTC

1. investigating Dec 04, 2025, 12:55 PM UTC

   We are currently investigating this issue.

2. resolved Dec 04, 2025, 01:14 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 31, 2025, 11:30 AM UTC· resolved Jul 31, 2025, 11:30 AM UTC

1. resolved Jul 31, 2025, 11:30 AM UTC

   We recently identified and resolved an issue affecting the delivery of newly user-uploaded images. A security-related configuration update introduced a change where application domains no longer serve user-uploaded images directly. These images are now delivered via our CDN for enhanced security and performance. However, a misconfiguration in this new setup resulted in images that were not yet scaled to requested dimensions being incorrectly redirected before processing could complete. This caused an infinite redirect loop. Already existing and scaled images were not affected. Resolution: The configuration issue has been corrected, and image delivery is now functioning as expected. We apologize for any inconvenience this has caused.

Read the full incident report →

Started Jun 10, 2025, 12:03 PM UTC· resolved Jun 10, 2025, 04:30 PM UTC

1. investigating Jun 10, 2025, 12:03 PM UTC

   See https://status.openai.com/ for more information

2. resolved Jun 10, 2025, 04:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 05, 2025, 10:35 AM UTC· resolved Mar 05, 2025, 10:49 AM UTC

1. resolved Mar 05, 2025, 10:30 AM UTC

   Today, our services were challenged by a substantial Distributed Denial of Service (DDoS) attack, causing sporadic 502 Bad Gateway errors in our User Interfaces between 11:35 and 11:49 (CET). Our automated countermeasures swiftly identified and blocked thousands of malicious IPs taking part in the attack, significantly minimizing its impact. While these efforts greatly mitigated the situation, some 502 errors were unavoidable. We apologize for the inconvenience and disruption this caused our users and are committed to enhancing our security posture to better handle such challenges in the future.

2. postmortem Mar 13, 2025, 02:43 PM UTC

   Due to the high number of concurrent requests with a long timeout, a middleware reached its connection limit and had to reject database requests, thus causing 502 errors within the User Interface. In the meantime, we heavily increased the connection capacity on that middleware to avoid such an issue in the future. Despite this unsuccessful attack, all websites remained fully operational, experiencing no downtime and maintaining their usual level of efficiency.

Read the full incident report →

Started Nov 18, 2024, 03:30 AM UTC· resolved Nov 18, 2024, 07:15 AM UTC

1. resolved Nov 18, 2024, 03:30 AM UTC

   An unplanned maintenance by our data center operator on the network infrastructure resulted in databases being set to a read-only mode, which caused errors in the application between 4:30 and 8:15 (CET).

Read the full incident report →