<?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>Blockbax Status - Incident history</title>
    <link>https://status.blockbax.com</link>
    <description>Blockbax</description>
    <pubDate>Thu, 24 Sep 2026 19:15:00 +0000</pubDate>
    
<item>
  <title>Scheduled maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Mobile app, HTTP, Web app, CoAP, MQTT
    Sep 24, 20:15:00 GMT+0 - Completed - Maintenance has completed successfully Sep 24, 19:15:01 GMT+0 - Identified - Maintenance is now in progress Sep 24, 16:03:36 GMT+0 - Identified - We will perform scheduled maintenance on our infrastructure. For short periods within this window you may experience brief delays and/or intermittent errors. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>20:15:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>19:15:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>16:03:36</var> GMT+0</small><br><strong>Identified</strong> -
  We will perform scheduled maintenance on our infrastructure. For short periods within this window you may experience brief delays and/or intermittent errors..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 24 Sep 2026 19:15:00 +0000</pubDate>
  <link>https://status.blockbax.com/maintenance/cmufq1kz8020613qnp9ra29or</link>
  <guid>https://status.blockbax.com/maintenance/cmufq1kz8020613qnp9ra29or</guid>
</item>

<item>
  <title>Scheduled maintenance</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Mobile app, HTTP, Web app
    Sep 15, 18:00:00 GMT+0 - Completed - Maintenance has completed successfully Sep 15, 16:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 4, 08:51:29 GMT+0 - Identified - We will perform scheduled maintenance on our infrastructure. For short periods within this window you may experience brief delays and/or intermittent errors. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> , , </p>
    <p><small>Sep <var data-var='date'> 15</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Sep <var data-var='date'> 15</var>, <var data-var='time'>16:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>08:51:29</var> GMT+0</small><br><strong>Identified</strong> -
  We will perform scheduled maintenance on our infrastructure. For short periods within this window you may experience brief delays and/or intermittent errors..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 15 Sep 2026 16:00:00 +0000</pubDate>
  <link>https://status.blockbax.com/maintenance/cmtmpsu7l09ti13qj1gbibysd</link>
  <guid>https://status.blockbax.com/maintenance/cmtmpsu7l09ti13qj1gbibysd</guid>
</item>

<item>
  <title>Problems with MQTT outbound connectors</title>
  <description>
    Type: Incident
    Duration: 4 hours and 59 minutes

    Affected Components: MQTT
    Aug 19, 12:14:00 GMT+0 - Resolved - The issue has been resolved. The root cause was a pre-existing bug that is triggered during deployments, which surfaced after a recent release. 

We have fixed the bug and MQTT outbound connectors are functioning properly again. All retained values have been restored and no data was lost. Aug 19, 07:15:00 GMT+0 - Investigating - We&#039;re investigating an issue with MQTT outbound connectors for subscribing to property updates where the latest retained property value is not always available. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 59 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 19</var>, <var data-var='time'>12:14:00</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue has been resolved. The root cause was a pre-existing bug that is triggered during deployments, which surfaced after a recent release. 

We have fixed the bug and MQTT outbound connectors are functioning properly again. All retained values have been restored and no data was lost..</p>
<p><small>Aug <var data-var='date'> 19</var>, <var data-var='time'>07:15:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;re investigating an issue with MQTT outbound connectors for subscribing to property updates where the latest retained property value is not always available..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 19 Aug 2026 07:15:00 +0000</pubDate>
  <link>https://status.blockbax.com/incident/cmt01qgkd01z321mzbpss4vc4</link>
  <guid>https://status.blockbax.com/incident/cmt01qgkd01z321mzbpss4vc4</guid>
</item>

<item>
  <title>Elevated error rates</title>
  <description>
    Type: Incident
    Duration: 13 minutes

    Affected Components: HTTP
    Aug 11, 08:09:00 GMT+0 - Resolved - Error rates have returned to normal and HTTP measurement ingestion should work as expected again.

We determined the root cause to be a recent change that was deployed resulting in intermittent errors for around 13 minutes, causing 404 errors to user requests. We rolled back the change and error rates returned to normal. Aug 11, 07:56:00 GMT+0 - Investigating - We&#039;re investigating elevated error rates for HTTP measurement ingestion. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 13 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 11</var>, <var data-var='time'>08:09:00</var> GMT+0</small><br><strong>Resolved</strong> -
  Error rates have returned to normal and HTTP measurement ingestion should work as expected again.

We determined the root cause to be a recent change that was deployed resulting in intermittent errors for around 13 minutes, causing 404 errors to user requests. We rolled back the change and error rates returned to normal..</p>
<p><small>Aug <var data-var='date'> 11</var>, <var data-var='time'>07:56:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;re investigating elevated error rates for HTTP measurement ingestion..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 11 Aug 2026 07:56:00 +0000</pubDate>
  <link>https://status.blockbax.com/incident/cmsoellob07i20rlo5xkily1r</link>
  <guid>https://status.blockbax.com/incident/cmsoellob07i20rlo5xkily1r</guid>
</item>

<item>
  <title>Delayed processing measurements</title>
  <description>
    Type: Incident
    Duration: 32 minutes

    Affected Components: Mobile app, HTTP, Web app, CoAP, MQTT
    May 26, 10:09:38 GMT+0 - Resolved - Processing delays have been resolved, and all systems are now operating normally. May 26, 09:37:40 GMT+0 - Investigating - We are currently behind in the processing of measurements, we are investigating the incident and will follow-up when we have an update. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 32 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>10:09:38</var> GMT+0</small><br><strong>Resolved</strong> -
  Processing delays have been resolved, and all systems are now operating normally..</p>
<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>09:37:40</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently behind in the processing of measurements, we are investigating the incident and will follow-up when we have an update..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 26 May 2026 09:37:40 +0000</pubDate>
  <link>https://status.blockbax.com/incident/cmpmfz7q913t6qkouh1trgnep</link>
  <guid>https://status.blockbax.com/incident/cmpmfz7q913t6qkouh1trgnep</guid>
</item>

<item>
  <title>Delayed processing of events and alarms</title>
  <description>
    Type: Incident
    Duration: 2 hours and 49 minutes

    Affected Components: Mobile app, HTTP, Web app
    Apr 29, 12:19:23 GMT+0 - Resolved - Processing delays have been resolved, and all systems are now operating normally. Apr 29, 10:21:00 GMT+0 - Monitoring - We implemented a fix and the delay in processing is decreasing. We will continue monitoring the progress. Apr 29, 09:30:00 GMT+0 - Investigating - We are currently behind in the processing of events and alarms, we are investigating the incident and will follow-up when we have an update. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 49 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    <p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>12:19:23</var> GMT+0</small><br><strong>Resolved</strong> -
  Processing delays have been resolved, and all systems are now operating normally..</p>
<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>10:21:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and the delay in processing is decreasing. We will continue monitoring the progress..</p>
<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>09:30:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently behind in the processing of events and alarms, we are investigating the incident and will follow-up when we have an update..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 29 Apr 2026 09:30:00 +0000</pubDate>
  <link>https://status.blockbax.com/incident/cmojvm53a00995oyzvcfvga1w</link>
  <guid>https://status.blockbax.com/incident/cmojvm53a00995oyzvcfvga1w</guid>
</item>

<item>
  <title>Delayed processing of events and alarms</title>
  <description>
    Type: Incident
    Duration: 3 hours

    Affected Components: Mobile app, HTTP, Web app
    Mar 30, 08:00:00 GMT+0 - Resolved - Processing delays have been resolved, and all systems are now operating normally. Mar 30, 05:00:00 GMT+0 - Investigating - We are currently behind in the processing of events and alarms, we are investigating the incident and will follow-up when we have an update. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> , , </p>
    <p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Resolved</strong> -
  Processing delays have been resolved, and all systems are now operating normally..</p>
<p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently behind in the processing of events and alarms, we are investigating the incident and will follow-up when we have an update..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 30 Mar 2026 05:00:00 +0000</pubDate>
  <link>https://status.blockbax.com/incident/cmncz17t308eo13at3fpjfzbr</link>
  <guid>https://status.blockbax.com/incident/cmncz17t308eo13at3fpjfzbr</guid>
</item>

<item>
  <title>Scheduled maintenance</title>
  <description>
    Type: Maintenance
    Duration: 30 minutes

    Affected Components: Mobile app, CoAP, HTTP, Web app, MQTT
    Mar 30, 05:30:00 GMT+0 - Completed - Maintenance has completed successfully Mar 30, 05:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 30, 05:00:00 GMT+0 - Identified - We are planning for scheduled maintenance on our infrastructure and for a few minutes intermittent errors can occur during this time window. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    <p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>05:30:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>05:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for scheduled maintenance on our infrastructure and for a few minutes intermittent errors can occur during this time window..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 30 Mar 2026 05:00:00 +0000</pubDate>
  <link>https://status.blockbax.com/maintenance/cmn4zxtxn0003cjld7trbu7r4</link>
  <guid>https://status.blockbax.com/maintenance/cmn4zxtxn0003cjld7trbu7r4</guid>
</item>

<item>
  <title>Delayed processing of events and alarms</title>
  <description>
    Type: Incident
    Duration: 36 minutes

    Affected Components: , Mobile app, HTTP, Web app, 
Application →
    Oct 27, 13:46:00 GMT+0 - Resolved - Processing delays have been resolved, and all systems are now operating normally. Oct 27, 12:21:00 GMT+0 - Investigating - We are currently behind in the processing of events and alarms, we are investigating the incident and will follow-up when we have an update. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 36 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>13:46:00</var> GMT+0</small><br><strong>Resolved</strong> -
  Processing delays have been resolved, and all systems are now operating normally..</p>
<p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>12:21:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently behind in the processing of events and alarms, we are investigating the incident and will follow-up when we have an update..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 27 Oct 2025 12:21:00 +0000</pubDate>
  <link>https://status.blockbax.com/incident/cmh95nrhj0054hp2ozcfb5p27</link>
  <guid>https://status.blockbax.com/incident/cmh95nrhj0054hp2ozcfb5p27</guid>
</item>

<item>
  <title>Elevated error rates</title>
  <description>
    Type: Incident
    Duration: 8 minutes

    Affected Components: , , Mobile app, Web app, HTTP, 
Application → 
APIs →
    Jun 12, 13:06:00 GMT+0 - Resolved - Error rates have returned to normal and users should be able to use Blockbax as expected. We determined the cause to be a network disruption resulting in intermittent errors, causing errors on certain requests. Jun 12, 12:58:00 GMT+0 - Investigating - We&#039;re investigating elevated error rates and reports of users seeing error pages. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>13:06:00</var> GMT+0</small><br><strong>Resolved</strong> -
  Error rates have returned to normal and users should be able to use Blockbax as expected. We determined the cause to be a network disruption resulting in intermittent errors, causing errors on certain requests..</p>
<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>12:58:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;re investigating elevated error rates and reports of users seeing error pages..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 12 Jun 2025 12:58:00 +0000</pubDate>
  <link>https://status.blockbax.com/incident/cmbtefhl20003vdwshxvt8174</link>
  <guid>https://status.blockbax.com/incident/cmbtefhl20003vdwshxvt8174</guid>
</item>

<item>
  <title>Duplicate processing</title>
  <description>
    Type: Incident
    Duration: 6 days and 10 hours

    Affected Components: Mobile app, Web app, HTTP, CoAP, MQTT
    May 20, 15:21:00 GMT+0 - Resolved - We have manually closed all instances of events that were duplicated and not properly closed. Please be aware of the potential incidental duplicates during the affected period (May 19, between 15:11 and 17:07), and contact us if you have any questions. May 19, 15:07:00 GMT+0 - Monitoring - We identified some events generated during the affected period (May 19, between 15:11 and 17:07) are duplicate. We are investigating how to best resolve this. May 19, 13:11:00 GMT+0 - Investigating - We had an incident where, due to a maintenance procedure with unintended side-effects, we had incidental duplicate processing of data. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days and 10 hours</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    <p><small>May <var data-var='date'> 20</var>, <var data-var='time'>15:21:00</var> GMT+0</small><br><strong>Resolved</strong> -
  We have manually closed all instances of events that were duplicated and not properly closed. Please be aware of the potential incidental duplicates during the affected period (May 19, between 15:11 and 17:07), and contact us if you have any questions..</p>
<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>15:07:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  We identified some events generated during the affected period (May 19, between 15:11 and 17:07) are duplicate. We are investigating how to best resolve this..</p>
<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>13:11:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We had an incident where, due to a maintenance procedure with unintended side-effects, we had incidental duplicate processing of data..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 19 May 2025 13:11:00 +0000</pubDate>
  <link>https://status.blockbax.com/incident/cmaw9hn7r000bsx2g5vhv8ac5</link>
  <guid>https://status.blockbax.com/incident/cmaw9hn7r000bsx2g5vhv8ac5</guid>
</item>

<item>
  <title>Errors in dashboard widgets</title>
  <description>
    Type: Incident
    Duration: 4 minutes

    Affected Components: Web app
    Apr 3, 10:01:00 GMT+0 - Resolved - Errors in dashboard widgets are resolved and users should be able to use Blockbax as expected.

We determined the root cause to be a recent change that was deployed causing errors for certain dashboard widgets (API requests and mobile app were unaffected). We rolled back the change and error rates returned to normal. Apr 3, 09:57:00 GMT+0 - Investigating - We&#039;re investigating reports of users seeing errors in dashboard widgets. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>10:01:00</var> GMT+0</small><br><strong>Resolved</strong> -
  Errors in dashboard widgets are resolved and users should be able to use Blockbax as expected.

We determined the root cause to be a recent change that was deployed causing errors for certain dashboard widgets (API requests and mobile app were unaffected). We rolled back the change and error rates returned to normal..</p>
<p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>09:57:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;re investigating reports of users seeing errors in dashboard widgets..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 3 Apr 2025 09:57:00 +0000</pubDate>
  <link>https://status.blockbax.com/incident/cm917b5fj00ek2f5j5lhj86fg</link>
  <guid>https://status.blockbax.com/incident/cm917b5fj00ek2f5j5lhj86fg</guid>
</item>

<item>
  <title>Scheduled maintenance</title>
  <description>
    Type: Maintenance
    Duration: 50 minutes

    Affected Components: HTTP, Web app, Mobile app
    Mar 10, 17:50:00 GMT+0 - Completed - Maintenance has completed successfully Mar 10, 17:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 10, 17:00:00 GMT+0 - Identified - We are planning for scheduled maintenance on our infrastructure and for a few minutes intermittent read errors can occur during this time window. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 50 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    <p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>17:50:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>17:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for scheduled maintenance on our infrastructure and for a few minutes intermittent read errors can occur during this time window..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 10 Mar 2025 17:00:00 +0000</pubDate>
  <link>https://status.blockbax.com/maintenance/cm7w4yeje000w76ngb44uxos3</link>
  <guid>https://status.blockbax.com/maintenance/cm7w4yeje000w76ngb44uxos3</guid>
</item>

<item>
  <title>Scheduled maintenance</title>
  <description>
    Type: Maintenance
    Duration: 5 days

    Affected Components: HTTP, Web app, Mobile app
    Feb 24, 19:00:00 GMT+0 - Completed - Maintenance has completed successfully Feb 24, 17:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 24, 17:00:00 GMT+0 - Identified - We are planning for scheduled maintenance on our infrastructure and for some periods during this time window intermittent errors can occur. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 days</p>
    <p><strong>Affected Components:</strong> , , </p>
    <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>17:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for scheduled maintenance on our infrastructure and for some periods during this time window intermittent errors can occur..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 24 Feb 2025 17:00:00 +0000</pubDate>
  <link>https://status.blockbax.com/maintenance/cm7eu0gwg0042m4rec9prox3u</link>
  <guid>https://status.blockbax.com/maintenance/cm7eu0gwg0042m4rec9prox3u</guid>
</item>

<item>
  <title>Scheduled maintenance</title>
  <description>
    Type: Maintenance
    Duration: 15 hours

    Affected Components: HTTP, CoAP, MQTT, Web app, Mobile app
    Feb 24, 03:15:00 GMT+0 - Completed - Maintenance has completed successfully Feb 24, 03:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 24, 03:00:00 GMT+0 - Identified - We are planning for scheduled maintenance on our infrastructure and for a few minutes intermittent errors can occur during this time window. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 15 hours</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>03:15:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>03:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for scheduled maintenance on our infrastructure and for a few minutes intermittent errors can occur during this time window..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 24 Feb 2025 03:00:00 +0000</pubDate>
  <link>https://status.blockbax.com/maintenance/cm7ektttf000qycv27yr015dn</link>
  <guid>https://status.blockbax.com/maintenance/cm7ektttf000qycv27yr015dn</guid>
</item>

<item>
  <title>Dashboards can not be loaded</title>
  <description>
    Type: Incident
    Duration: 8 minutes

    Affected Components: Web app
    Aug 20, 08:02:00 GMT+0 - Resolved - The issue has been resolved. We determined the root cause to be a recent change that was deployed, causing dashboards to show a version mismatch error for users that reloaded the web app (first login or after refresh). We fixed the version mismatch and dashboards are functioning properly again. Aug 20, 07:54:00 GMT+0 - Investigating - We&#039;re investigating issues due to which dashboards can not be loaded. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 20</var>, <var data-var='time'>08:02:00</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue has been resolved. We determined the root cause to be a recent change that was deployed, causing dashboards to show a version mismatch error for users that reloaded the web app (first login or after refresh). We fixed the version mismatch and dashboards are functioning properly again..</p>
<p><small>Aug <var data-var='date'> 20</var>, <var data-var='time'>07:54:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;re investigating issues due to which dashboards can not be loaded..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 20 Aug 2024 07:54:00 +0000</pubDate>
  <link>https://status.blockbax.com/incident/cm0251bwe001fo3vvhq9afzlp</link>
  <guid>https://status.blockbax.com/incident/cm0251bwe001fo3vvhq9afzlp</guid>
</item>

<item>
  <title>Scheduled maintenance</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: HTTP, CoAP, MQTT, Web app, Mobile app
    Jul 11, 19:00:00 GMT+0 - Completed - Maintenance has completed successfully Jul 11, 17:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 11, 17:00:00 GMT+0 - Identified - We are planning for scheduled maintenance on our infrastructure and small delays and intermittent errors can occur. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    <p><small>Jul <var data-var='date'> 11</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Jul <var data-var='date'> 11</var>, <var data-var='time'>17:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jul <var data-var='date'> 11</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for scheduled maintenance on our infrastructure and small delays and intermittent errors can occur..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 11 Jul 2024 17:00:00 +0000</pubDate>
  <link>https://status.blockbax.com/maintenance/clycnxqx21064532yon45zx61d7</link>
  <guid>https://status.blockbax.com/maintenance/clycnxqx21064532yon45zx61d7</guid>
</item>

<item>
  <title>Scheduled maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Web app, Mobile app
    Apr 10, 20:35:00 GMT+0 - Completed - Maintenance has completed successfully. Apr 10, 19:45:00 GMT+0 - Identified - We are planning for a scheduled maintenance on our infrastructure and during a short time in this maintenance window small delays and web app errors can occur (APIs are unaffected). Apr 10, 19:30:00 GMT+0 - Identified - We are planning for a scheduled maintenance on our infrastructure and during a short time in this maintenance window small delays and read errors can occur (sending measurements and regular updates are unaffected). 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>20:35:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>19:45:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for a scheduled maintenance on our infrastructure and during a short time in this maintenance window small delays and web app errors can occur (APIs are unaffected)..</p>
<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>19:30:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for a scheduled maintenance on our infrastructure and during a short time in this maintenance window small delays and read errors can occur (sending measurements and regular updates are unaffected)..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 10 Apr 2024 19:30:00 +0000</pubDate>
  <link>https://status.blockbax.com/maintenance/cluu8ab5667128j3ochv7u6pc9</link>
  <guid>https://status.blockbax.com/maintenance/cluu8ab5667128j3ochv7u6pc9</guid>
</item>

<item>
  <title>Elevated error rates</title>
  <description>
    Type: Incident
    Duration: 8 minutes

    Affected Components: Mobile app, Web app
    Apr 5, 13:15:00 GMT+0 - Resolved - Error rates have returned to normal and users should be able to use Blockbax as expected.

We determined the root cause to be a recent change that was deployed resulting in intermittent errors, causing errors on certain web app requests (API requests were unaffected). We rolled back the change and error rates returned to normal. Apr 5, 13:07:00 GMT+0 - Investigating - We&#039;re investigating elevated error rates and reports of users seeing error pages. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Apr <var data-var='date'> 5</var>, <var data-var='time'>13:15:00</var> GMT+0</small><br><strong>Resolved</strong> -
  Error rates have returned to normal and users should be able to use Blockbax as expected.

We determined the root cause to be a recent change that was deployed resulting in intermittent errors, causing errors on certain web app requests (API requests were unaffected). We rolled back the change and error rates returned to normal..</p>
<p><small>Apr <var data-var='date'> 5</var>, <var data-var='time'>13:07:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;re investigating elevated error rates and reports of users seeing error pages..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 5 Apr 2024 13:07:00 +0000</pubDate>
  <link>https://status.blockbax.com/incident/clump5i5p5531bcmxr56kkg03</link>
  <guid>https://status.blockbax.com/incident/clump5i5p5531bcmxr56kkg03</guid>
</item>

<item>
  <title>Elevated error rates</title>
  <description>
    Type: Incident
    Duration: 12 hours

    Affected Components: HTTP, CoAP, Web app, Mobile app, MQTT
    Feb 1, 13:16:00 GMT+0 - Resolved - Error rates have returned to normal and users should be able to use Blockbax as expected.

We determined the root cause to be a recent change that was deployed resulting in intermittent errors, causing errors on certain read requests (ingesting measurements and updating data was unaffected). We rolled back the change and error rates returned to normal. Feb 1, 13:04:00 GMT+0 - Investigating - We&#039;re investigating elevated error rates and reports of users seeing error pages. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 12 hours</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    <p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>13:16:00</var> GMT+0</small><br><strong>Resolved</strong> -
  Error rates have returned to normal and users should be able to use Blockbax as expected.

We determined the root cause to be a recent change that was deployed resulting in intermittent errors, causing errors on certain read requests (ingesting measurements and updating data was unaffected). We rolled back the change and error rates returned to normal..</p>
<p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>13:04:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;re investigating elevated error rates and reports of users seeing error pages..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 1 Feb 2024 13:04:00 +0000</pubDate>
  <link>https://status.blockbax.com/incident/cls38nyru147132balm6vi31jbe</link>
  <guid>https://status.blockbax.com/incident/cls38nyru147132balm6vi31jbe</guid>
</item>

<item>
  <title>Elevated error rates</title>
  <description>
    Type: Incident
    Duration: 2 days and 15 hours

    Affected Components: HTTP, Web app, CoAP, Mobile app, MQTT
    Jan 10, 11:06:00 GMT+0 - Resolved - Error rates have returned to normal and users should be able to use Blockbax as expected. 

We determined the root cause to be a recent change that was deployed resulting in intermittent errors for around 5 minutes, causing 500 errors to user requests. We rolled back the change and error rates returned to normal. Jan 10, 10:03:00 GMT+0 - Investigating - We&#039;re investigating elevated error rates and reports of users seeing error pages.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days and 15 hours</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    <p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>11:06:00</var> GMT+0</small><br><strong>Resolved</strong> -
  Error rates have returned to normal and users should be able to use Blockbax as expected. 

We determined the root cause to be a recent change that was deployed resulting in intermittent errors for around 5 minutes, causing 500 errors to user requests. We rolled back the change and error rates returned to normal..</p>
<p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>10:03:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;re investigating elevated error rates and reports of users seeing error pages. .</p>
]]>
  </content:encoded>
  <pubDate>Wed, 10 Jan 2024 10:03:00 +0000</pubDate>
  <link>https://status.blockbax.com/incident/clr7pzkzy24608b9nlxlub3sqo</link>
  <guid>https://status.blockbax.com/incident/clr7pzkzy24608b9nlxlub3sqo</guid>
</item>

<item>
  <title>Scheduled maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 day and 6 hours

    Affected Components: HTTP, Web app, Mobile app
    Oct 4, 18:30:00 GMT+0 - Completed - Maintenance has completed successfully. Oct 4, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 4, 18:00:00 GMT+0 - Identified - We are planning for a major scheduled maintenance on our infrastructure and during a short time in this maintenance window delays in processing can be expected together with some incidental read errors (ingesting measurements and updating data is unaffected). 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 day and 6 hours</p>
    <p><strong>Affected Components:</strong> , , </p>
    <p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>18:30:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for a major scheduled maintenance on our infrastructure and during a short time in this maintenance window delays in processing can be expected together with some incidental read errors (ingesting measurements and updating data is unaffected)..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 4 Oct 2023 18:00:00 +0000</pubDate>
  <link>https://status.blockbax.com/maintenance/clnahbufc4189bkoeifgg8mkp</link>
  <guid>https://status.blockbax.com/maintenance/clnahbufc4189bkoeifgg8mkp</guid>
</item>

<item>
  <title>Scheduled maintenance</title>
  <description>
    Type: Maintenance
    Duration: 9 hours

    Affected Components: HTTP, Mobile app, Web app
    Sep 11, 21:45:00 GMT+0 - Completed - Maintenance has completed successfully Sep 11, 19:30:00 GMT+0 - Identified - Maintenance is now in progress Sep 11, 18:00:00 GMT+0 - Identified - We are planning for a major scheduled maintenance on our infrastructure and during a short time delays in processing can be expected together with some incidental read errors (ingesting measurements and updating data is unaffected). 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 9 hours</p>
    <p><strong>Affected Components:</strong> , , </p>
    <p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>21:45:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>19:30:00</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for a major scheduled maintenance on our infrastructure and during a short time delays in processing can be expected together with some incidental read errors (ingesting measurements and updating data is unaffected)..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 11 Sep 2023 21:45:00 +0000</pubDate>
  <link>https://status.blockbax.com/maintenance/clmalp32a9284bglwqfnnlrkt</link>
  <guid>https://status.blockbax.com/maintenance/clmalp32a9284bglwqfnnlrkt</guid>
</item>

<item>
  <title>Scheduled maintenance</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Mobile app, HTTP, MQTT, CoAP, Web app
    Jan 26, 19:00:00 GMT+0 - Completed - Maintenance has completed successfully Jan 26, 17:00:01 GMT+0 - Identified - Maintenance is now in progress Jan 26, 17:00:00 GMT+0 - Identified - We are planning for a major scheduled maintenance on our infrastructure and during a short time logging in and/or updating data is not possible (ingesting measurements is unaffected). 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    <p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>17:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for a major scheduled maintenance on our infrastructure and during a short time logging in and/or updating data is not possible (ingesting measurements is unaffected)..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 26 Jan 2023 17:00:00 +0000</pubDate>
  <link>https://status.blockbax.com/maintenance/cld8z2mp230287bdop9v2ksm94</link>
  <guid>https://status.blockbax.com/maintenance/cld8z2mp230287bdop9v2ksm94</guid>
</item>

<item>
  <title>Problems loading web app</title>
  <description>
    Type: Incident
    Duration: 1 day and 21 hours

    Affected Components: Web app
    Jan 20, 14:30:00 GMT+0 - Resolved - Error rates have returned to normal and users should be able to use Blockbax as expected. 

We determined the root cause to be a recent change that was deployed by our third-party content delivery network (CloudFront) resulting in intermittent DNS resolve errors, causing 502 errors to user requests. AWS has rolled back the change and error rates returned to normal. Jan 20, 13:45:00 GMT+0 - Investigating - We&#039;re investigating elevated error rates and reports of users seeing error pages.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day and 21 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jan <var data-var='date'> 20</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br><strong>Resolved</strong> -
  Error rates have returned to normal and users should be able to use Blockbax as expected. 

We determined the root cause to be a recent change that was deployed by our third-party content delivery network (CloudFront) resulting in intermittent DNS resolve errors, causing 502 errors to user requests. AWS has rolled back the change and error rates returned to normal..</p>
<p><small>Jan <var data-var='date'> 20</var>, <var data-var='time'>13:45:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;re investigating elevated error rates and reports of users seeing error pages. .</p>
]]>
  </content:encoded>
  <pubDate>Fri, 20 Jan 2023 13:45:00 +0000</pubDate>
  <link>https://status.blockbax.com/incident/cld8xl37w183279bcoi5xb4c8x4</link>
  <guid>https://status.blockbax.com/incident/cld8xl37w183279bcoi5xb4c8x4</guid>
</item>

  </channel>
  </rss>