<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>EnderDevelopment Status - Incident history</title>
    <link>https://enderdevelopment.instatus.com</link>
    <description>EnderDevelopment</description>
    <pubDate>Fri, 10 Apr 2026 21:55:40 +0000</pubDate>
    
<item>
  <title>Official Site is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Official Site
    Apr 10, 21:55:41 GMT+0 - Investigating - Official Site is currently experiencing issues. This incident has been automatically triggered following a system alert. The situation could be due to a brief unexpected maintenance or a more persistent technical problem. We’re investigating and will update you shortly. Apr 10, 22:38:52 GMT+0 - Resolved - Official Site is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:55:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Official Site is currently experiencing issues. This incident has been automatically triggered following a system alert. The situation could be due to a brief unexpected maintenance or a more persistent technical problem. We’re investigating and will update you shortly..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:38:52&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Official Site is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 10 Apr 2026 21:55:40 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/incident/cmntg339e0emejoma9bje6r4s</link>
  <guid>https://enderdevelopment.instatus.com/incident/cmntg339e0emejoma9bje6r4s</guid>
</item>

<item>
  <title>Official Site is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Official Site
    Apr 3, 05:53:58 GMT+0 - Investigating - Official Site is currently experiencing issues. This incident has been automatically triggered following a system alert. The situation could be due to a brief unexpected maintenance or a more persistent technical problem. We’re investigating and will update you shortly. Apr 3, 05:55:43 GMT+0 - Resolved - Official Site is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:53:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Official Site is currently experiencing issues. This incident has been automatically triggered following a system alert. The situation could be due to a brief unexpected maintenance or a more persistent technical problem. We’re investigating and will update you shortly..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:55:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Official Site is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 3 Apr 2026 05:53:57 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/incident/cmnihncm905b6w0tudne6x9tp</link>
  <guid>https://enderdevelopment.instatus.com/incident/cmnihncm905b6w0tudne6x9tp</guid>
</item>

<item>
  <title>Official Site is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Official Site
    Apr 2, 08:01:48 GMT+0 - Resolved - Official Site is back up. This incident was automatically resolved by Instatus monitoring. Apr 2, 00:04:23 GMT+0 - Investigating - Official Site is currently experiencing issues. This incident has been automatically triggered following a system alert. The situation could be due to a brief unexpected maintenance or a more persistent technical problem. We’re investigating and will update you shortly. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:01:48&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Official Site is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:04:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Official Site is currently experiencing issues. This incident has been automatically triggered following a system alert. The situation could be due to a brief unexpected maintenance or a more persistent technical problem. We’re investigating and will update you shortly..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 2 Apr 2026 00:04:23 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/incident/cmngppy4p04tgwrwphytpfixx</link>
  <guid>https://enderdevelopment.instatus.com/incident/cmngppy4p04tgwrwphytpfixx</guid>
</item>

<item>
  <title>Official Site is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Official Site
    Apr 1, 23:23:49 GMT+0 - Investigating - Official Site is currently experiencing issues. This incident has been automatically triggered following a system alert. The situation could be due to a brief unexpected maintenance or a more persistent technical problem. We’re investigating and will update you shortly. Apr 1, 23:47:38 GMT+0 - Resolved - Official Site is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:23:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Official Site is currently experiencing issues. This incident has been automatically triggered following a system alert. The situation could be due to a brief unexpected maintenance or a more persistent technical problem. We’re investigating and will update you shortly..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:47:38&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Official Site is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 1 Apr 2026 23:23:48 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/incident/cmngo9r6b04nnoasxs7lkhjfb</link>
  <guid>https://enderdevelopment.instatus.com/incident/cmngo9r6b04nnoasxs7lkhjfb</guid>
</item>

<item>
  <title>Extended Maintenance – Upgrade Window - Platform remain fully online</title>
  <description>
    Type: Maintenance
    Duration: 1 day and 4 hours

    Affected Components: Dashboard, EndAI - Core
    Mar 26, 21:00:00 GMT+0 - Identified - We are initiating a **long-term maintenance window (\~28 hours)** to implement major improvements to our **core architecture and plugin generation system**.

This work is focused on addressing the current **high rate of build and code failures**, with the goal of delivering a **more reliable, stable, and high-quality output pipeline**.

The platform will remain **fully online**, however you may experience:

* **Temporary fatal errors**
* Intermittent availability
* Slower processing or failed tasks during restarts

This is a significant upgrade aimed at **fundamentally improving system performance and consistency**.

We appreciate your patience Mar 26, 21:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 27, 17:50:54 GMT+0 - Identified - After \~20 hours of ongoing maintenance, we’ve achieved a **major breakthrough in build performance**.

We’ve successfully optimized the system to the point where **\~80% of Minecraft plugins now build successfully on the first attempt**, compared to **\~10% previously**.

We identified this issue later than expected, and we sincerely apologize for the impact it may have caused.

To make up for it, we will be sending an **email to all users with a special discount**.

Work is still ongoing as we continue refining the system — but this is a huge step forward.

Thank you for sticking with us Mar 28, 01:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 day and 4 hours</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are initiating a **long-term maintenance window (\~28 hours)** to implement major improvements to our **core architecture and plugin generation system**.

This work is focused on addressing the current **high rate of build and code failures**, with the goal of delivering a **more reliable, stable, and high-quality output pipeline**.

The platform will remain **fully online**, however you may experience:

* **Temporary fatal errors**
* Intermittent availability
* Slower processing or failed tasks during restarts

This is a significant upgrade aimed at **fundamentally improving system performance and consistency**.

We appreciate your patience.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:50:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  After \~20 hours of ongoing maintenance, we’ve achieved a **major breakthrough in build performance**.

We’ve successfully optimized the system to the point where **\~80% of Minecraft plugins now build successfully on the first attempt**, compared to **\~10% previously**.

We identified this issue later than expected, and we sincerely apologize for the impact it may have caused.

To make up for it, we will be sending an **email to all users with a special discount**.

Work is still ongoing as we continue refining the system — but this is a huge step forward.

Thank you for sticking with us.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 26 Mar 2026 21:00:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/maintenance/cmn7x47c80b7nn1odf9lypmzu</link>
  <guid>https://enderdevelopment.instatus.com/maintenance/cmn7x47c80b7nn1odf9lypmzu</guid>
</item>

<item>
  <title>Misclassification Issue</title>
  <description>
    Type: Incident
    Duration: 19 minutes

    Affected Components: EndAI - Core
    Mar 25, 18:33:52 GMT+0 - Investigating - We are currently experiencing an internal bug where, for an unexpected reason, **all projects are being incorrectly identified as Discord bots**.

Our team is actively **investigating the root cause** and working to resolve the issue as quickly as possible.

We apologize for the confusion and any disruption this may cause — updates will follow shortly. Mar 25, 18:38:35 GMT+0 - Identified - The misclassification issue has been **fully resolved**, and projects are now being handled correctly.

We are now actively **investigating a separate issue** related to **plan generation**, specifically around **progressive iterations and quality degradation over time**.

Our team is working to identify the root cause and ensure consistent performance across all iterations.

Thank you for your patience — further updates will follow. Mar 25, 18:52:36 GMT+0 - Resolved - The issue has been **fully resolved**, and we’ve also deployed improvements affecting **existing project refactoring**.

This results in more consistent behavior and better overall reliability across projects.

Thank you for your patience 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 19 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:33:52&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing an internal bug where, for an unexpected reason, **all projects are being incorrectly identified as Discord bots**.

Our team is actively **investigating the root cause** and working to resolve the issue as quickly as possible.

We apologize for the confusion and any disruption this may cause — updates will follow shortly..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:38:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The misclassification issue has been **fully resolved**, and projects are now being handled correctly.

We are now actively **investigating a separate issue** related to **plan generation**, specifically around **progressive iterations and quality degradation over time**.

Our team is working to identify the root cause and ensure consistent performance across all iterations.

Thank you for your patience — further updates will follow..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:52:36&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue has been **fully resolved**, and we’ve also deployed improvements affecting **existing project refactoring**.

This results in more consistent behavior and better overall reliability across projects.

Thank you for your patience.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 25 Mar 2026 18:33:52 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/incident/cmn6dtvve01f9jfghil9jv6vq</link>
  <guid>https://enderdevelopment.instatus.com/incident/cmn6dtvve01f9jfghil9jv6vq</guid>
</item>

<item>
  <title>Official Site is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Official Site
    Mar 25, 07:22:04 GMT+0 - Investigating - Official Site is currently experiencing issues. This incident has been automatically triggered following a system alert. The situation could be due to a brief unexpected maintenance or a more persistent technical problem. We’re investigating and will update you shortly. Mar 25, 07:32:12 GMT+0 - Resolved - Official Site is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:22:04&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Official Site is currently experiencing issues. This incident has been automatically triggered following a system alert. The situation could be due to a brief unexpected maintenance or a more persistent technical problem. We’re investigating and will update you shortly..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:32:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Official Site is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 25 Mar 2026 07:22:03 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/incident/cmn5ptyqe00t8n7ofa9fiiecy</link>
  <guid>https://enderdevelopment.instatus.com/incident/cmn5ptyqe00t8n7ofa9fiiecy</guid>
</item>

<item>
  <title>Next-Level Improvements Rolling Out</title>
  <description>
    Type: Maintenance
    Duration: 11 hours

    Affected Components: Dashboard, EndAI - Storage, EndAI - Core
    Mar 24, 14:00:00 GMT+0 - Identified - We will be performing a **major long-running maintenance window (up to \~10 hours)** to deploy deep improvements across our infrastructure.

Additionally, **1–2 shorter follow-up maintenance phases** may occur related to this update.

While these operations are designed to be seamless, you may experience:

* **Brief disconnections (&lt;1 minute)**
* **Occasionally incomplete tasks**
* **Temporary interruptions during processing**

These are expected, as we will be performing **frequent restarts of our backend systems and AI providers** as part of a major overhaul.

This maintenance is aimed at significantly improving:

* **Code quality**
* **Platform stability**
* **Overall user experience**

We appreciate your patience - this is a big step forward for the platform 🚀 Mar 24, 14:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 25, 01:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 11 hours</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We will be performing a **major long-running maintenance window (up to \~10 hours)** to deploy deep improvements across our infrastructure.

Additionally, **1–2 shorter follow-up maintenance phases** may occur related to this update.

While these operations are designed to be seamless, you may experience:

* **Brief disconnections (&lt;1 minute)**
* **Occasionally incomplete tasks**
* **Temporary interruptions during processing**

These are expected, as we will be performing **frequent restarts of our backend systems and AI providers** as part of a major overhaul.

This maintenance is aimed at significantly improving:

* **Code quality**
* **Platform stability**
* **Overall user experience**

We appreciate your patience - this is a big step forward for the platform 🚀.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 24 Mar 2026 14:00:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/maintenance/cmn4nir7107zi11j16v43z4t8</link>
  <guid>https://enderdevelopment.instatus.com/maintenance/cmn4nir7107zi11j16v43z4t8</guid>
</item>

<item>
  <title>Ongoing Service Disruption</title>
  <description>
    Type: Incident
    Duration: 6 hours and 42 minutes

    Affected Components: Dashboard, EndAI - Core
    Mar 23, 16:18:56 GMT+0 - Monitoring - We’ve deployed a **potentially definitive fix** to address the recurring backend issue.

The system is now stable, and we are **actively monitoring performance and behavior in real-time** to ensure everything remains fully operational.

While early signals are positive, we’ll keep a close watch to confirm long-term stability.

Thank you again for your patience Mar 23, 17:38:38 GMT+0 - Identified - The issue has unfortunately **reoccurred** and is again affecting the platform.

Our team is actively **investigating the root cause** and working toward a stable resolution.

We apologize for the continued inconvenience and will provide further updates shortly. Mar 23, 17:48:12 GMT+0 - Monitoring - The issue now appears to be **resolved again**, and the platform is returning to normal operation.

We are currently **optimizing and fine-tuning the system** to improve overall stability and prevent further occurrences.

We will continue monitoring closely. Mar 23, 22:42:27 GMT+0 - Resolved - The issue has been **fully resolved**.

Root cause was identified as **blocking synchronous operations on remote storage**, combined with **locking mechanisms that caused backend stalls under load**.

We have addressed these bottlenecks and implemented fixes to ensure smoother, non-blocking behavior.

The system is now stable and operating normally.

Thank you for your patience Mar 23, 16:00:28 GMT+0 - Investigating - We are currently experiencing a **recurring incident** where the issue has reappeared, causing **backend instability and temporary system blocks**.

This may result in **failed requests, slow performance, or temporary unavailability** of certain features.

Our team is actively investigating the root cause and working on a **permanent fix**. Additional backend restarts and adjustments may occur during this process.

We sincerely apologize for the continued disruption and appreciate your patience while we resolve this once and for all. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 42 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:18:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We’ve deployed a **potentially definitive fix** to address the recurring backend issue.

The system is now stable, and we are **actively monitoring performance and behavior in real-time** to ensure everything remains fully operational.

While early signals are positive, we’ll keep a close watch to confirm long-term stability.

Thank you again for your patience.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:38:38&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue has unfortunately **reoccurred** and is again affecting the platform.

Our team is actively **investigating the root cause** and working toward a stable resolution.

We apologize for the continued inconvenience and will provide further updates shortly..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:48:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The issue now appears to be **resolved again**, and the platform is returning to normal operation.

We are currently **optimizing and fine-tuning the system** to improve overall stability and prevent further occurrences.

We will continue monitoring closely..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:42:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue has been **fully resolved**.

Root cause was identified as **blocking synchronous operations on remote storage**, combined with **locking mechanisms that caused backend stalls under load**.

We have addressed these bottlenecks and implemented fixes to ensure smoother, non-blocking behavior.

The system is now stable and operating normally.

Thank you for your patience.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:00:28&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing a **recurring incident** where the issue has reappeared, causing **backend instability and temporary system blocks**.

This may result in **failed requests, slow performance, or temporary unavailability** of certain features.

Our team is actively investigating the root cause and working on a **permanent fix**. Additional backend restarts and adjustments may occur during this process.

We sincerely apologize for the continued disruption and appreciate your patience while we resolve this once and for all..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 23 Mar 2026 16:00:28 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/incident/cmn3dgxdi06sd147yk2ncfrmd</link>
  <guid>https://enderdevelopment.instatus.com/incident/cmn3dgxdi06sd147yk2ncfrmd</guid>
</item>

<item>
  <title>Service Disruption</title>
  <description>
    Type: Incident
    Duration: 27 minutes

    Affected Components: Dashboard, EndAI - Storage
    Mar 22, 17:30:51 GMT+0 - Investigating - We are currently experiencing a **new incident affecting platform stability**, caused by an issue in the backend infrastructure that is impacting system reliability and request handling.

As a result, some users may encounter **errors, slow responses, or temporary unavailability**.

Our team is actively working on a resolution. This may require **additional backend restarts and configuration adjustments** while we stabilize the system.

We sincerely apologize for the inconvenience and are prioritizing a full fix as quickly as possible.

Thank you for your patience. Mar 22, 17:57:29 GMT+0 - Resolved - The issue has been **identified, monitored, and fully resolved**.

We have taken immediate action to stabilize the system and ensure everything is now operating correctly.

We will continue to monitor closely and implement additional safeguards — **we expect this not to occur again**.

Thank you for your patience  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 27 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:30:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing a **new incident affecting platform stability**, caused by an issue in the backend infrastructure that is impacting system reliability and request handling.

As a result, some users may encounter **errors, slow responses, or temporary unavailability**.

Our team is actively working on a resolution. This may require **additional backend restarts and configuration adjustments** while we stabilize the system.

We sincerely apologize for the inconvenience and are prioritizing a full fix as quickly as possible.

Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:57:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue has been **identified, monitored, and fully resolved**.

We have taken immediate action to stabilize the system and ensure everything is now operating correctly.

We will continue to monitor closely and implement additional safeguards — **we expect this not to occur again**.

Thank you for your patience .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 22 Mar 2026 17:30:51 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/incident/cmn219c8m0qo6wzchdbfsb834</link>
  <guid>https://enderdevelopment.instatus.com/incident/cmn219c8m0qo6wzchdbfsb834</guid>
</item>

<item>
  <title>Degraded Performance and Service Interruptions</title>
  <description>
    Type: Incident
    Duration: 45 minutes

    Affected Components: Dashboard, EndAI - Core
    Mar 22, 10:17:12 GMT+0 - Investigating - We are currently experiencing a service disruption affecting parts of our platform.

The issue is caused by unexpected rate limiting behavior combined with database locking, which is leading to significant slowdowns and, in some cases, complete workflow interruptions.

Our team is actively investigating and working to mitigate the impact as quickly as possible. During this time, you may experience degraded performance or temporary unavailability of certain features.

We will provide further updates as soon as more information becomes available.

Thank you for your patience. Mar 22, 10:21:55 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 22, 11:01:51 GMT+0 - Resolved - The rate limiting issue has been successfully identified and resolved.

We are currently investigating additional minor bugs that may still impact the user experience, causing occasional inconsistencies or friction in workflows. While these issues are not causing major outages, they may still affect usability.

Our team is actively working to address them and further stabilize the platform. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 45 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:17:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing a service disruption affecting parts of our platform.

The issue is caused by unexpected rate limiting behavior combined with database locking, which is leading to significant slowdowns and, in some cases, complete workflow interruptions.

Our team is actively investigating and working to mitigate the impact as quickly as possible. During this time, you may experience degraded performance or temporary unavailability of certain features.

We will provide further updates as soon as more information becomes available.

Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:21:55&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:01:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The rate limiting issue has been successfully identified and resolved.

We are currently investigating additional minor bugs that may still impact the user experience, causing occasional inconsistencies or friction in workflows. While these issues are not causing major outages, they may still affect usability.

Our team is actively working to address them and further stabilize the platform..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 22 Mar 2026 10:17:12 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/incident/cmn1lrn7g0m6d995pqinpty22</link>
  <guid>https://enderdevelopment.instatus.com/incident/cmn1lrn7g0m6d995pqinpty22</guid>
</item>

<item>
  <title>Ongoing Platform Improvements</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Dashboard, EndAI - Core
    Mar 21, 23:40:00 GMT+0 - Identified - We’re currently rolling out a series of **major improvements and critical fixes** based directly on user feedback.

These updates require **frequent backend restarts** and configuration changes, which may cause **temporary minor disruptions** while using the platform.

We sincerely apologize for the inconvenience, but these changes are essential to deliver **significant improvements in stability, performance, and overall service quality**.

Thanks for your patience Mar 21, 23:40:01 GMT+0 - Identified - Maintenance is now in progress Mar 22, 01:40:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We’re currently rolling out a series of **major improvements and critical fixes** based directly on user feedback.

These updates require **frequent backend restarts** and configuration changes, which may cause **temporary minor disruptions** while using the platform.

We sincerely apologize for the inconvenience, but these changes are essential to deliver **significant improvements in stability, performance, and overall service quality**.

Thanks for your patience.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:40:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 21 Mar 2026 23:40:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/maintenance/cmn0yyjll0feo995pp20mp0gq</link>
  <guid>https://enderdevelopment.instatus.com/maintenance/cmn0yyjll0feo995pp20mp0gq</guid>
</item>

<item>
  <title>Brief System Update (Possible Short Downtime)</title>
  <description>
    Type: Maintenance
    Duration: 5 minutes

    Affected Components: Server AMS-3, Host Free Bot, , Server AMS-2, EndAI - Core, Official Site, , EndAI, LeakVision, Server AMS-1 [Main], 
EnderDevelopment - Services → 
EnderDevelopment - Official Site →
    Mar 14, 19:45:00 GMT+0 - Identified - We will perform a brief system update shortly.  
A **short downtime of less than 5 minutes** may occur while updates are applied.

Our team is working to ensure the process is completed as quickly as possible.

Thank you for your patience. Mar 14, 19:45:01 GMT+0 - Identified - Maintenance is now in progress Mar 14, 19:50:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We will perform a brief system update shortly.  
A **short downtime of less than 5 minutes** may occur while updates are applied.

Our team is working to ensure the process is completed as quickly as possible.

Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:45:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:50:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 14 Mar 2026 19:45:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/maintenance/cmmqqhw110crqw2il7djujtbq</link>
  <guid>https://enderdevelopment.instatus.com/maintenance/cmmqqhw110crqw2il7djujtbq</guid>
</item>

<item>
  <title>AI Response Degradation</title>
  <description>
    Type: Incident
    Duration: 9 hours and 8 minutes

    Affected Components: EndAI - Core
    Mar 7, 10:56:43 GMT+0 - Investigating - We are currently investigating a degradation in AI response performance across the platform. Users may experience slower response times and, in some cases, reduced output quality from the AI services.

Our engineering team has identified abnormal latency patterns affecting the response pipeline and is actively analyzing system logs, infrastructure metrics, and recent deployments to determine the root cause.

Mitigation actions are in progress while the investigation continues. Further updates will be provided as more information becomes available.

We appreciate your patience while we work to restore full service performance. Mar 7, 11:42:18 GMT+0 - Identified - The root cause of the performance degradation has been identified. The issue was related to inefficiencies within part of the AI response processing pipeline.

Several fixes have already been implemented, resulting in an improvement of response times by approximately **200%** compared to the degraded state observed earlier.

Our engineering team is continuing to work on additional optimizations to fully resolve the issue and eliminate the remaining minor failures that may still occur in some cases.

We will continue monitoring the system closely and provide further updates as progress is made. Mar 7, 12:02:46 GMT+0 - Identified - Following the previously implemented fixes, we observed a significant improvement in response times (approximately 200% compared to the degraded state). However, the issue has not yet been fully resolved and some performance instability and minor failures are still being reported.

Our engineering team is continuing to investigate the underlying causes and is actively working on additional fixes to stabilize the AI response pipeline.

We will provide further updates as soon as more information becomes available. Mar 7, 12:16:09 GMT+0 - Monitoring - Additional fixes and optimizations have been deployed to the AI response pipeline. Following these changes, system performance has significantly improved and response times appear to have stabilized.

We are currently monitoring the platform closely to ensure the system remains stable and that no further performance degradation occurs.

Further updates will be provided if necessary. Mar 7, 12:53:39 GMT+0 - Investigating - Following additional instability detected during the monitoring phase, we have temporarily taken the affected AI services offline to prevent further degradation of the platform.

Our engineering team is currently re-evaluating the system and conducting a deeper analysis of the underlying issues affecting the AI response pipeline. This includes reviewing infrastructure metrics, recent changes, and internal processing components.

We are actively working to identify the remaining root causes and will provide further updates as soon as more information becomes available. Mar 7, 14:40:06 GMT+0 - Monitoring - The root cause of the instability has now been identified and resolved. After an extensive investigation, our engineering team worked intensively to modify parts of the AI core management responsible for the performance degradation.

The updated system has been deployed and is expected to stabilize fully within the next few minutes.

Alongside this fix, we will also release a set of changelogs outlining the improvements made, including the introduction of a new **&quot;Reason&quot; mode** that can be toggled On or Off.

We are currently monitoring the platform closely to ensure stability across all AI services. Mar 7, 20:05:05 GMT+0 - Resolved - All systems are now fully operational and AI services have returned to normal performance levels.

Following an extensive investigation conducted throughout the day, our engineering team identified that the primary cause of the instability was related to the internal request management system of the **AI Core**.

While the platform is still in beta, the rapid growth in active users and request volume exposed architectural limitations in the original request handling pipeline. The system responsible for managing AI inference requests had become increasingly inefficient under higher concurrency, leading to abnormal latency patterns, degraded response performance, and intermittent failures.

To resolve the issue, we performed a significant refactor of the AI Core request management layer. This included rewriting key parts of the response pipeline to improve concurrency handling, request scheduling, and internal processing flow.

The updated architecture has now been deployed across the platform and early metrics show stable latency and normal response throughput.

Alongside this fix, several improvements have been introduced, including internal optimizations and the upcoming release of the **&quot;Reason&quot; mode**, which can be toggled On or Off depending on the use case.

We will continue monitoring the platform closely over the next hours to ensure long-term stability.

We sincerely thank our users for their patience during this incident while our team worked to restore full service reliability. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 hours and 8 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:56:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating a degradation in AI response performance across the platform. Users may experience slower response times and, in some cases, reduced output quality from the AI services.

Our engineering team has identified abnormal latency patterns affecting the response pipeline and is actively analyzing system logs, infrastructure metrics, and recent deployments to determine the root cause.

Mitigation actions are in progress while the investigation continues. Further updates will be provided as more information becomes available.

We appreciate your patience while we work to restore full service performance..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:42:18&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The root cause of the performance degradation has been identified. The issue was related to inefficiencies within part of the AI response processing pipeline.

Several fixes have already been implemented, resulting in an improvement of response times by approximately **200%** compared to the degraded state observed earlier.

Our engineering team is continuing to work on additional optimizations to fully resolve the issue and eliminate the remaining minor failures that may still occur in some cases.

We will continue monitoring the system closely and provide further updates as progress is made..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:02:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Following the previously implemented fixes, we observed a significant improvement in response times (approximately 200% compared to the degraded state). However, the issue has not yet been fully resolved and some performance instability and minor failures are still being reported.

Our engineering team is continuing to investigate the underlying causes and is actively working on additional fixes to stabilize the AI response pipeline.

We will provide further updates as soon as more information becomes available..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:16:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Additional fixes and optimizations have been deployed to the AI response pipeline. Following these changes, system performance has significantly improved and response times appear to have stabilized.

We are currently monitoring the platform closely to ensure the system remains stable and that no further performance degradation occurs.

Further updates will be provided if necessary..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:53:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Following additional instability detected during the monitoring phase, we have temporarily taken the affected AI services offline to prevent further degradation of the platform.

Our engineering team is currently re-evaluating the system and conducting a deeper analysis of the underlying issues affecting the AI response pipeline. This includes reviewing infrastructure metrics, recent changes, and internal processing components.

We are actively working to identify the remaining root causes and will provide further updates as soon as more information becomes available..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:40:06&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The root cause of the instability has now been identified and resolved. After an extensive investigation, our engineering team worked intensively to modify parts of the AI core management responsible for the performance degradation.

The updated system has been deployed and is expected to stabilize fully within the next few minutes.

Alongside this fix, we will also release a set of changelogs outlining the improvements made, including the introduction of a new **&quot;Reason&quot; mode** that can be toggled On or Off.

We are currently monitoring the platform closely to ensure stability across all AI services..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:05:05&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  All systems are now fully operational and AI services have returned to normal performance levels.

Following an extensive investigation conducted throughout the day, our engineering team identified that the primary cause of the instability was related to the internal request management system of the **AI Core**.

While the platform is still in beta, the rapid growth in active users and request volume exposed architectural limitations in the original request handling pipeline. The system responsible for managing AI inference requests had become increasingly inefficient under higher concurrency, leading to abnormal latency patterns, degraded response performance, and intermittent failures.

To resolve the issue, we performed a significant refactor of the AI Core request management layer. This included rewriting key parts of the response pipeline to improve concurrency handling, request scheduling, and internal processing flow.

The updated architecture has now been deployed across the platform and early metrics show stable latency and normal response throughput.

Alongside this fix, several improvements have been introduced, including internal optimizations and the upcoming release of the **&quot;Reason&quot; mode**, which can be toggled On or Off depending on the use case.

We will continue monitoring the platform closely over the next hours to ensure long-term stability.

We sincerely thank our users for their patience during this incident while our team worked to restore full service reliability..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 7 Mar 2026 10:56:43 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/incident/cmmg7ko0603yxia99ehxd5qva</link>
  <guid>https://enderdevelopment.instatus.com/incident/cmmg7ko0603yxia99ehxd5qva</guid>
</item>

<item>
  <title>Login &amp; Dashboard Access Issues</title>
  <description>
    Type: Incident
    Duration: 4 minutes

    
    Feb 27, 23:25:46 GMT+0 - Investigating - We are currently experiencing issues affecting user login and dashboard access. Some users may encounter authentication failures, session invalidation, or incomplete dashboard loading.

Our team has identified the anomaly and is actively investigating the root cause. Initial analysis suggests a potential issue related to session handling and/or backend service communication.

We are prioritizing this incident and will provide updates as soon as more information becomes available.

We apologize for the inconvenience and appreciate your patience. Feb 27, 23:30:09 GMT+0 - Resolved - The login and dashboard access issue has been fully resolved.

The disruption was caused by an internal credentials modification error, which temporarily impacted authentication and dashboard services. Although the duration of the incident was brief, the impact was significant.

Once identified, the incorrect configuration was immediately reverted and services were restored to full functionality.

We are reviewing our internal change management procedures to prevent similar incidents in the future.

We sincerely apologize for the inconvenience caused and appreciate your understanding. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:25:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing issues affecting user login and dashboard access. Some users may encounter authentication failures, session invalidation, or incomplete dashboard loading.

Our team has identified the anomaly and is actively investigating the root cause. Initial analysis suggests a potential issue related to session handling and/or backend service communication.

We are prioritizing this incident and will provide updates as soon as more information becomes available.

We apologize for the inconvenience and appreciate your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:30:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The login and dashboard access issue has been fully resolved.

The disruption was caused by an internal credentials modification error, which temporarily impacted authentication and dashboard services. Although the duration of the incident was brief, the impact was significant.

Once identified, the incorrect configuration was immediately reverted and services were restored to full functionality.

We are reviewing our internal change management procedures to prevent similar incidents in the future.

We sincerely apologize for the inconvenience caused and appreciate your understanding..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 27 Feb 2026 23:25:46 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/incident/cmm5it6or00du41jwe25ao2bj</link>
  <guid>https://enderdevelopment.instatus.com/incident/cmm5it6or00du41jwe25ao2bj</guid>
</item>

<item>
  <title>Intermittent Instability via Cloudflare Proxy</title>
  <description>
    Type: Incident
    Duration: 58 minutes

    
    Feb 26, 18:18:16 GMT+0 - Investigating - We are currently investigating an intermittent instability affecting `dash.enderdevelopment.com` when accessed through Cloudflare.

Some users may experience:

* Error 520 (Unknown Error)
* Temporary connection drops
* Inconsistent behavior on specific routes

Initial analysis indicates the issue appears to be related to the interaction between Cloudflare’s proxy layer and the origin server connection handling. Direct origin access does not show persistent failures.

We are actively monitoring the situation and applying configuration adjustments to improve connection stability.

Further updates will follow as soon as additional diagnostics are completed. Feb 26, 18:45:19 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Feb 26, 19:15:55 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 58 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:18:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an intermittent instability affecting `dash.enderdevelopment.com` when accessed through Cloudflare.

Some users may experience:

* Error 520 (Unknown Error)
* Temporary connection drops
* Inconsistent behavior on specific routes

Initial analysis indicates the issue appears to be related to the interaction between Cloudflare’s proxy layer and the origin server connection handling. Direct origin access does not show persistent failures.

We are actively monitoring the situation and applying configuration adjustments to improve connection stability.

Further updates will follow as soon as additional diagnostics are completed..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:45:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:15:55&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 26 Feb 2026 18:18:16 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/incident/cmm3sdujn02y6n3vlxycejgqx</link>
  <guid>https://enderdevelopment.instatus.com/incident/cmm3sdujn02y6n3vlxycejgqx</guid>
</item>

<item>
  <title>Datacenter Migration</title>
  <description>
    Type: Maintenance
    Duration: 12 hours

    Affected Components: Server AMS-3, Host Free Bot, Server AMS-2, EndAI - Core, EndAI - Storage, Server NYC-1, Official Site, EndAI, LeakVision, Server AMS-1 [Main]
    Feb 18, 05:00:00 GMT+0 - Identified - Our infrastructure provider will be performing a full datacenter migration affecting the environment where our services are hosted.

During this maintenance window:

* All websites will be temporarily unavailable
* The AI platform will be offline
* APIs and backend services may not respond
* Management dashboards will not be accessible

This is a scheduled infrastructure-level operation outside of our direct control, aimed at improving overall stability, reliability, and performance.

No data loss is expected.

Once the migration is completed, services will be gradually restored and closely monitored to ensure full operational stability.

We apologize for the temporary inconvenience and appreciate your understanding. Feb 18, 05:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 18, 17:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 12 hours</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our infrastructure provider will be performing a full datacenter migration affecting the environment where our services are hosted.

During this maintenance window:

* All websites will be temporarily unavailable
* The AI platform will be offline
* APIs and backend services may not respond
* Management dashboards will not be accessible

This is a scheduled infrastructure-level operation outside of our direct control, aimed at improving overall stability, reliability, and performance.

No data loss is expected.

Once the migration is completed, services will be gradually restored and closely monitored to ensure full operational stability.

We apologize for the temporary inconvenience and appreciate your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 18 Feb 2026 05:00:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/maintenance/cmlr2h19h005tr0up6u6s00v6</link>
  <guid>https://enderdevelopment.instatus.com/maintenance/cmlr2h19h005tr0up6u6s00v6</guid>
</item>

<item>
  <title>Discord Full Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 6 hours

    Affected Components: Official Site
    Jan 1, 15:45:00 GMT+0 - Identified - We are officially starting the **2026 Roadmap**.  
Right now, the Discord server is undergoing a **full restructuring** to align with our new vision and systems.

Channels, roles, and structure will change.  
This is intentional.

This channel will remain active for official updates only.  
More soon. Jan 1, 15:45:01 GMT+0 - Identified - Maintenance is now in progress Jan 1, 21:45:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 6 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are officially starting the **2026 Roadmap**.  
Right now, the Discord server is undergoing a **full restructuring** to align with our new vision and systems.

Channels, roles, and structure will change.  
This is intentional.

This channel will remain active for official updates only.  
More soon..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:45:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 1 Jan 2026 15:45:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/maintenance/cmjvm5tlj006018h09m522wxt</link>
  <guid>https://enderdevelopment.instatus.com/maintenance/cmjvm5tlj006018h09m522wxt</guid>
</item>

<item>
  <title>Planned API &amp; Backend Migration in Progres</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 43 minutes

    Affected Components: Server AMS-2, EndAI
    Dec 13, 17:25:00 GMT+0 - Identified - We’re currently performing a planned migration of our API infrastructure and backend services to improve stability, performance, and reliability.

**What to expect during this migration:**

* Temporary service interruptions or delays may occur.
* Some features might be temporarily unavailable.

**After the migration:**  
All services will automatically resume normal operation—no action is needed on your part. The migration is expected to be completed within the next 2 hours, after which full functionality will be restored.

Thank you for your patience and understanding as we work to make our platform faster, more reliable, and better for everyone! Dec 13, 17:28:02 GMT+0 - Identified - Maintenance is now in progress. Dec 13, 19:11:27 GMT+0 - Completed - The migration of our API infrastructure and backend services has been successfully completed.

**What’s new:**

* Improved system stability and performance.
* Faster response times across all services.
* Backend fully optimized for reliability and scalability.

All services are now running normally—no action is required on your part.

_Thank you for your patience and support as we worked to make our platform faster, more reliable, and better for everyone!_ 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 43 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:25:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We’re currently performing a planned migration of our API infrastructure and backend services to improve stability, performance, and reliability.

**What to expect during this migration:**

* Temporary service interruptions or delays may occur.
* Some features might be temporarily unavailable.

**After the migration:**  
All services will automatically resume normal operation—no action is needed on your part. The migration is expected to be completed within the next 2 hours, after which full functionality will be restored.

Thank you for your patience and understanding as we work to make our platform faster, more reliable, and better for everyone!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:28:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:11:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The migration of our API infrastructure and backend services has been successfully completed.

**What’s new:**

* Improved system stability and performance.
* Faster response times across all services.
* Backend fully optimized for reliability and scalability.

All services are now running normally—no action is required on your part.

_Thank you for your patience and support as we worked to make our platform faster, more reliable, and better for everyone!_.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 13 Dec 2025 17:25:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/maintenance/cmj4kjq75055wddah2yq46kca</link>
  <guid>https://enderdevelopment.instatus.com/maintenance/cmj4kjq75055wddah2yq46kca</guid>
</item>

<item>
  <title>Degraded Service</title>
  <description>
    Type: Incident
    Duration: 14 hours and 39 minutes

    Affected Components: , Official Site, EndAI, LeakVision, Server AMS-1 [Main], 
EnderDevelopment - Official Site →
    Nov 18, 19:28:59 GMT+0 - Investigating - After spending the entire afternoon conducting extensive software-level diagnostics and running multiple targeted tests across our AMS-1 environment, we have confirmed that the issue is **not originating from the application or service layer**.

All internal checks : including service integrity, configuration validation, and network stack inspection—returned consistent results, leading us to conclude that the root cause is likely located at a **lower-level infrastructure layer** within the datacenter.

To ensure a precise and immediate resolution, our technicians are being dispatched to the datacenter in the next few minutes.  
They will perform on-rack inspections, hardware verification, and low-level network checks. A fix will be applied **on-site** as soon as the anomalous component is identified.

A further update will be provided once the on-site analysis begins. Nov 18, 19:34:47 GMT+0 - Investigating - Our technicians have arrived at the datacenter and will now begin a full on-site inspection.  
They will investigate the root cause for approximately **1 hour and 30 minutes** before applying the necessary fix.

Further updates will follow as soon as we have confirmed results. Nov 18, 22:53:23 GMT+0 - Resolved - We are pleased to confirm that the issue affecting AMS-1 has been fully **identified and resolved**.

A special thanks goes to **Lorenzo from DeluxHost**, who collaborated actively with our team throughout the investigation and resolution process.  
His direct support at the datacenter allowed us to apply the fix immediately and restore full stability across the infrastructure.

Thank you all for your patience during this incident.  
All systems are now operating normally. Nov 18, 12:31:16 GMT+0 - Investigating - &lt;https://www.cloudflarestatus.com/incidents/8gmgl950y3h7&gt; Nov 18, 08:14:00 GMT+0 - Investigating - We have some problem with the Main Server of our infrastructure AMS-1.  
  
We are investigating about the issue 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 hours and 39 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:28:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  After spending the entire afternoon conducting extensive software-level diagnostics and running multiple targeted tests across our AMS-1 environment, we have confirmed that the issue is **not originating from the application or service layer**.

All internal checks : including service integrity, configuration validation, and network stack inspection—returned consistent results, leading us to conclude that the root cause is likely located at a **lower-level infrastructure layer** within the datacenter.

To ensure a precise and immediate resolution, our technicians are being dispatched to the datacenter in the next few minutes.  
They will perform on-rack inspections, hardware verification, and low-level network checks. A fix will be applied **on-site** as soon as the anomalous component is identified.

A further update will be provided once the on-site analysis begins..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:34:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Our technicians have arrived at the datacenter and will now begin a full on-site inspection.  
They will investigate the root cause for approximately **1 hour and 30 minutes** before applying the necessary fix.

Further updates will follow as soon as we have confirmed results..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:53:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We are pleased to confirm that the issue affecting AMS-1 has been fully **identified and resolved**.

A special thanks goes to **Lorenzo from DeluxHost**, who collaborated actively with our team throughout the investigation and resolution process.  
His direct support at the datacenter allowed us to apply the fix immediately and restore full stability across the infrastructure.

Thank you all for your patience during this incident.  
All systems are now operating normally..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:31:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  &lt;https://www.cloudflarestatus.com/incidents/8gmgl950y3h7&gt;.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:14:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We have some problem with the Main Server of our infrastructure AMS-1.  
  
We are investigating about the issue.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 18 Nov 2025 08:14:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/incident/cmi4arllb01thho4ayltop2eo</link>
  <guid>https://enderdevelopment.instatus.com/incident/cmi4arllb01thho4ayltop2eo</guid>
</item>

<item>
  <title>EndAI Scheduled Maintenance Underway</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 26 minutes

    Affected Components: EndAI
    Oct 30, 19:49:00 GMT+0 - Identified - We’re currently performing a planned update to deploy key stability enhancements and improve overall system performance.

**What to expect during this maintenance:**

* Temporary service interruptions may occur.
* Responses may be delayed or unavailable for a short period.

**After the update:**  
EndAI will resume normal operation automatically—no action is needed on your part. Full functionality should be restored within a few minutes once the maintenance is complete.

Thank you for your patience and support as we work to make EndAI faster, more reliable, and better for everyone! Oct 30, 19:49:01 GMT+0 - Identified - Maintenance is now in progress Oct 30, 21:15:30 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 26 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:49:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We’re currently performing a planned update to deploy key stability enhancements and improve overall system performance.

**What to expect during this maintenance:**

* Temporary service interruptions may occur.
* Responses may be delayed or unavailable for a short period.

**After the update:**  
EndAI will resume normal operation automatically—no action is needed on your part. Full functionality should be restored within a few minutes once the maintenance is complete.

Thank you for your patience and support as we work to make EndAI faster, more reliable, and better for everyone!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:49:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:15:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 30 Oct 2025 19:49:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/maintenance/cmhdu7shq00nrfoswigkyangw</link>
  <guid>https://enderdevelopment.instatus.com/maintenance/cmhdu7shq00nrfoswigkyangw</guid>
</item>

<item>
  <title>Fast Reboot on Free Bot Service</title>
  <description>
    Type: Maintenance
    Duration: 10 minutes

    Affected Components: Host Free Bot
    Oct 3, 12:55:01 GMT+0 - Identified - Maintenance is now in progress Oct 3, 12:55:00 GMT+0 - Identified - We are performing a quick reboot of our Free Bot Service infrastructure to apply critical stability improvements and optimize system performance.

**Impact:**  
During this brief maintenance window:

* All bots on the free plan will be temporarily offline.
* Bots will not respond to messages or commands.

**Post-Maintenance:**  
Once the reboot is complete, all bots will automatically restart. No action is required from you—just allow a few minutes for services to fully recover and resume normal operation.

We appreciate your patience and understanding as we work to deliver a faster, more reliable experience. Thank you for using our service! Oct 3, 13:05:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:55:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:55:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are performing a quick reboot of our Free Bot Service infrastructure to apply critical stability improvements and optimize system performance.

**Impact:**  
During this brief maintenance window:

* All bots on the free plan will be temporarily offline.
* Bots will not respond to messages or commands.

**Post-Maintenance:**  
Once the reboot is complete, all bots will automatically restart. No action is required from you—just allow a few minutes for services to fully recover and resume normal operation.

We appreciate your patience and understanding as we work to deliver a faster, more reliable experience. Thank you for using our service!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:05:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 3 Oct 2025 12:55:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/maintenance/cmgauhey90469y78c3y214iyo</link>
  <guid>https://enderdevelopment.instatus.com/maintenance/cmgauhey90469y78c3y214iyo</guid>
</item>

<item>
  <title>Network Upgrade</title>
  <description>
    Type: Incident
    Duration: 26 minutes

    Affected Components: Official Site, , Host Free Bot, , , Server AMS-3, Server AMS-1 [Main], Server AMS-2, 
EnderDevelopment - Official Site → 
EnderDevelopment - Services → 
Network - Server →
    Sep 15, 21:08:41 GMT+0 - Investigating - DeluxHost is performing a Network Upgrade, this can impact our system. Sep 15, 21:13:28 GMT+0 - Identified - The server AMS-3 of Host Free Bot is working fine.  
  
We stay to wait the work of AMS-1 &amp; AMS-2 Sep 15, 21:34:44 GMT+0 - Resolved - All is working fine. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 26 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:08:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  DeluxHost is performing a Network Upgrade, this can impact our system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:13:28&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The server AMS-3 of Host Free Bot is working fine.  
  
We stay to wait the work of AMS-1 &amp; AMS-2.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:34:44&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  All is working fine..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 15 Sep 2025 21:08:41 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/incident/cmflm8v2j00co129pytxgfstr</link>
  <guid>https://enderdevelopment.instatus.com/incident/cmflm8v2j00co129pytxgfstr</guid>
</item>

<item>
  <title>Migrating Free Bot Host Node</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Host Free Bot
    Sep 4, 01:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 4, 03:00:00 GMT+0 - Completed - Maintenance has completed successfully Sep 4, 01:00:00 GMT+0 - Identified - We will be performing a scheduled migration of our free hosting infrastructure to a new node. This upgrade is necessary to improve performance, stability, and future scalability.

**Impact:**

During the maintenance window:

* **All bots hosted on our free plan will be temporarily offline.**
* Bots will be unresponsive and will not process messages.

**Post-Maintenance:**

Once the migration is complete, **all bots will be automatically restarted**. No action is required on your part. Please allow a few minutes for all services to fully restore.

We apologize for any inconvenience this necessary maintenance may cause. We are committed to providing a more robust and reliable service.

Thank you for your understanding. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We will be performing a scheduled migration of our free hosting infrastructure to a new node. This upgrade is necessary to improve performance, stability, and future scalability.

**Impact:**

During the maintenance window:

* **All bots hosted on our free plan will be temporarily offline.**
* Bots will be unresponsive and will not process messages.

**Post-Maintenance:**

Once the migration is complete, **all bots will be automatically restarted**. No action is required on your part. Please allow a few minutes for all services to fully restore.

We apologize for any inconvenience this necessary maintenance may cause. We are committed to providing a more robust and reliable service.

Thank you for your understanding..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 4 Sep 2025 01:00:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/maintenance/cmf4ot99f001t8wquurzmf4wg</link>
  <guid>https://enderdevelopment.instatus.com/maintenance/cmf4ot99f001t8wquurzmf4wg</guid>
</item>

<item>
  <title>Dashboard / Billing Emergency Upgrade</title>
  <description>
    Type: Maintenance
    Duration: 22 hours and 26 minutes

    
    Aug 16, 23:41:03 GMT+0 - Completed - The maintenance has been successfully completed, and **all services are now fully operational**.

After an intense 24/7 investigation, the root cause was identified: a **corrupted backup file** that had been created during an overlapping system operation. This led to a critical file being silently overwritten with malformed data, which in turn caused the billing system to serve unexpected content and behave unpredictably.

Thanks to a deep forensic analysis, the corrupted file was isolated and replaced with a clean version. The entire Client Area environment has since been verified, optimized, and hardened to prevent similar issues in the future.

**What we’ve done:**

* Replaced the corrupted theme file
* Cleared and regenerated caches safely
* Verified integrity of all core files
* Improved backup procedures (now performed on quiescent systems)
* The current backup contains all data up to August 13, 2025\. Any customers, invoices, or orders placed after that date will need to be flagged and re-entered.

We sincerely thank you for your patience and understanding during this challenging period.

Thank you for trusting **EnderDevelopment**.  
Stay tuned for upcoming improvements and new features. Aug 16, 01:15:00 GMT+0 - Identified - We are currently performing **emergency maintenance and optimization** on the Customer Area to resolve lingering instability and improve long-term performance.

Following the recent full restoration of our core systems, we are taking this opportunity — despite the unfortunate timing — to proactively rebuild and upgrade the Customer Area infrastructure. This includes:

* Deep system cleanup and performance tuning
* Application of critical security patches and updates
* Implementation of previously announced feature enhancements
* Database optimization to prevent future inconsistencies

While this means temporary unavailability, the intervention will result in a faster, more reliable, and secure experience for all users.

Thank you for your understanding and continued trust in EnderDevelopment. Aug 16, 01:15:01 GMT+0 - Identified - Maintenance is now in progress 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 22 hours and 26 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:41:03&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The maintenance has been successfully completed, and **all services are now fully operational**.

After an intense 24/7 investigation, the root cause was identified: a **corrupted backup file** that had been created during an overlapping system operation. This led to a critical file being silently overwritten with malformed data, which in turn caused the billing system to serve unexpected content and behave unpredictably.

Thanks to a deep forensic analysis, the corrupted file was isolated and replaced with a clean version. The entire Client Area environment has since been verified, optimized, and hardened to prevent similar issues in the future.

**What we’ve done:**

* Replaced the corrupted theme file
* Cleared and regenerated caches safely
* Verified integrity of all core files
* Improved backup procedures (now performed on quiescent systems)
* The current backup contains all data up to August 13, 2025\. Any customers, invoices, or orders placed after that date will need to be flagged and re-entered.

We sincerely thank you for your patience and understanding during this challenging period.

Thank you for trusting **EnderDevelopment**.  
Stay tuned for upcoming improvements and new features..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:15:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are currently performing **emergency maintenance and optimization** on the Customer Area to resolve lingering instability and improve long-term performance.

Following the recent full restoration of our core systems, we are taking this opportunity — despite the unfortunate timing — to proactively rebuild and upgrade the Customer Area infrastructure. This includes:

* Deep system cleanup and performance tuning
* Application of critical security patches and updates
* Implementation of previously announced feature enhancements
* Database optimization to prevent future inconsistencies

While this means temporary unavailability, the intervention will result in a faster, more reliable, and secure experience for all users.

Thank you for your understanding and continued trust in EnderDevelopment..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:15:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 16 Aug 2025 01:15:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/maintenance/cmedkeu580003juje9s305stq</link>
  <guid>https://enderdevelopment.instatus.com/maintenance/cmedkeu580003juje9s305stq</guid>
</item>

<item>
  <title>Large Scale Issue</title>
  <description>
    Type: Incident
    Duration: 8 hours and 12 minutes

    Affected Components: Server AMS-1 [Main], Official Site, , 
EnderDevelopment - Official Site →
    Aug 15, 16:59:14 GMT+0 - Investigating - We are currently investigating this incident. Aug 15, 17:43:49 GMT+0 - Investigating - We are currently investigating an issue causing instability in our services. Currently, the symptoms appear to be related to multiple factors, including:

\- Network system anomalies

\- Infrastructure stability fluctuations

\- Intermittent configuration issues and corrupt databases

The technical team is fully engaged and analyzing all affected components to identify the root cause and restore stable operation as quickly as possible. Aug 15, 20:10:20 GMT+0 - Identified - After thorough investigation, we have identified severe infrastructure-level corruption and irreparable data inconsistencies affecting the **Main AMS-1** server. Despite recovery attempts, the integrity of critical system components and databases cannot be restored reliably.

As a result, **we have made the decision to perform a full reinstallation of the server** to ensure long-term stability and data consistency.

This process will require:

\- Complete OS and service reconfiguration

\- Manual restoration from a verified backup dated **yesterday**

\- Extended downtime, expected to last **several more hours**

We sincerely apologize for the prolonged disruption. This action is necessary to prevent further instability and to rebuild the system on a fully healthy foundation.

Our team is working around the clock to complete the restoration and bring services back online as quickly and safely as possible. We will provide another update as soon as the system is operational.

Thank you for your patience and understanding. Aug 15, 21:33:48 GMT+0 - Identified - We have started the manual restoration from yesterday&#039;s backup on the rebuilt Main AMS-1 server. Our team is working at full capacity to minimize downtime and ensure a stable recovery.

Services are expected to be fully restored within the next **hour**. We sincerely apologize for the inconvenience and thank you for your patience. Aug 16, 00:08:01 GMT+0 - Monitoring - We are pleased to report that we have successfully restored approximately 90% of our systems, and all restored components appear to be functioning as expected. Our team is actively monitoring the systems to ensure ongoing stability and performance.

However, we are still experiencing significant issues with the customer area, which remain unresolved. Our technical team is prioritizing these problems and working diligently to address them as quickly as possible.

We will continue to provide updates as we make further progress. Thank you for your patience and understanding during this time. Aug 16, 01:11:39 GMT+0 - Resolved - We are pleased to announce that all critical systems have now been fully restored and are operating normally. The majority of services, including website access, backend operations, and support platforms, are confirmed stable and performing as expected.

However, the **Customer Area** remains temporarily offline.

We understand this may cause some inconvenience, but this proactive step is essential to ensure a more robust, scalable, and secure experience moving forward.

Our team will provide a follow-up update with an estimated time of completion for the Customer Area restoration. 

CEO of EnderDevelopment 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:59:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:43:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an issue causing instability in our services. Currently, the symptoms appear to be related to multiple factors, including:

\- Network system anomalies

\- Infrastructure stability fluctuations

\- Intermittent configuration issues and corrupt databases

The technical team is fully engaged and analyzing all affected components to identify the root cause and restore stable operation as quickly as possible..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:10:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  After thorough investigation, we have identified severe infrastructure-level corruption and irreparable data inconsistencies affecting the **Main AMS-1** server. Despite recovery attempts, the integrity of critical system components and databases cannot be restored reliably.

As a result, **we have made the decision to perform a full reinstallation of the server** to ensure long-term stability and data consistency.

This process will require:

\- Complete OS and service reconfiguration

\- Manual restoration from a verified backup dated **yesterday**

\- Extended downtime, expected to last **several more hours**

We sincerely apologize for the prolonged disruption. This action is necessary to prevent further instability and to rebuild the system on a fully healthy foundation.

Our team is working around the clock to complete the restoration and bring services back online as quickly and safely as possible. We will provide another update as soon as the system is operational.

Thank you for your patience and understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:33:48&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have started the manual restoration from yesterday&#039;s backup on the rebuilt Main AMS-1 server. Our team is working at full capacity to minimize downtime and ensure a stable recovery.

Services are expected to be fully restored within the next **hour**. We sincerely apologize for the inconvenience and thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:08:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We are pleased to report that we have successfully restored approximately 90% of our systems, and all restored components appear to be functioning as expected. Our team is actively monitoring the systems to ensure ongoing stability and performance.

However, we are still experiencing significant issues with the customer area, which remain unresolved. Our technical team is prioritizing these problems and working diligently to address them as quickly as possible.

We will continue to provide updates as we make further progress. Thank you for your patience and understanding during this time..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:11:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We are pleased to announce that all critical systems have now been fully restored and are operating normally. The majority of services, including website access, backend operations, and support platforms, are confirmed stable and performing as expected.

However, the **Customer Area** remains temporarily offline.

We understand this may cause some inconvenience, but this proactive step is essential to ensure a more robust, scalable, and secure experience moving forward.

Our team will provide a follow-up update with an estimated time of completion for the Customer Area restoration. 

CEO of EnderDevelopment.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 15 Aug 2025 16:59:14 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/incident/cmed2p47x00115txzv5kvcc3p</link>
  <guid>https://enderdevelopment.instatus.com/incident/cmed2p47x00115txzv5kvcc3p</guid>
</item>

<item>
  <title>Network Upgrade</title>
  <description>
    Type: Maintenance
    Duration: 10 minutes

    Affected Components: Server AMS-2, Server AMS-1 [Main], Official Site
    Aug 3, 15:25:01 GMT+0 - Identified - Maintenance is now in progress Aug 3, 15:35:00 GMT+0 - Completed - Maintenance has completed successfully Aug 3, 15:25:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time for upgrade performance and security on our network 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:25:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:35:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:25:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for a scheduled maintenance during that time for upgrade performance and security on our network.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 3 Aug 2025 15:25:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/maintenance/cmdvu26ga00a0x90owj3kwy2p</link>
  <guid>https://enderdevelopment.instatus.com/maintenance/cmdvu26ga00a0x90owj3kwy2p</guid>
</item>

<item>
  <title>Rolling Update in Progress – Dashboard 3.0 Live</title>
  <description>
    Type: Maintenance
    Duration: 4 days and 4 hours

    
    Aug 2, 22:20:00 GMT+0 - Identified - The ED 3.0 upgrade is now live for the dashboard! After 2 months of backend &amp; frontend updates, we&#039;re finally rolling out the **completely redesigned Dashboard v3.0** — new layout, fresh ED-themed design, added sections, and improved performance.  
  
⚠️ This update includes multiple rapid patches. **Temporary bugs or performance issues may occur.**  
Please report any problems immediately.

Thank you for your patience! Aug 2, 22:20:01 GMT+0 - Identified - Maintenance is now in progress Aug 7, 02:20:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 days and 4 hours</p>
    
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The ED 3.0 upgrade is now live for the dashboard! After 2 months of backend &amp; frontend updates, we&#039;re finally rolling out the **completely redesigned Dashboard v3.0** — new layout, fresh ED-themed design, added sections, and improved performance.  
  
⚠️ This update includes multiple rapid patches. **Temporary bugs or performance issues may occur.**  
Please report any problems immediately.

Thank you for your patience!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:20:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 2 Aug 2025 22:20:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/maintenance/cmduteupq004ovq8vck8wriyh</link>
  <guid>https://enderdevelopment.instatus.com/maintenance/cmduteupq004ovq8vck8wriyh</guid>
</item>

<item>
  <title>Dashboard Major Update</title>
  <description>
    Type: Maintenance
    Duration: 2 days, 12 hours and 4 minutes

    
    Jul 2, 10:00:00 GMT+0 - Identified - We are pleased to inform you that we’ll be performing scheduled maintenance over the next few days to significantly improve our Dashboard (Client Area). This update will include major enhancements to the UI/UX design, performance, usability, as well as bug fixes and other improvements.

During this period, any requests related to invoices or support tickets will be handled manually via the ticketing system.

We appreciate your patience and understanding while we work to bring you a better and more efficient experience.

Thank you for your continued support! Jul 6, 11:45:17 GMT+0 - Identified - Dear customers,

We would like to inform you that, due to some unexpected technical issues during the implementation of the new version of the dashboard, we are forced to extend maintenance until Tuesday, 8 July at 2:00 AM.

We apologise for the inconvenience and thank you for your patience. This is an important update that requires the utmost precision and commitment to ensure the best possible service.

We greatly appreciate your understanding and cooperation. Jul 8, 23:49:23 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 days, 12 hours and 4 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are pleased to inform you that we’ll be performing scheduled maintenance over the next few days to significantly improve our Dashboard (Client Area). This update will include major enhancements to the UI/UX design, performance, usability, as well as bug fixes and other improvements.

During this period, any requests related to invoices or support tickets will be handled manually via the ticketing system.

We appreciate your patience and understanding while we work to bring you a better and more efficient experience.

Thank you for your continued support!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:45:17&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Dear customers,

We would like to inform you that, due to some unexpected technical issues during the implementation of the new version of the dashboard, we are forced to extend maintenance until Tuesday, 8 July at 2:00 AM.

We apologise for the inconvenience and thank you for your patience. This is an important update that requires the utmost precision and commitment to ensure the best possible service.

We greatly appreciate your understanding and cooperation..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:49:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 2 Jul 2025 10:00:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/maintenance/cmclrtffu00163ku1ax2gkr0u</link>
  <guid>https://enderdevelopment.instatus.com/maintenance/cmclrtffu00163ku1ax2gkr0u</guid>
</item>

<item>
  <title>Performance Improvements &amp; Update our system</title>
  <description>
    Type: Maintenance
    Duration: 10 minutes

    Affected Components: Official Site, , Server AMS-1 [Main], 
EnderDevelopment - Official Site →
    Jul 1, 16:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time for Performance Improvements &amp; Update our system. Jul 1, 16:10:00 GMT+0 - Completed - Maintenance has completed successfully Jul 1, 16:00:01 GMT+0 - Identified - Maintenance is now in progress 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for a scheduled maintenance during that time for Performance Improvements &amp; Update our system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:10:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 1 Jul 2025 16:00:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/maintenance/cmckprd0w0007hvh04u7gre3y</link>
  <guid>https://enderdevelopment.instatus.com/maintenance/cmckprd0w0007hvh04u7gre3y</guid>
</item>

<item>
  <title>Mail delivery system update</title>
  <description>
    Type: Maintenance
    Duration: 35 minutes

    
    Jun 29, 19:54:01 GMT+0 - Identified - Maintenance is now in progress Jun 29, 20:28:48 GMT+0 - Completed - Maintenance has completed successfully. Jun 29, 20:16:43 GMT+0 - Identified - We had some issues during the implementation.

This could mean that the maintenance will last longer than expected.

We apologize for the inconvenience Jun 29, 19:54:00 GMT+0 - Identified - We are planning for a scheduled maintenance for update e improve the mail delivery system during that time. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 35 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:54:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:28:48&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:16:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We had some issues during the implementation.

This could mean that the maintenance will last longer than expected.

We apologize for the inconvenience.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:54:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for a scheduled maintenance for update e improve the mail delivery system during that time..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 29 Jun 2025 19:54:00 +0000</pubDate>
  <link>https://enderdevelopment.instatus.com/maintenance/cmci395hm0005fc5mdwqzs5yc</link>
  <guid>https://enderdevelopment.instatus.com/maintenance/cmci395hm0005fc5mdwqzs5yc</guid>
</item>

  </channel>
  </rss>