<?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>Concordium Status - Incident history</title>
    <link>https://status.mainnet.concordium.com</link>
    <description>Concordium</description>
    <pubDate>Tue, 10 Mar 2026 10:00:00 +0000</pubDate>
    
<item>
  <title>Protocol update 10</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Mainnet
    Mar 10, 11:00:00 GMT+0 - Completed - Maintenance has completed successfully Mar 10, 10:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 10, 10:00:00 GMT+0 - Identified - A protocol update to [protocol version 10](https://proposals.concordium.com/updates/P10.html)[ ](https://proposals.concordium.com/updates/P10.html)is planned to take effect on Mainnet on March 10, 2026.  
New node software compliant with the protocol update (version 10.0.5 is released for Linux, Windows and MacOS, available [here](https://docs.concordium.com/en/mainnet/docs/installation/downloads.html#concordium-node-distributions) ([release notes](https://docs.concordium.com/en/mainnet/docs/release-notes/release-notes-lp.html#mainnet)).  
**Node runners must upgrade their nodes to version 10.0.5 before the new protocol takes effect.** Nodes running earlier versions will stop processing new blocks at that point. 
  </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>Mar <var data-var='date'> 10</var>, <var data-var='time'>11:00: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'>10: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'>10:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  A protocol update to [protocol version 10](https://proposals.concordium.com/updates/P10.html)[ ](https://proposals.concordium.com/updates/P10.html)is planned to take effect on Mainnet on March 10, 2026.  
New node software compliant with the protocol update (version 10.0.5 is released for Linux, Windows and MacOS, available [here](https://docs.concordium.com/en/mainnet/docs/installation/downloads.html#concordium-node-distributions) ([release notes](https://docs.concordium.com/en/mainnet/docs/release-notes/release-notes-lp.html#mainnet)).  
**Node runners must upgrade their nodes to version 10.0.5 before the new protocol takes effect.** Nodes running earlier versions will stop processing new blocks at that point..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 10 Mar 2026 10:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/cmmde6gdq0005ebstm3g8y3jm</link>
  <guid>https://status.mainnet.concordium.com/maintenance/cmmde6gdq0005ebstm3g8y3jm</guid>
</item>

<item>
  <title>During update of wallet backend the list of transactions will not receive the latest transactions</title>
  <description>
    Type: Maintenance
    Duration: 6 minutes

    Affected Components: Wallet Backend
    Jan 23, 07:09:59 GMT+0 - Completed - Maintenance has completed successfully. Jan 23, 07:03:45 GMT+0 - Identified - Maintenance is now in progress. Jan 23, 07:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time.

The update is not expected to otherwise impact the functions of the wallets. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jan <var data-var='date'> 23</var>, <var data-var='time'>07:09:59</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Jan <var data-var='date'> 23</var>, <var data-var='time'>07:03:45</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress..</p>
<p><small>Jan <var data-var='date'> 23</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time.

The update is not expected to otherwise impact the functions of the wallets..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 23 Jan 2026 07:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/cmkpu17m0005k11y62u0sx67f</link>
  <guid>https://status.mainnet.concordium.com/maintenance/cmkpu17m0005k11y62u0sx67f</guid>
</item>

<item>
  <title>Protocol update 9</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Mainnet
    Sep 23, 11:00:00 GMT+0 - Completed - Maintenance has completed successfully Sep 23, 10:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 23, 10:00:00 GMT+0 - Identified - A protocol update to [protocol ](https://proposals.concordium.com/updates/P9.html)[version ](https://proposals.concordium.com/updates/P9.html)[9](https://proposals.concordium.com/updates/P9.html) is planned to take effect on mainnet on September 23rd, 2025.

New node software compliant with the protocol update (version 9.0.7) is released for Linux, Windows and MacOS, available [here](https://docs.concordium.com/en/mainnet/docs/installation/downloads.html#concordium-node-distributions) ([release notes](https://docs.concordium.com/en/mainnet/docs/release-notes/release-notes-lp.html#mainnet)).

**Node runners must upgrade their nodes to version 9.0.7 before the new protocol takes effect.** Nodes running earlier versions will stop processing new blocks at that point. 
  </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'> 23</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Sep <var data-var='date'> 23</var>, <var data-var='time'>10:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 23</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  A protocol update to [protocol ](https://proposals.concordium.com/updates/P9.html)[version ](https://proposals.concordium.com/updates/P9.html)[9](https://proposals.concordium.com/updates/P9.html) is planned to take effect on mainnet on September 23rd, 2025.

New node software compliant with the protocol update (version 9.0.7) is released for Linux, Windows and MacOS, available [here](https://docs.concordium.com/en/mainnet/docs/installation/downloads.html#concordium-node-distributions) ([release notes](https://docs.concordium.com/en/mainnet/docs/release-notes/release-notes-lp.html#mainnet)).

**Node runners must upgrade their nodes to version 9.0.7 before the new protocol takes effect.** Nodes running earlier versions will stop processing new blocks at that point..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 23 Sep 2025 10:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/cmf17j8kf000vy8l9pti9kymd</link>
  <guid>https://status.mainnet.concordium.com/maintenance/cmf17j8kf000vy8l9pti9kymd</guid>
</item>

<item>
  <title>Protocol update 8</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Mainnet
    Mar 17, 11:00:00 GMT+0 - Completed - Maintenance has completed successfully Mar 17, 10:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 17, 10:00:00 GMT+0 - Identified - A protocol update to [protocol version 8](https://proposals.concordium.com/updates/P8.html) is planned to take effect on mainnet on March 17th, 2025.

New node software compliant with the protocol update (version 8.0.3) is released for Linux, Windows and MacOS, available [here](https://docs.concordium.com/en/mainnet/docs/installation/downloads.html).

**Node runners must upgrade their nodes to version 8.0.3 before the new protocol takes effect.** Nodes running earlier versions will stop processing new blocks at that point. 
  </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>Mar <var data-var='date'> 17</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Mar <var data-var='date'> 17</var>, <var data-var='time'>10:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Mar <var data-var='date'> 17</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  A protocol update to [protocol version 8](https://proposals.concordium.com/updates/P8.html) is planned to take effect on mainnet on March 17th, 2025.

New node software compliant with the protocol update (version 8.0.3) is released for Linux, Windows and MacOS, available [here](https://docs.concordium.com/en/mainnet/docs/installation/downloads.html).

**Node runners must upgrade their nodes to version 8.0.3 before the new protocol takes effect.** Nodes running earlier versions will stop processing new blocks at that point..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 17 Mar 2025 10:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/cm7t3ioq3000pcnqwlww8ogup</link>
  <guid>https://status.mainnet.concordium.com/maintenance/cm7t3ioq3000pcnqwlww8ogup</guid>
</item>

<item>
  <title>CCDScan is not currently processing new blocks.</title>
  <description>
    Type: Incident
    Duration: 2 hours and 18 minutes

    Affected Components: CCD Scan
    Oct 30, 14:21:17 GMT+0 - Resolved - This incident has been resolved. Oct 30, 14:08:26 GMT+0 - Identified - We are continuing to work on a fix for this incident. Oct 30, 12:03:43 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>14:21:17</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>14:08:26</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>12:03:43</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 30 Oct 2024 12:03:43 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/cm2vtvx8q0013l12fku3ruk0g</link>
  <guid>https://status.mainnet.concordium.com/incident/cm2vtvx8q0013l12fku3ruk0g</guid>
</item>

<item>
  <title>Protocol Update on Mainnet</title>
  <description>
    Type: Maintenance
    Duration: 30 minutes

    Affected Components: Mainnet
    Oct 30, 10:30:00 GMT+0 - Completed - Maintenance has completed successfully Oct 30, 10:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 30, 10:00:00 GMT+0 - Identified - A protocol update to protocol version 7, which includes improvements to smart contract functionality and staking behavior, is planned to take effect on mainnet on October 30th, 2024.

New node software compliant with the protocol update is released for Linux, Windows, and MacOS here \[1\].

_Node runners must upgrade their nodes to version 7.0.5 before the new protocol takes effect._ Nodes running earlier versions will stop processing new blocks at that point.

For more details on the protocol update, see concordium-update-proposals \[2\].

\[1} &lt;https://developer.concordium.software/en/mainnet/net/installation/downloads.html#concordium-node-distributions&gt;

\[2\] &lt;https://proposals.concordium.software/updates/P7.html&gt; 
  </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>Oct <var data-var='date'> 30</var>, <var data-var='time'>10:30:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>10:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  A protocol update to protocol version 7, which includes improvements to smart contract functionality and staking behavior, is planned to take effect on mainnet on October 30th, 2024.

New node software compliant with the protocol update is released for Linux, Windows, and MacOS here \[1\].

_Node runners must upgrade their nodes to version 7.0.5 before the new protocol takes effect._ Nodes running earlier versions will stop processing new blocks at that point.

For more details on the protocol update, see concordium-update-proposals \[2\].

\[1} &lt;https://developer.concordium.software/en/mainnet/net/installation/downloads.html#concordium-node-distributions&gt;

\[2\] &lt;https://proposals.concordium.software/updates/P7.html&gt;.</p>
]]>
  </content:encoded>
  <pubDate>Wed, 30 Oct 2024 10:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/cm2emvksm0001suevitjtl59v</link>
  <guid>https://status.mainnet.concordium.com/maintenance/cm2emvksm0001suevitjtl59v</guid>
</item>

<item>
  <title>Performance degradation</title>
  <description>
    Type: Incident
    Duration: 1 hour and 26 minutes

    Affected Components: Mainnet
    Oct 15, 12:11:00 GMT+0 - Resolved - On the 15th of October 2024, we observed significant performance degradation between 12:45 CEST and 14:11 CEST. This issue was caused by 26.85% of the stake going offline during this period.   
Afterward, normal performance was fully restored. Oct 15, 10:45:00 GMT+0 - Identified - On the 15th of October 2024, we observed significant performance degradation between 12:45 CEST and 14:11 CEST. This issue was caused by 26.85% of the stake going offline during this period.   
Afterward, normal performance was fully restored. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 26 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>12:11:00</var> GMT+0</small><br><strong>Resolved</strong> -
  On the 15th of October 2024, we observed significant performance degradation between 12:45 CEST and 14:11 CEST. This issue was caused by 26.85% of the stake going offline during this period.   
Afterward, normal performance was fully restored..</p>
<p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>10:45:00</var> GMT+0</small><br><strong>Identified</strong> -
  On the 15th of October 2024, we observed significant performance degradation between 12:45 CEST and 14:11 CEST. This issue was caused by 26.85% of the stake going offline during this period.   
Afterward, normal performance was fully restored..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 15 Oct 2024 10:45:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/cm2ah64ks0001fpt9mxrbx0si</link>
  <guid>https://status.mainnet.concordium.com/incident/cm2ah64ks0001fpt9mxrbx0si</guid>
</item>

<item>
  <title>Increase transaction activity</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Mainnet
    Oct 9, 13:00:00 GMT+0 - Completed - Maintenance has completed successfully Oct 9, 11:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 9, 11:00:00 GMT+0 - Identified - We are expecting a mild increase in transaction activity on the 9th of October.   
No impact or degradation of service expected.   
We will monitor the blockchain closely 
  </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>Oct <var data-var='date'> 9</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>11:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 9</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are expecting a mild increase in transaction activity on the 9th of October.   
No impact or degradation of service expected.   
We will monitor the blockchain closely.</p>
]]>
  </content:encoded>
  <pubDate>Wed, 9 Oct 2024 11:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/cm20ihf78002h6ndgq7g6eah7</link>
  <guid>https://status.mainnet.concordium.com/maintenance/cm20ihf78002h6ndgq7g6eah7</guid>
</item>

<item>
  <title>Mainnet block production stopped</title>
  <description>
    Type: Incident
    Duration: 9 hours and 25 minutes

    Affected Components: Identity Providers, Mainnet, Wallet Backend, CCD Scan
    Jun 16, 18:24:46 GMT+0 - Resolved - This incident has been identified and resolved. We will work in the next day for releasing a patch and avoid this issue in the future. We are sorry for the inconvinience. Jun 16, 15:38:16 GMT+0 - Investigating - While our engineers work on finding the root cause of the issue, please proceed with rebooting your node as it might help with restoring the normal operations of the blockchain  Jun 16, 15:13:17 GMT+0 - Investigating - Investigation of the issue proceeds. Our engineers are working in identifying the root cause. Jun 16, 09:00:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 hours and 25 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>18:24:46</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been identified and resolved. We will work in the next day for releasing a patch and avoid this issue in the future. We are sorry for the inconvinience..</p>
<p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>15:38:16</var> GMT+0</small><br><strong>Investigating</strong> -
  While our engineers work on finding the root cause of the issue, please proceed with rebooting your node as it might help with restoring the normal operations of the blockchain .</p>
<p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>15:13:17</var> GMT+0</small><br><strong>Investigating</strong> -
  Investigation of the issue proceeds. Our engineers are working in identifying the root cause..</p>
<p><small>Jun <var data-var='date'> 16</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 16 Jun 2024 09:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/clxhlm1v6386903c1ofjt18h0pt</link>
  <guid>https://status.mainnet.concordium.com/incident/clxhlm1v6386903c1ofjt18h0pt</guid>
</item>

<item>
  <title>Ccd Scan degraded performance</title>
  <description>
    Type: Incident
    

    Affected Components: CCD Scan
    Feb 16, 11:18:31 GMT+0 - Resolved - The incident has been resolved. The service is fully restored 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>11:18:31</var> GMT+0</small><br><strong>Resolved</strong> -
  The incident has been resolved. The service is fully restored.</p>
]]>
  </content:encoded>
  <pubDate>Fri, 16 Feb 2024 11:18:31 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/clsok3uhp218639bfogygxyms1o</link>
  <guid>https://status.mainnet.concordium.com/incident/clsok3uhp218639bfogygxyms1o</guid>
</item>

<item>
  <title>JSON-RPC proxy will be disabled</title>
  <description>
    Type: Maintenance
    Duration: 5 hours

    
    Nov 27, 14:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 27, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 27, 09:00:00 GMT+0 - Identified - In preparation for the shutdown of the JSON-RPC service (json-rpc.mainnet.concordium.software) on December 04 at 10:00 CET we will temporarily disable the JSON-RPC service on **mainnet** on November 27 from 10:00-15:00 CET.

No other services will be affected. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 hours</p>
    
    <p><small>Nov <var data-var='date'> 27</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 27</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Nov <var data-var='date'> 27</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  In preparation for the shutdown of the JSON-RPC service (json-rpc.mainnet.concordium.software) on December 04 at 10:00 CET we will temporarily disable the JSON-RPC service on **mainnet** on November 27 from 10:00-15:00 CET.

No other services will be affected..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 27 Nov 2023 09:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/clp10ur6l13510ban9r4lxjzt8</link>
  <guid>https://status.mainnet.concordium.com/maintenance/clp10ur6l13510ban9r4lxjzt8</guid>
</item>

<item>
  <title>JSON-RPC proxy will be disabled</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    
    Nov 20, 11:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 20, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 20, 09:00:00 GMT+0 - Identified - In preparation for the shutdown of the JSON-RPC service (json-rpc.mainnet.concordium.software) on December 04 at 10:00 CET we will temporarily disable the JSON-RPC service on **mainnet** on November 20 from 10:00-12:00 CET.

No other services will be affected. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    
    <p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  In preparation for the shutdown of the JSON-RPC service (json-rpc.mainnet.concordium.software) on December 04 at 10:00 CET we will temporarily disable the JSON-RPC service on **mainnet** on November 20 from 10:00-12:00 CET.

No other services will be affected..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 20 Nov 2023 09:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/clp10szwz9821b1n9yzg91egy</link>
  <guid>https://status.mainnet.concordium.com/maintenance/clp10szwz9821b1n9yzg91egy</guid>
</item>

<item>
  <title>Protocol Update on Mainnet</title>
  <description>
    Type: Maintenance
    Duration: 18 hours and 46 minutes

    Affected Components: Mainnet
    Sep 25, 09:18:45 GMT+0 - Completed - Protocol 6 is in effect with genesis block 423ecc20a7a1731c94ab66c721a62e1a0ff34f601ddf7e7562e7bdd792e02b63.

Please note that pay day for rewards is now at approximately 09:00 UTC. Sep 25, 09:00:00 GMT+0 - Identified - A protocol update to implement the new Concordium BFT consensus protocol and to extends smart contract functionality will take effect on mainnet on September 25, 2023.

New node software compliant with the protocol update is released for Linux, Windows, and MacOS [here](https://developer.concordium.software/en/mainnet/net/installation/downloads.html#concordium-node-distributions). New versions of concordium-client, cargo-concordium, smart contract libraries and wallets have previously been released as well.

**Node runners must upgrade their nodes before the new protocol takes effect.** Old nodes will stop processing new blocks at that point.

For more details on the protocol update, see [concordium-update-proposals](https://proposals.concordium.software/updates/P6.html). 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 18 hours and 46 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 25</var>, <var data-var='time'>09:18:45</var> GMT+0</small><br><strong>Completed</strong> -
  Protocol 6 is in effect with genesis block 423ecc20a7a1731c94ab66c721a62e1a0ff34f601ddf7e7562e7bdd792e02b63.

Please note that pay day for rewards is now at approximately 09:00 UTC..</p>
<p><small>Sep <var data-var='date'> 25</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  A protocol update to implement the new Concordium BFT consensus protocol and to extends smart contract functionality will take effect on mainnet on September 25, 2023.

New node software compliant with the protocol update is released for Linux, Windows, and MacOS [here](https://developer.concordium.software/en/mainnet/net/installation/downloads.html#concordium-node-distributions). New versions of concordium-client, cargo-concordium, smart contract libraries and wallets have previously been released as well.

**Node runners must upgrade their nodes before the new protocol takes effect.** Old nodes will stop processing new blocks at that point.

For more details on the protocol update, see [concordium-update-proposals](https://proposals.concordium.software/updates/P6.html)..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 25 Sep 2023 09:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/clmenp2hu126963byn0babwe1rc</link>
  <guid>https://status.mainnet.concordium.com/maintenance/clmenp2hu126963byn0babwe1rc</guid>
</item>

<item>
  <title>Mysome.id will be temporarily down due to maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 12 minutes

    
    Sep 22, 09:40:45 GMT+0 - Completed - Maintenance has completed successfully. Sep 22, 08:28:36 GMT+0 - Identified - Maintenance is now in progress. Sep 22, 08:15:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 12 minutes</p>
    
    <p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>09:40:45</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>08:28:36</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress..</p>
<p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>08:15:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 22 Sep 2023 08:15:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/clmuardfz327608b5ocq79gwecq</link>
  <guid>https://status.mainnet.concordium.com/maintenance/clmuardfz327608b5ocq79gwecq</guid>
</item>

<item>
  <title>Wallet backed infrastructure maintenance</title>
  <description>
    Type: Maintenance
    Duration: 42 minutes

    Affected Components: Wallet Backend
    Sep 21, 13:41:48 GMT+0 - Completed - Maintenance has completed successfully. Sep 21, 13:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 21, 13:00:00 GMT+0 - Identified - We are performing some infrastructure changes in the wallet underlying platform. We do not expect any impact or service degradation during the process.
 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 42 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 21</var>, <var data-var='time'>13:41:48</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Sep <var data-var='date'> 21</var>, <var data-var='time'>13:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 21</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are performing some infrastructure changes in the wallet underlying platform. We do not expect any impact or service degradation during the process.
.</p>
]]>
  </content:encoded>
  <pubDate>Thu, 21 Sep 2023 13:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/clmt5uwp734531b8n3dowze9se</link>
  <guid>https://status.mainnet.concordium.com/maintenance/clmt5uwp734531b8n3dowze9se</guid>
</item>

<item>
  <title>Network dashboard will temporarily only show a subset of nodes</title>
  <description>
    Type: Maintenance
    Duration: 23 minutes

    Affected Components: CCD Scan
    Sep 19, 08:58:29 GMT+0 - Completed - Maintenance has completed successfully. Sep 19, 08:35:17 GMT+0 - Identified - Maintenance is now in progress. Sep 19, 08:30:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 23 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>08:58:29</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>08:35:17</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress..</p>
<p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>08:30:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 19 Sep 2023 08:30:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/clmq0nvkn65251bmmz3xswal3s</link>
  <guid>https://status.mainnet.concordium.com/maintenance/clmq0nvkn65251bmmz3xswal3s</guid>
</item>

<item>
  <title>Identity issuance with Danish MitID currently unavailable</title>
  <description>
    Type: Incident
    Duration: 6 days, 20 hours and 58 minutes

    Affected Components: Identity Providers
    Aug 23, 09:00:11 GMT+0 - Resolved - This incident has been resolved. Aug 16, 12:02:39 GMT+0 - Investigating - Identity issuance with the Danish eID solution MitID via our identity provider DTS is currently not working. DTS is informed.

Identities can still be issued with traditional ID documents. Note that to create identities with Danish ID documents, you will need to choose Notabene instead of DTS. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 20 hours and 58 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 23</var>, <var data-var='time'>09:00:11</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 16</var>, <var data-var='time'>12:02:39</var> GMT+0</small><br><strong>Investigating</strong> -
  Identity issuance with the Danish eID solution MitID via our identity provider DTS is currently not working. DTS is informed.

Identities can still be issued with traditional ID documents. Note that to create identities with Danish ID documents, you will need to choose Notabene instead of DTS..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 16 Aug 2023 12:02:39 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/clldonvh17915b0ome495s53l</link>
  <guid>https://status.mainnet.concordium.com/incident/clldonvh17915b0ome495s53l</guid>
</item>

<item>
  <title>Security update</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Wallet Backend, CCD Scan
    May 8, 08:30:00 GMT+0 - Completed - Maintenance has completed successfully May 8, 07:30:01 GMT+0 - Identified - Maintenance is now in progress May 8, 07:30:00 GMT+0 - Identified - We are implementing a security update in our wallet backend and network dashboard services. The procedure should not have any impact on the services. 
  </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>May <var data-var='date'> 8</var>, <var data-var='time'>08:30:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>07:30:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>07:30:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are implementing a security update in our wallet backend and network dashboard services. The procedure should not have any impact on the services..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 8 May 2023 07:30:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/clhehyvfs2557481dmzb1gtp99t</link>
  <guid>https://status.mainnet.concordium.com/maintenance/clhehyvfs2557481dmzb1gtp99t</guid>
</item>

<item>
  <title>Identity creation with Notabene is temporarily disabled in all Concordium wallets.</title>
  <description>
    Type: Incident
    Duration: 8 days, 22 hours and 52 minutes

    Affected Components: Identity Providers
    Jun 6, 10:42:48 GMT+0 - Resolved - This incident has been resolved. Identity creation with Notabene works in all Concordium wallets again. Mar 30, 11:51:06 GMT+0 - Investigating - Identity creation with Notabene is temporarily disabled in all Concordium wallets. **Please use our other identity provider DTS to create new identities.**

Existing identities issued by Notabene are still valid and identity and account recovery works for both Notabene and DTS identities. Only creation of new Notabene identities is affected. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 days, 22 hours and 52 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>10:42:48</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved. Identity creation with Notabene works in all Concordium wallets again..</p>
<p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>11:51:06</var> GMT+0</small><br><strong>Investigating</strong> -
  Identity creation with Notabene is temporarily disabled in all Concordium wallets. **Please use our other identity provider DTS to create new identities.**

Existing identities issued by Notabene are still valid and identity and account recovery works for both Notabene and DTS identities. Only creation of new Notabene identities is affected..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 30 Mar 2023 11:51:06 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/clfv21m7n27996igom2w5wg757</link>
  <guid>https://status.mainnet.concordium.com/incident/clfv21m7n27996igom2w5wg757</guid>
</item>

<item>
  <title>Identity creation on an iOS device using Notabene is not possible</title>
  <description>
    Type: Incident
    Duration: 3 days, 23 hours and 12 minutes

    Affected Components: Identity Providers
    Mar 21, 09:55:03 GMT+0 - Resolved - This incident has been resolved. Mar 17, 10:43:21 GMT+0 - Investigating - Issuing a new identity using Notabene is not possible on iPhones at the moment, as our iOS wallets crash after entering the Notabene identity flow.

Please use our other identity provider DTS to issue identities in our iOS wallets. Our other wallets are not affected.

Notabene is investigating the incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 23 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Mar <var data-var='date'> 21</var>, <var data-var='time'>09:55:03</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Mar <var data-var='date'> 17</var>, <var data-var='time'>10:43:21</var> GMT+0</small><br><strong>Investigating</strong> -
  Issuing a new identity using Notabene is not possible on iPhones at the moment, as our iOS wallets crash after entering the Notabene identity flow.

Please use our other identity provider DTS to issue identities in our iOS wallets. Our other wallets are not affected.

Notabene is investigating the incident..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 17 Mar 2023 10:43:21 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/clfcewexy1495286aocauk0fiag</link>
  <guid>https://status.mainnet.concordium.com/incident/clfcewexy1495286aocauk0fiag</guid>
</item>

<item>
  <title>CCDScan stopped processing new data</title>
  <description>
    Type: Incident
    Duration: 2 hours and 24 minutes

    Affected Components: CCD Scan
    Dec 21, 11:03:00 GMT+0 - Resolved - The remaining issue is fixed; the APY values are correctly calculated again. Dec 15, 11:03:00 GMT+0 - Resolved - The issue is resolved. [CCDScan](https://ccdscan.io/) shows up-to-date data again.

Note however that APY values are currently incorrect. We are working on it and expect it to be fixed early next week (week 51). Dec 15, 08:39:23 GMT+0 - Investigating - [CCDScan](https://ccdscan.io/) has stopped displaying new data. It can still be used to view data before December 15, 09:05 CET. For newer data, please use the [mainnet dashboard](https://dashboard.mainnet.concordium.software/) instead.

We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 24 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>11:03:00</var> GMT+0</small><br><strong>Resolved</strong> -
  The remaining issue is fixed; the APY values are correctly calculated again..</p>
<p><small>Dec <var data-var='date'> 15</var>, <var data-var='time'>11:03:00</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue is resolved. [CCDScan](https://ccdscan.io/) shows up-to-date data again.

Note however that APY values are currently incorrect. We are working on it and expect it to be fixed early next week (week 51)..</p>
<p><small>Dec <var data-var='date'> 15</var>, <var data-var='time'>08:39:23</var> GMT+0</small><br><strong>Investigating</strong> -
  [CCDScan](https://ccdscan.io/) has stopped displaying new data. It can still be used to view data before December 15, 09:05 CET. For newer data, please use the [mainnet dashboard](https://dashboard.mainnet.concordium.software/) instead.

We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 15 Dec 2022 08:39:23 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/clbotym6r1106hgor25irpvks</link>
  <guid>https://status.mainnet.concordium.com/incident/clbotym6r1106hgor25irpvks</guid>
</item>

<item>
  <title>Protocol Update on Mainnet</title>
  <description>
    Type: Maintenance
    Duration: 3 minutes

    Affected Components: Mainnet
    Dec 13, 08:08:16 GMT+0 - Completed - Protocol 5 is in effect since block 34e1074da9be14e16b3dd538985732a350ebc1283b5cb060b0cae85021a34e86.

Please note that in the future (from 14 December 2022) pay day for rewards shifts to 09:05 CET instead of 09:00 CET. Dec 13, 08:05:00 GMT+0 - Identified - A protocol update to implement smart contract upgradability and performance improvements will take effect on mainnet on December 13, 2022.

New node software compliant with the protocol update is released for Linux, Windows, and MacOS [here](https://developer.concordium.software/en/mainnet/net/installation/downloads.html#concordium-node-distributions-v5-0-6).

The new node version also fixes a security issue in node version 4. **Therefore, we strongly recommend all nodes to get updated as soon as possible after the node release and latest before the protocol update on December 13.** Old nodes will stop processing new blocks at that point.

For more details on the protocol update, see [concordium-update-proposals](https://proposals.concordium.software/updates/P5.html). The security advisory describing the security issue will be published on December 13. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Dec <var data-var='date'> 13</var>, <var data-var='time'>08:08:16</var> GMT+0</small><br><strong>Completed</strong> -
  Protocol 5 is in effect since block 34e1074da9be14e16b3dd538985732a350ebc1283b5cb060b0cae85021a34e86.

Please note that in the future (from 14 December 2022) pay day for rewards shifts to 09:05 CET instead of 09:00 CET..</p>
<p><small>Dec <var data-var='date'> 13</var>, <var data-var='time'>08:05:00</var> GMT+0</small><br><strong>Identified</strong> -
  A protocol update to implement smart contract upgradability and performance improvements will take effect on mainnet on December 13, 2022.

New node software compliant with the protocol update is released for Linux, Windows, and MacOS [here](https://developer.concordium.software/en/mainnet/net/installation/downloads.html#concordium-node-distributions-v5-0-6).

The new node version also fixes a security issue in node version 4. **Therefore, we strongly recommend all nodes to get updated as soon as possible after the node release and latest before the protocol update on December 13.** Old nodes will stop processing new blocks at that point.

For more details on the protocol update, see [concordium-update-proposals](https://proposals.concordium.software/updates/P5.html). The security advisory describing the security issue will be published on December 13..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 13 Dec 2022 08:05:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/clb21h6y87544hzollgur6jwv</link>
  <guid>https://status.mainnet.concordium.com/maintenance/clb21h6y87544hzollgur6jwv</guid>
</item>

<item>
  <title>Identity provider DTS currently unreachable</title>
  <description>
    Type: Incident
    Duration: 1 hour and 17 minutes

    Affected Components: Identity Providers
    Nov 23, 15:32:53 GMT+0 - Resolved - The identity provider DTS is operational again. Nov 23, 14:15:41 GMT+0 - Investigating - Our identity provider DTS is currently unreachable. We have informed them and they are investigating the incident.

To create new identities, please use Notabene instead. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 17 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 23</var>, <var data-var='time'>15:32:53</var> GMT+0</small><br><strong>Resolved</strong> -
  The identity provider DTS is operational again..</p>
<p><small>Nov <var data-var='date'> 23</var>, <var data-var='time'>14:15:41</var> GMT+0</small><br><strong>Investigating</strong> -
  Our identity provider DTS is currently unreachable. We have informed them and they are investigating the incident.

To create new identities, please use Notabene instead..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 23 Nov 2022 14:15:41 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/clatqad9477713xwn20i1n8ylm</link>
  <guid>https://status.mainnet.concordium.com/incident/clatqad9477713xwn20i1n8ylm</guid>
</item>

<item>
  <title>Minor inconsistent transaction data in wallets</title>
  <description>
    Type: Incident
    Duration: 20 hours and 15 minutes

    Affected Components: Wallet Backend
    Nov 19, 10:44:22 GMT+0 - Resolved - We just resolved the issue! Nov 18, 14:29:57 GMT+0 - Identified - We are continuing to work on a fix for this incident. Nov 18, 14:29:35 GMT+0 - Investigating - We are experiencing some minor inconsistency for the following accounts:
- 3gvrwc2rWqXmjNf1kxD6N1FonmrdGprb6H8Juenud77LKuhGXP
- 35CJPZohio6Ztii2zy1AYzJKvuxbGG44wrBn7hLHiYLoF2nxnh

The wallets might show duplicate transactions in the transaction history overview. 
The blockchain is unaffected.
We are working in fixing the inconsistency.
We expect it will be resolved over the weekend. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 19</var>, <var data-var='time'>10:44:22</var> GMT+0</small><br><strong>Resolved</strong> -
  We just resolved the issue!.</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:29:57</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:29:35</var> GMT+0</small><br><strong>Investigating</strong> -
  We are experiencing some minor inconsistency for the following accounts:
- 3gvrwc2rWqXmjNf1kxD6N1FonmrdGprb6H8Juenud77LKuhGXP
- 35CJPZohio6Ztii2zy1AYzJKvuxbGG44wrBn7hLHiYLoF2nxnh

The wallets might show duplicate transactions in the transaction history overview. 
The blockchain is unaffected.
We are working in fixing the inconsistency.
We expect it will be resolved over the weekend..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 18 Nov 2022 14:29:35 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/clamlkzmj12514i1oktd3z4dtp</link>
  <guid>https://status.mainnet.concordium.com/incident/clamlkzmj12514i1oktd3z4dtp</guid>
</item>

<item>
  <title>Identity creation with Notabene is disabled in the Concordium Wallet for Android</title>
  <description>
    Type: Incident
    Duration: 3 days, 22 hours and 23 minutes

    Affected Components: Identity Providers
    Oct 10, 08:24:29 GMT+0 - Resolved - The issue has been identified and fixed.

Notabene is enabled again, and fully functional. Oct 6, 10:01:41 GMT+0 - Investigating - Our identity provider Notabene is experiencing technical difficulties. It is not possible to create identities with them in the new Concordium Wallet for Android (Concordium - Blockchain Wallet) at the moment. 

Please use the other identity provider DTS instead.

The issue is under investigation. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 22 hours and 23 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>08:24:29</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue has been identified and fixed.

Notabene is enabled again, and fully functional..</p>
<p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>10:01:41</var> GMT+0</small><br><strong>Investigating</strong> -
  Our identity provider Notabene is experiencing technical difficulties. It is not possible to create identities with them in the new Concordium Wallet for Android (Concordium - Blockchain Wallet) at the moment. 

Please use the other identity provider DTS instead.

The issue is under investigation..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 6 Oct 2022 10:01:41 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/cl8ww2tbm2186i3n4c3pl1d5w</link>
  <guid>https://status.mainnet.concordium.com/incident/cl8ww2tbm2186i3n4c3pl1d5w</guid>
</item>

<item>
  <title>Node upgrade</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 23 minutes

    Affected Components: Mainnet
    Aug 1, 14:32:54 GMT+0 - Completed - Maintenance has completed successfully. Aug 1, 13:10:11 GMT+0 - Identified - We are upgrading the Concordium nodes in our infrastructure. No impact expected. Aug 1, 13:10:11 GMT+0 - Identified - We are upgrading the Concordium nodes in our infrastructure. No impact expected. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 23 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 1</var>, <var data-var='time'>14:32:54</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Aug <var data-var='date'> 1</var>, <var data-var='time'>13:10:11</var> GMT+0</small><br><strong>Identified</strong> -
  We are upgrading the Concordium nodes in our infrastructure. No impact expected..</p>
<p><small>Aug <var data-var='date'> 1</var>, <var data-var='time'>13:10:11</var> GMT+0</small><br><strong>Identified</strong> -
  We are upgrading the Concordium nodes in our infrastructure. No impact expected..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 1 Aug 2022 13:10:11 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/cl6arrxda28575wvnderzgovpo</link>
  <guid>https://status.mainnet.concordium.com/maintenance/cl6arrxda28575wvnderzgovpo</guid>
</item>

<item>
  <title>Node upgrade</title>
  <description>
    Type: Maintenance
    Duration: 3 hours

    Affected Components: Mainnet
    Jul 4, 11:00:00 GMT+0 - Completed - Maintenance has completed successfully Jul 4, 11:00:00 GMT+0 - Completed - Maintenance has completed successfully Jul 4, 08:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 4, 08:00:00 GMT+0 - Identified - We are upgrading the Concordium nodes in our infrastructure. No impact expected. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>08:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are upgrading the Concordium nodes in our infrastructure. No impact expected..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 4 Jul 2022 08:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/cl56g9d1u35852l5ocouxirssy</link>
  <guid>https://status.mainnet.concordium.com/maintenance/cl56g9d1u35852l5ocouxirssy</guid>
</item>

<item>
  <title>Migration of supporting services to new backend for transaction data</title>
  <description>
    Type: Maintenance
    Duration: 31 minutes

    Affected Components: Wallet Backend
    Jul 1, 09:30:57 GMT+0 - Completed - Maintenance has completed successfully. Jul 1, 09:22:39 GMT+0 - Identified - Maintenance is now in progress. Jul 1, 09:00:00 GMT+0 - Identified - The switch is not expected to have any observable impact other than wallet proxy being unavailable for a few moments. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 31 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>09:30:57</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>09:22:39</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  The switch is not expected to have any observable impact other than wallet proxy being unavailable for a few moments..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 1 Jul 2022 09:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/cl50stqar15664mnn21feyil4l</link>
  <guid>https://status.mainnet.concordium.com/maintenance/cl50stqar15664mnn21feyil4l</guid>
</item>

<item>
  <title>Protocol update to enable delegation and updated smart contracts</title>
  <description>
    Type: Maintenance
    Duration: 4 minutes

    Affected Components: Mainnet
    Jun 23, 08:03:42 GMT+0 - Completed - The protocol update is effective. Jun 23, 08:00:01 GMT+0 - Identified - Maintenance is now in progress Jun 23, 08:00:01 GMT+0 - Identified - Maintenance is now in progress Jun 23, 08:00:00 GMT+0 - Identified - A protocol update to add support for delegation, baker pools, and updated smart contracts will take effect on mainnet on June 23, 2022.

New node software compliant with the protocol update has already been released for Linux, Windows, and MacOS [here](https://developer.concordium.software/en/mainnet/net/installation/downloads.html#concordium-node-distributions). Node runners **must upgrade** their nodes before the new protocol takes effect. Old nodes will stop processing new blocks at that point.

For more details on the protocol update, see [concordium-update-proposals](https://github.com/Concordium/concordium-update-proposals).

The protocol update on mainnet is preceded by a similar protocol update on testnet effected on June 13, 2022. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>08:03:42</var> GMT+0</small><br><strong>Completed</strong> -
  The protocol update is effective..</p>
<p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>08:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>08:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  A protocol update to add support for delegation, baker pools, and updated smart contracts will take effect on mainnet on June 23, 2022.

New node software compliant with the protocol update has already been released for Linux, Windows, and MacOS [here](https://developer.concordium.software/en/mainnet/net/installation/downloads.html#concordium-node-distributions). Node runners **must upgrade** their nodes before the new protocol takes effect. Old nodes will stop processing new blocks at that point.

For more details on the protocol update, see [concordium-update-proposals](https://github.com/Concordium/concordium-update-proposals).

The protocol update on mainnet is preceded by a similar protocol update on testnet effected on June 13, 2022..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 23 Jun 2022 08:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/cl4grhbqi57729l7ohys9bhhet</link>
  <guid>https://status.mainnet.concordium.com/maintenance/cl4grhbqi57729l7ohys9bhhet</guid>
</item>

<item>
  <title>Node upgrade</title>
  <description>
    Type: Maintenance
    Duration: 5 hours

    Affected Components: Mainnet
    Jun 15, 12:30:00 GMT+0 - Completed - Maintenance has completed successfully Jun 15, 07:30:01 GMT+0 - Identified - Maintenance is now in progress Jun 15, 07:30:01 GMT+0 - Identified - Maintenance is now in progress Jun 15, 07:30:00 GMT+0 - Identified - We are planning the node upgrade in our infrastructure. No impact expected. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>07:30:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>07:30:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>07:30:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning the node upgrade in our infrastructure. No impact expected..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 15 Jun 2022 07:30:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/cl4f9om30595606q0mzudpko98m</link>
  <guid>https://status.mainnet.concordium.com/maintenance/cl4f9om30595606q0mzudpko98m</guid>
</item>

<item>
  <title>Scheduled downtime for identity provider Notabene </title>
  <description>
    Type: Maintenance
    Duration: 15 minutes

    Affected Components: Identity Providers
    Mar 16, 11:15:00 GMT+0 - Completed - Maintenance has completed successfully. Mar 16, 11:00:00 GMT+0 - Identified - Identity provider Notabene will deploy a new infrastructure environment on their side and therefore scheduled an expected downtime of max. 1 hour. 

During this maintenance, identities can be issued with identity provider Digital Trust Solutions. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>11:15:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  Identity provider Notabene will deploy a new infrastructure environment on their side and therefore scheduled an expected downtime of max. 1 hour. 

During this maintenance, identities can be issued with identity provider Digital Trust Solutions..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 16 Mar 2022 11:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/cl0s3dcin276487e4oeiytewvhu</link>
  <guid>https://status.mainnet.concordium.com/maintenance/cl0s3dcin276487e4oeiytewvhu</guid>
</item>

<item>
  <title>Identity provider DTS will be inaccessible</title>
  <description>
    Type: Maintenance
    Duration: 15 minutes

    Affected Components: Identity Providers
    Feb 23, 09:19:43 GMT+0 - Completed - Maintenance has completed successfully. Feb 23, 09:01:00 GMT+0 - Identified - Maintenance is now in progress. Feb 23, 09:00:00 GMT+0 - Identified - Our identity provider Digital Trust Solutions (DTS) plans to perform a maintenance on 23-02-2022 at 10:00 CET. It is expected to take around 15 minutes. During this period, DTS will be inaccessible and no identities can be issued via DTS.

To issue identities, please wait until DTS is accessible again or use our other identity provider Notabene. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>09:19:43</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>09:01:00</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress..</p>
<p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  Our identity provider Digital Trust Solutions (DTS) plans to perform a maintenance on 23-02-2022 at 10:00 CET. It is expected to take around 15 minutes. During this period, DTS will be inaccessible and no identities can be issued via DTS.

To issue identities, please wait until DTS is accessible again or use our other identity provider Notabene..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 23 Feb 2022 09:01:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/ckzy12a6k370211efmt1ulruqmq</link>
  <guid>https://status.mainnet.concordium.com/maintenance/ckzy12a6k370211efmt1ulruqmq</guid>
</item>

<item>
  <title>Scheduled infrastructure maintenance</title>
  <description>
    Type: Maintenance
    Duration: 4 hours and 8 minutes

    Affected Components: Mainnet, Wallet Backend, Identity Providers, CCD Scan
    Feb 1, 16:08:09 GMT+0 - Completed - Maintenance has completed successfully. Feb 1, 12:00:00 GMT+0 - Identified - We are planning for a scheduled network maintenance during that time. We are not expecting any impact in the network.
 Feb 1, 11:59:59 GMT+0 - Identified - Maintenance is now in progress. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 hours and 8 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>16:08:09</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for a scheduled network maintenance during that time. We are not expecting any impact in the network.
.</p>
<p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>11:59:59</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 1 Feb 2022 12:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/ckz40lg7a180687d2oo5ay15qnk</link>
  <guid>https://status.mainnet.concordium.com/maintenance/ckz40lg7a180687d2oo5ay15qnk</guid>
</item>

<item>
  <title>Minor update on Wallet backend </title>
  <description>
    Type: Maintenance
    Duration: 23 minutes

    Affected Components: Wallet Backend, Identity Providers
    Jan 27, 14:07:37 GMT+0 - Completed - Maintenance has completed successfully. Jan 27, 14:07:05 GMT+0 - Identified - Maintenance is now in progress. Jan 27, 13:44:11 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 23 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>14:07:37</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>14:07:05</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress..</p>
<p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>13:44:11</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 27 Jan 2022 13:44:11 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/ckyx14z2z85476d7oc82r3real</link>
  <guid>https://status.mainnet.concordium.com/maintenance/ckyx14z2z85476d7oc82r3real</guid>
</item>

<item>
  <title>Protocol Update on Mainnet</title>
  <description>
    Type: Maintenance
    Duration: 5 minutes

    Affected Components: Mainnet
    Jan 11, 11:05:14 GMT+0 - Completed - The protocol update is effective. Jan 11, 11:00:00 GMT+0 - Identified - The protocol update to add support for account aliases as described previously is rescheduled to take effect on mainnet on January 11, 2022. Jan 11, 11:00:00 GMT+0 - Identified - **Important note to all bakers:** Please do not lower your stake or deregister as baker before the protocol update is effective. Jan 11, 11:00:00 GMT+0 - Identified - A protocol update to add support for multiple addresses for the same account, also referred to as account aliases, will take effect on mainnet on January 17, 2022.

New node software compliant with the protocol update has already been released for Linux, Windows, and MacOS [here](https://developer.concordium.software/en/mainnet/net/installation/downloads.html#concordium-node-distributions). Node runners **must upgrade** their nodes before the new protocol takes effect. Old nodes will stop processing new blocks at that point.

For more details on the protocol update, see [concordium-update-proposals](https://github.com/Concordium/concordium-update-proposals).

The protocol update on mainnet is preceded by a similar protocol update on testnet in December 2021. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jan <var data-var='date'> 11</var>, <var data-var='time'>11:05:14</var> GMT+0</small><br><strong>Completed</strong> -
  The protocol update is effective..</p>
<p><small>Jan <var data-var='date'> 11</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  The protocol update to add support for account aliases as described previously is rescheduled to take effect on mainnet on January 11, 2022..</p>
<p><small>Jan <var data-var='date'> 11</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  **Important note to all bakers:** Please do not lower your stake or deregister as baker before the protocol update is effective..</p>
<p><small>Jan <var data-var='date'> 11</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  A protocol update to add support for multiple addresses for the same account, also referred to as account aliases, will take effect on mainnet on January 17, 2022.

New node software compliant with the protocol update has already been released for Linux, Windows, and MacOS [here](https://developer.concordium.software/en/mainnet/net/installation/downloads.html#concordium-node-distributions). Node runners **must upgrade** their nodes before the new protocol takes effect. Old nodes will stop processing new blocks at that point.

For more details on the protocol update, see [concordium-update-proposals](https://github.com/Concordium/concordium-update-proposals).

The protocol update on mainnet is preceded by a similar protocol update on testnet in December 2021..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 11 Jan 2022 11:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/ckxftjedn376408slej5l2wgqt</link>
  <guid>https://status.mainnet.concordium.com/maintenance/ckxftjedn376408slej5l2wgqt</guid>
</item>

<item>
  <title>Node upgrade</title>
  <description>
    Type: Maintenance
    Duration: 7 days and 12 hours

    Affected Components: Mainnet
    Jan 7, 11:00:00 GMT+0 - Completed - During this upgrade, finalization is expected to stop for a brief amount of time. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 7 days and 12 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  During this upgrade, finalization is expected to stop for a brief amount of time..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 7 Jan 2022 11:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/maintenance/ckxygnt4y1522898vom5rzlfbmn</link>
  <guid>https://status.mainnet.concordium.com/maintenance/ckxygnt4y1522898vom5rzlfbmn</guid>
</item>

<item>
  <title>Outage of backend services</title>
  <description>
    Type: Incident
    Duration: 22 hours and 54 minutes

    Affected Components: Wallet Backend, CCD Scan
    Nov 14, 08:28:00 GMT+0 - Resolved - The incident has been resolved and services are fully operational. Nov 13, 09:40:54 GMT+0 - Monitoring - We resolved the issues and both the wallet-proxy and the chain explorer on the network dashboard are operational.

We are monitoring for any additional signs of instability. Nov 13, 09:32:52 GMT+0 - Identified - The mobile wallet backend is operational again. Nov 13, 08:29:06 GMT+0 - Investigating - The wallet proxy and the chain explorer are not operational.

As a consequence mobile wallets cannot be used.

We are investigating the issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 22 hours and 54 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>08:28:00</var> GMT+0</small><br><strong>Resolved</strong> -
  The incident has been resolved and services are fully operational..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>09:40:54</var> GMT+0</small><br><strong>Monitoring</strong> -
  We resolved the issues and both the wallet-proxy and the chain explorer on the network dashboard are operational.

We are monitoring for any additional signs of instability..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>09:32:52</var> GMT+0</small><br><strong>Identified</strong> -
  The mobile wallet backend is operational again..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>08:29:06</var> GMT+0</small><br><strong>Investigating</strong> -
  The wallet proxy and the chain explorer are not operational.

As a consequence mobile wallets cannot be used.

We are investigating the issue..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 13 Nov 2021 08:29:06 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/ckvxjs82s468785qnaupwvpwjt</link>
  <guid>https://status.mainnet.concordium.com/incident/ckvxjs82s468785qnaupwvpwjt</guid>
</item>

<item>
  <title>Incorrect data displayed on the network dashboard</title>
  <description>
    Type: Incident
    Duration: 20 hours and 51 minutes

    Affected Components: CCD Scan
    Oct 11, 08:41:46 GMT+0 - Resolved - We just resolved the issue! Oct 10, 11:51:00 GMT+0 - Investigating - The network dashboard displays incorrect data, including some duplicate bakers.

The network is operating normally apart from the display issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 hours and 51 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 11</var>, <var data-var='time'>08:41:46</var> GMT+0</small><br><strong>Resolved</strong> -
  We just resolved the issue!.</p>
<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>11:51:00</var> GMT+0</small><br><strong>Investigating</strong> -
  The network dashboard displays incorrect data, including some duplicate bakers.

The network is operating normally apart from the display issue..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 10 Oct 2021 11:51:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/ckul899rf286217s8lkotjuyv0y</link>
  <guid>https://status.mainnet.concordium.com/incident/ckul899rf286217s8lkotjuyv0y</guid>
</item>

<item>
  <title>Support services outage</title>
  <description>
    Type: Incident
    Duration: 10 minutes

    Affected Components: Wallet Backend, CCD Scan
    Oct 8, 09:20:00 GMT+0 - Resolved - The issue was identified and resolved.
Network Dashboard and Wallet Backend become available again. Oct 8, 09:10:00 GMT+0 - Investigating - Network Dashboard and Wallet Backend become unresponsive. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>09:20:00</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue was identified and resolved.
Network Dashboard and Wallet Backend become available again..</p>
<p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>09:10:00</var> GMT+0</small><br><strong>Investigating</strong> -
  Network Dashboard and Wallet Backend become unresponsive..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 8 Oct 2021 09:10:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/ckui6egfx752940pookpl557fys</link>
  <guid>https://status.mainnet.concordium.com/incident/ckui6egfx752940pookpl557fys</guid>
</item>

<item>
  <title>Partial interruption of identity issuance</title>
  <description>
    Type: Incident
    Duration: 17 hours and 24 minutes

    Affected Components: Identity Providers
    Jul 29, 06:47:11 GMT+0 - Resolved - Desktop wallet version 1.1.6 has been released for Windows as well, resolving the identity issuance issue. Jul 28, 14:47:45 GMT+0 - Identified - The new version 1.1.6 of the desktop wallet that fixes the issue has been released for MacOS and Linux.

The Windows version will be available shortly and an update will be posted here. Jul 28, 14:07:48 GMT+0 - Identified - We have identified the issue and are working on an update to the desktop wallet to fix it. Jul 28, 13:22:44 GMT+0 - Investigating - We are currently experiencing an issue with identity creation via the newly released desktop wallet. Identity creation fails immediately after identity verification.

We are investigating the cause of the issue together with the identity provider.

Identity issuance via the mobile wallets is expected to work. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 17 hours and 24 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>06:47:11</var> GMT+0</small><br><strong>Resolved</strong> -
  Desktop wallet version 1.1.6 has been released for Windows as well, resolving the identity issuance issue..</p>
<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>14:47:45</var> GMT+0</small><br><strong>Identified</strong> -
  The new version 1.1.6 of the desktop wallet that fixes the issue has been released for MacOS and Linux.

The Windows version will be available shortly and an update will be posted here..</p>
<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>14:07:48</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the issue and are working on an update to the desktop wallet to fix it..</p>
<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>13:22:44</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently experiencing an issue with identity creation via the newly released desktop wallet. Identity creation fails immediately after identity verification.

We are investigating the cause of the issue together with the identity provider.

Identity issuance via the mobile wallets is expected to work..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 28 Jul 2021 13:22:44 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/ckrniy5db5249757nmvcbcaltdu</link>
  <guid>https://status.mainnet.concordium.com/incident/ckrniy5db5249757nmvcbcaltdu</guid>
</item>

<item>
  <title>Identities cannot be issued</title>
  <description>
    Type: Incident
    Duration: 2 hours and 15 minutes

    Affected Components: Identity Providers
    Jul 12, 15:42:48 GMT+0 - Resolved - We just resolved the issue!

New identities can again be issued. Jul 12, 13:27:32 GMT+0 - Investigating - New identities cannot be issued with the Notabene identity issuer. Accounts and existing identities can be used without problems.

We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 12</var>, <var data-var='time'>15:42:48</var> GMT+0</small><br><strong>Resolved</strong> -
  We just resolved the issue!

New identities can again be issued..</p>
<p><small>Jul <var data-var='date'> 12</var>, <var data-var='time'>13:27:32</var> GMT+0</small><br><strong>Investigating</strong> -
  New identities cannot be issued with the Notabene identity issuer. Accounts and existing identities can be used without problems.

We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 12 Jul 2021 13:27:32 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/ckr0ny8i41758847vohd0r1ltcb</link>
  <guid>https://status.mainnet.concordium.com/incident/ckr0ny8i41758847vohd0r1ltcb</guid>
</item>

<item>
  <title>Interruptions in mainnet supporting services</title>
  <description>
    Type: Incident
    

    Affected Components: CCD Scan, Wallet Backend
    Jul 1, 08:00:00 GMT+0 - Resolved - On 01-07-2021 between 09:30 and 10:00 CEST, we experienced network issues in mainnet supporting services like network dashboard and mobile wallet backend. All issues are resolved and services are back to normal.
 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Resolved</strong> -
  On 01-07-2021 between 09:30 and 10:00 CEST, we experienced network issues in mainnet supporting services like network dashboard and mobile wallet backend. All issues are resolved and services are back to normal.
.</p>
]]>
  </content:encoded>
  <pubDate>Thu, 1 Jul 2021 08:00:00 +0000</pubDate>
  <link>https://status.mainnet.concordium.com/incident/ckqkv9f5f270103a0n844h5s6do</link>
  <guid>https://status.mainnet.concordium.com/incident/ckqkv9f5f270103a0n844h5s6do</guid>
</item>

  </channel>
  </rss>