<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:nde-status.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://nde-status.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://nde-status.instatus.com/history.atom"/>
  <title>Nde-Code&#039;s systems status Status - Incident history</title>
  <updated>2026-07-18T19:36:10.701+00:00</updated>
  <author>
    <name>Nde-Code&#039;s systems status</name>
  </author>
  
<entry>
  <id>tag:nde-status.instatus.com,2005:Incident/cmrqrp0si002p0koe2wy6c5bd</id>
  <published>2026-07-18T19:36:10.701+00:00</published>
  <updated>2026-07-18T20:32:37.960+00:00</updated>
  <link rel="alternate" type="text/html" href="https://nde-status.instatus.com/incident/cmrqrp0si002p0koe2wy6c5bd"/>
  <title>Performance degradation mitigated.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Main website</p>
    <p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>20:32:37</var> GMT+0</small><br /><strong>Postmortem</strong> -
  On 18/07/2026 at 21:36, I was notified of a performance issue affecting my website. The report clearly showed that the first byte took far too long to respond (over 10,000 ms). The next cron check was also impacted by the degradation, with the first byte again taking too long to respond. It was only after the third cron check that the incident was resolved. The affected regions were Europe and Canada, suggesting it was likely a networking issue with the CDN provider..</p>
<p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>19:56:05</var> GMT+0</small><br /><strong>Resolved</strong> -
  The degradation affecting my website has been mitigated. A root cause analysis is currently underway, and I will share further details as soon as they are available..</p>
<p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>19:36:11</var> GMT+0</small><br /><strong>Investigating</strong> -
  I am investigating a reported degradation affecting my website&#039;s response time. The next update will be provided after the next scheduled cron check..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:nde-status.instatus.com,2005:Incident/cmrlbpo4q02gmf8o2xs2z9qno</id>
  <published>2026-07-15T00:09:56.218+00:00</published>
  <updated>2026-07-15T06:25:23.889+00:00</updated>
  <link rel="alternate" type="text/html" href="https://nde-status.instatus.com/incident/cmrlbpo4q02gmf8o2xs2z9qno"/>
  <title>Performance degradation mitigated.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Main website</p>
    <p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>06:25:23</var> GMT+0</small><br /><strong>Postmortem</strong> -
  On July 15 at 02:09:56, I received an incident about my website&#039;s response time exceeding the configured limit. After a quick review, it became clear that the main issue was in Europe, where the TLS response time averaged over 500ms. Combined with other factors, the total response time exceeded 1000ms, resulting in a degradation report. The incident was automatically closed ten minutes later, after the next cron check..</p>
<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>00:19:54</var> GMT+0</small><br /><strong>Resolved</strong> -
  The degradation affecting my website has been mitigated. A root cause analysis is currently underway, and I will share further details as soon as they are available..</p>
<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>00:09:56</var> GMT+0</small><br /><strong>Investigating</strong> -
  I am investigating a reported degradation affecting my website&#039;s response time. The next update will be provided after the next scheduled cron check..</p>

        ]]>
  </content>
</entry>

</feed>