<?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>Strise Status - Incident history</title>
    <link>https://status.strise.ai</link>
    <description>Strise</description>
    <pubDate>Tue, 22 Sep 2026 10:46:26 +0000</pubDate>
    
<item>
  <title>Issues generating review PDFs</title>
  <description>
    Type: Incident
    Duration: 44 minutes

    Affected Components: Application, API
    Sep 22, 11:30:53 GMT+0 - Resolved - This incident has been resolved. All PDFs have been regenerated. Sep 22, 10:46:26 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 44 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>11:30:53</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved. All PDFs have been regenerated..</p>
<p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>10:46:26</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 22 Sep 2026 10:46:26 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmucju0331fzw1bruis949mt1</link>
  <guid>https://status.strise.ai/incident/cmucju0331fzw1bruis949mt1</guid>
</item>

<item>
  <title>Review PDFs failing to generate for some entities</title>
  <description>
    Type: Incident
    Duration: 7 hours and 7 minutes

    Affected Components: Application
    Sep 9, 16:52:17 GMT+0 - Resolved - This incident has been resolved. Sep 9, 14:34:16 GMT+0 - Identified - No description yet Sep 9, 09:45:00 GMT+0 - Identified - We are working on a fix for this incident. PDFs will be regenerated. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours and 7 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>16:52:17</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>14:34:16</var> GMT+0</small><br><strong>Identified</strong> -
  No description yet.</p>
<p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>09:45:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are working on a fix for this incident. PDFs will be regenerated..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 9 Sep 2026 09:45:00 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmtu71ujn0mbb13pquattwf4d</link>
  <guid>https://status.strise.ai/incident/cmtu71ujn0mbb13pquattwf4d</guid>
</item>

<item>
  <title>Settings page unavailable</title>
  <description>
    Type: Incident
    Duration: 3 minutes

    Affected Components: Application
    Aug 28, 13:16:57 GMT+0 - Resolved - This incident has been resolved. Aug 28, 13:16:56 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Aug 28, 13:13:29 GMT+0 - Identified - We are continuing to work on a fix for this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>13:16:57</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>13:16:56</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>13:13:29</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 28 Aug 2026 13:13:29 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmtcz2sw2012o1bo7uyhwkd02</link>
  <guid>https://status.strise.ai/incident/cmtcz2sw2012o1bo7uyhwkd02</guid>
</item>

<item>
  <title>ID-porten, Contact and reservation register, Machine porten, MinID, eMediation, ELMA, eInnsyn, Employee porten, Self-service solutions, Altinn - Operational problems</title>
  <description>
    Type: Incident
    Duration: 3 days, 10 hours and 37 minutes

    Affected Components: Digdir → Maskinporten
    Sep 14, 10:28:43 GMT+0 - Resolved - # **Report after denial of service attack**

This is an open report \(«post mortem»\) after the denial of service attack against ID-porten on 24-26 August.

‌

**The attack**

From 03:38 on Monday 24 August to 19:30 on Wednesday 26 August, several of Digdir&#039;s shared solutions were completely or partially unavailable for periods as a result of a denial of service attack \(DDoS\). DDoS attacks overload digital services with artificial network traffic to make them unavailable.

The attack targeted ID-porten. This was the third denial of service attack against ID-porten in nine weeks. The attack was two to three times more powerful than previously.

ID-porten and several other of Digdir&#039;s shared solutions are operated on a common operating platform at our operating partner Vivicta. The attack therefore also affected eFormidling, ELMA, Kontakt- og reservasjonsregisteret, eInnsyn, Maskinporten and Ansattporten. Altinn, eSignering and Digital mailbox for citizens were also affected as a result of login via ID-porten not being possible for periods.

 

**Event sequence and measures**

The incident started at 03:38 on August 24, and Digdir confirmed in a status message at 08:11 that it was a denial of service attack.   Continuous measures were taken along the way to reduce the scope of the attack and stabilize the solutions, in collaboration with Vivicta.  From 07:20 the same day, there was increased stability and availability again in all of Digdir&#039;s shared solutions.

The DDoS attack came in waves and the attack pattern changed along the way. From 13:20 to 14:15 on August 24, several of Digdir&#039;s shared solutions were again unavailable. On Tuesday, August 25, there were particular challenges with eSignering, which remained unavailable until 01:42 on Wednesday night. On Wednesday, August 26, the solutions were still stable, and at 19:30 the attack was over. Digdir chose to maintain the restrictions that had been implemented until the next day while monitoring the situation.

Although the denial of service attack was both more powerful and longer-lasting than previous attacks, the measures contributed to the solutions being largely available during the incident. Traffic in Norway was, with some exceptions, stable throughout the entire period. Measures that were implemented led to periodic restrictions on traffic through the ID-porten from abroad. On August 27 at 09:00, Digdir confirmed via a status message that the attack was over, and at 14:50 that the joint solutions were back in normal operation. Until September 2, problems could be experienced with logging in to the ID-porten from abroad.

The Norwegian Data Protection Authority and the National Security Authority \(NSM\) were notified in accordance with current procedures.

There are no indications that the incident has resulted in personal data being compromised.

The entire incident is being reviewed in line with Digdir&#039;s routines and practices. Attack methods are continuously evolving, and handling this type of attack requires ongoing adaptations. Digdir is working closely with its operational partners to improve incident handling and, to the greatest extent possible, protect ourselves against similar attacks in the future. Sep 2, 07:08:41 GMT+0 - Resolved - The incident has been resolved. 

A postmortem report on the incident will be published at a later date. Aug 27, 12:50:30 GMT+0 - Resolved - This incident has been resolved. Aug 27, 12:50:29 GMT+0 - Monitoring - All solutions are now functioning normally.

There are still some operational disruptions related to traffic from abroad, which we are working to resolve. 
We will continue to monitor the situation and update as needed. Aug 27, 07:06:30 GMT+0 - Monitoring - Status 09:00

This indicates that the attack has ended. Our solutions have largely functioned as normal throughout the night, and traffic is picking up as usual throughout the day. Only some traffic from abroad has still experienced operational disruptions as a result of the attack. We have maintained our contingency measures throughout the night as an insurance policy, and are monitoring the situation throughout the day.

The attack began on Monday night at 03:38 and stopped at 19:30 on Wednesday evening. With the exception of short periods, the ID-porten and the shared solutions have been available at all times. We expect to return to normal operations within the next few days. Aug 26, 21:04:25 GMT+0 - Identified - Update 23:00

The solutions are still in stable operating status.

ID-porten still has limitations.

The next scheduled status update is tomorrow morning at approximately 09:00 Aug 26, 19:01:59 GMT+0 - Identified - The solutions are still in stable operating status.

ID-porten still has limitations.

The next scheduled status message is approx. 11 p.m. Aug 26, 16:17:58 GMT+0 - Identified - The solutions are still in stable operating status.

ID-porten still has limitations.

The next scheduled status message is approx. 9 p.m. Aug 26, 13:02:49 GMT+0 - Identified - The solutions are still in stable operating status.

ID-porten still has limitations.

The next scheduled status message is approx. 6 p.m. Aug 26, 11:02:57 GMT+0 - Identified - The solutions are still in stable operating status.

ID-porten still has limitations.

The next scheduled status update is approximately 3 p.m. Aug 26, 08:57:06 GMT+0 - Identified - Update 10:55

Still stable operational status. 

ID-porten still has limitations.

The next scheduled status update is approx. 1 p.m. Aug 26, 07:06:41 GMT+0 - Identified - Update 09:05

The attack has continued through the night, but the solutions have been stable.

ID-porten still has limitations.

Next update will be approx. 10:30 Aug 25, 23:42:27 GMT+0 - Identified - Update 01:40

The attack has been going on for most of the day except for a short break. 

The suppliers at eSignering have taken measures so that this service is now functioning normally again.

ID-porten still has limitations and we know that it is already, and is starting to become critical for several customers and services. Unfortunately, we do not have an estimate for when we can release even more. 

Thank you for your patience, we will continue with status updates tomorrow. Aug 25, 20:14:08 GMT+0 - Identified - Update 22:13

We have nothing new to report right now. A little recap of the day will be coming soon. Aug 25, 17:09:19 GMT+0 - Identified - Update 19:07

There was a short pause in the attack before it started up again with the same strength at approximately 17:15.

Otherwise, the situation is the same for all solutions.

The next scheduled status update is at 22:00. Aug 25, 15:14:12 GMT+0 - Identified - Update 17:13

Still the same status as it has been for a while.

ID-porten still has the same limitations.

eSignering is unavailable due to the limitations in ID-porten. You can still create signing assignments, but it is the signing itself that is unavailable.

The next scheduled update is at 19:00. Aug 25, 12:12:55 GMT+0 - Identified - Update 14:00

ID-porten still has the same limitations.

eSignering is unavailable due to the limitations in ID-porten. You can still create signing assignments, but it is the signing itself that is unavailable.

We can also inform you that measures have been taken to help those who have had connection problems with ELMA and Maskinporten. Here we have received confirmation from several customers that it is working again now. Aug 25, 10:00:52 GMT+0 - Identified - Update 12:00

ID-porten still has the same limitations.

eSignering is unavailable due to the limitations in ID-porten. You can still create signing assignments, but it is the signing itself that is unavailable.

The machine port should function as normal. Aug 25, 08:33:27 GMT+0 - Identified - We have made some updates on the status of our solutions.

ID-porten still has the same limitations.

eSignering is unavailable due to the limitations in ID-porten. You can still create signing assignments, but it is the signing itself that is unavailable.

The machine port should function as normal, but we have received some indications from customers who are still having problems with connection or increased response time. We are looking into this together with the operating partner.

The next scheduled update will be at 12:00. Aug 25, 07:33:48 GMT+0 - Identified - Update 09:30.

Still the same status for ID-porten. We will update info about the other solutions soon. Aug 25, 06:15:18 GMT+0 - Identified - The attack has been going on all night and is still ongoing. 

The status of the solutions is the same as we ended yesterday. It works for many, but there are still many who are experiencing problems.

The next update will be around 09:30 Aug 24, 21:49:05 GMT+0 - Identified - Some measures that worsened the situation for our solutions have been reversed. 

We are back to the same status as around 9 p.m. This means that it works for many, but there are also many who are still experiencing problems. 

The attacks are still ongoing, so we are going into the night with the restrictions that have been in place for most of the day today. 

There will be no more updates during the night. 

Thank you for your patience. Aug 24, 20:03:24 GMT+0 - Identified - Update 22:01

We are experiencing a worsening of the situation. Aug 24, 19:15:37 GMT+0 - Identified - Update 21:13
The shared solutions are still stable, but with the same limitations as at 16:00.

We will provide a new status update before 23:00. Aug 24, 14:09:27 GMT+0 - Identified - Update at 4pm:
The attack is still ongoing, but the solutions are stable with the restrictions that have been set. 

We know that some people are still experiencing problems, and we are continuously assessing when we can relax some restrictions. Aug 24, 12:51:50 GMT+0 - Identified - We are seeing some improvement again from around 2:14 PM. However, there will be some customers and services that will still experience operational disruptions and problems connecting. Aug 24, 11:25:49 GMT+0 - Identified - We are seeing a deterioration in several solutions again. Aug 24, 10:42:02 GMT+0 - Identified - As of 12:20 we see that it is stabilizing again. We are aware that there are still services and customers experiencing operational disruptions.

The next scheduled update is approximately 13:30 Aug 24, 10:08:28 GMT+0 - Identified - We are seeing a deterioration in the ID portal, the Employee portal, the Contact and Reservation Register. Aug 24, 09:36:27 GMT+0 - Identified - The solutions still appear stable, but we are aware that some customers and services are still affected by the measures that have been taken.

The next scheduled update is approximately 1:30 PM. Aug 24, 07:51:07 GMT+0 - Identified - We are seeing increased stability and availability in all solutions from approximately 08:50.

The next status update will be at 11:30 unless there are any major changes before then. Aug 24, 06:11:53 GMT+0 - Identified - Our operating partner Vivicta confirms that this is a denial of service attack. We have been working closely with Vivicta on stabilizing measures since the attack began, and are now experiencing improvement. As of 07.25, the solutions are on the way up, and more people are able to log in via the ID-porten. We are continuing with additional stabilizing measures, and continue to monitor the solutions. Aug 24, 05:29:55 GMT+0 - Investigating - Update as of 07:28

We are experiencing increased availability of the solutions as of 07:25. However, some may still experience issues. Aug 24, 04:42:18 GMT+0 - Investigating - Update at 06:41

Digdir&#039;s shared solutions have been unavailable since 03:38. This applies to ID-porten, Employee Portal, Contact and Reservation Register, Min ID, Maskinporten, eFormidling, eInnsyn, ELMA, Self-service.
Altinn, eSignering and Digital mailbox for residents are also affected, as a result of login via ID-porten not being possible.
The same applies to login to public entities that use ID-porten. For some services, such as Helse Norge, you can use a mobile app to log in.
We are working together with our operations provider Vivicta to resolve the problems as quickly as possible. Aug 24, 03:50:11 GMT+0 - Investigating - Update as of 05:48 

We are still experiencing problems with several solutions. This applies to ID-porten, Contact and reservation register, Maskinporten, MinID, eFormidling, ELMA, eInnsyn, Ansattporten, Self-service solutions, Altinn. 

The problems occurred from 03:38 Aug 24, 02:52:30 GMT+0 - Investigating - Update at 04:51. 

We are still experiencing problems with several solutions. 

Applies to ID-porten, Contact and reservation register, Maskinporten, MinID, eFormidling, ELMA, eInnsyn, Ansattporten, Self-service solutions, Altinn Aug 24, 02:13:11 GMT+0 - Investigating - There are problems with several solutions as of 03:41. We are investigating the problems. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 10 hours and 37 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 14</var>, <var data-var='time'>10:28:43</var> GMT+0</small><br><strong>Resolved</strong> -
  # **Report after denial of service attack**

This is an open report \(«post mortem»\) after the denial of service attack against ID-porten on 24-26 August.

‌

**The attack**

From 03:38 on Monday 24 August to 19:30 on Wednesday 26 August, several of Digdir&#039;s shared solutions were completely or partially unavailable for periods as a result of a denial of service attack \(DDoS\). DDoS attacks overload digital services with artificial network traffic to make them unavailable.

The attack targeted ID-porten. This was the third denial of service attack against ID-porten in nine weeks. The attack was two to three times more powerful than previously.

ID-porten and several other of Digdir&#039;s shared solutions are operated on a common operating platform at our operating partner Vivicta. The attack therefore also affected eFormidling, ELMA, Kontakt- og reservasjonsregisteret, eInnsyn, Maskinporten and Ansattporten. Altinn, eSignering and Digital mailbox for citizens were also affected as a result of login via ID-porten not being possible for periods.

 

**Event sequence and measures**

The incident started at 03:38 on August 24, and Digdir confirmed in a status message at 08:11 that it was a denial of service attack.   Continuous measures were taken along the way to reduce the scope of the attack and stabilize the solutions, in collaboration with Vivicta.  From 07:20 the same day, there was increased stability and availability again in all of Digdir&#039;s shared solutions.

The DDoS attack came in waves and the attack pattern changed along the way. From 13:20 to 14:15 on August 24, several of Digdir&#039;s shared solutions were again unavailable. On Tuesday, August 25, there were particular challenges with eSignering, which remained unavailable until 01:42 on Wednesday night. On Wednesday, August 26, the solutions were still stable, and at 19:30 the attack was over. Digdir chose to maintain the restrictions that had been implemented until the next day while monitoring the situation.

Although the denial of service attack was both more powerful and longer-lasting than previous attacks, the measures contributed to the solutions being largely available during the incident. Traffic in Norway was, with some exceptions, stable throughout the entire period. Measures that were implemented led to periodic restrictions on traffic through the ID-porten from abroad. On August 27 at 09:00, Digdir confirmed via a status message that the attack was over, and at 14:50 that the joint solutions were back in normal operation. Until September 2, problems could be experienced with logging in to the ID-porten from abroad.

The Norwegian Data Protection Authority and the National Security Authority \(NSM\) were notified in accordance with current procedures.

There are no indications that the incident has resulted in personal data being compromised.

The entire incident is being reviewed in line with Digdir&#039;s routines and practices. Attack methods are continuously evolving, and handling this type of attack requires ongoing adaptations. Digdir is working closely with its operational partners to improve incident handling and, to the greatest extent possible, protect ourselves against similar attacks in the future..</p>
<p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>07:08:41</var> GMT+0</small><br><strong>Resolved</strong> -
  The incident has been resolved. 

A postmortem report on the incident will be published at a later date..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>12:50:30</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>12:50:29</var> GMT+0</small><br><strong>Monitoring</strong> -
  All solutions are now functioning normally.

There are still some operational disruptions related to traffic from abroad, which we are working to resolve. 
We will continue to monitor the situation and update as needed..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>07:06:30</var> GMT+0</small><br><strong>Monitoring</strong> -
  Status 09:00

This indicates that the attack has ended. Our solutions have largely functioned as normal throughout the night, and traffic is picking up as usual throughout the day. Only some traffic from abroad has still experienced operational disruptions as a result of the attack. We have maintained our contingency measures throughout the night as an insurance policy, and are monitoring the situation throughout the day.

The attack began on Monday night at 03:38 and stopped at 19:30 on Wednesday evening. With the exception of short periods, the ID-porten and the shared solutions have been available at all times. We expect to return to normal operations within the next few days..</p>
<p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>21:04:25</var> GMT+0</small><br><strong>Identified</strong> -
  Update 23:00

The solutions are still in stable operating status.

ID-porten still has limitations.

The next scheduled status update is tomorrow morning at approximately 09:00.</p>
<p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>19:01:59</var> GMT+0</small><br><strong>Identified</strong> -
  The solutions are still in stable operating status.

ID-porten still has limitations.

The next scheduled status message is approx. 11 p.m..</p>
<p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>16:17:58</var> GMT+0</small><br><strong>Identified</strong> -
  The solutions are still in stable operating status.

ID-porten still has limitations.

The next scheduled status message is approx. 9 p.m..</p>
<p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>13:02:49</var> GMT+0</small><br><strong>Identified</strong> -
  The solutions are still in stable operating status.

ID-porten still has limitations.

The next scheduled status message is approx. 6 p.m..</p>
<p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>11:02:57</var> GMT+0</small><br><strong>Identified</strong> -
  The solutions are still in stable operating status.

ID-porten still has limitations.

The next scheduled status update is approximately 3 p.m..</p>
<p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>08:57:06</var> GMT+0</small><br><strong>Identified</strong> -
  Update 10:55

Still stable operational status. 

ID-porten still has limitations.

The next scheduled status update is approx. 1 p.m..</p>
<p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>07:06:41</var> GMT+0</small><br><strong>Identified</strong> -
  Update 09:05

The attack has continued through the night, but the solutions have been stable.

ID-porten still has limitations.

Next update will be approx. 10:30.</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>23:42:27</var> GMT+0</small><br><strong>Identified</strong> -
  Update 01:40

The attack has been going on for most of the day except for a short break. 

The suppliers at eSignering have taken measures so that this service is now functioning normally again.

ID-porten still has limitations and we know that it is already, and is starting to become critical for several customers and services. Unfortunately, we do not have an estimate for when we can release even more. 

Thank you for your patience, we will continue with status updates tomorrow..</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>20:14:08</var> GMT+0</small><br><strong>Identified</strong> -
  Update 22:13

We have nothing new to report right now. A little recap of the day will be coming soon..</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>17:09:19</var> GMT+0</small><br><strong>Identified</strong> -
  Update 19:07

There was a short pause in the attack before it started up again with the same strength at approximately 17:15.

Otherwise, the situation is the same for all solutions.

The next scheduled status update is at 22:00..</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>15:14:12</var> GMT+0</small><br><strong>Identified</strong> -
  Update 17:13

Still the same status as it has been for a while.

ID-porten still has the same limitations.

eSignering is unavailable due to the limitations in ID-porten. You can still create signing assignments, but it is the signing itself that is unavailable.

The next scheduled update is at 19:00..</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>12:12:55</var> GMT+0</small><br><strong>Identified</strong> -
  Update 14:00

ID-porten still has the same limitations.

eSignering is unavailable due to the limitations in ID-porten. You can still create signing assignments, but it is the signing itself that is unavailable.

We can also inform you that measures have been taken to help those who have had connection problems with ELMA and Maskinporten. Here we have received confirmation from several customers that it is working again now..</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>10:00:52</var> GMT+0</small><br><strong>Identified</strong> -
  Update 12:00

ID-porten still has the same limitations.

eSignering is unavailable due to the limitations in ID-porten. You can still create signing assignments, but it is the signing itself that is unavailable.

The machine port should function as normal..</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>08:33:27</var> GMT+0</small><br><strong>Identified</strong> -
  We have made some updates on the status of our solutions.

ID-porten still has the same limitations.

eSignering is unavailable due to the limitations in ID-porten. You can still create signing assignments, but it is the signing itself that is unavailable.

The machine port should function as normal, but we have received some indications from customers who are still having problems with connection or increased response time. We are looking into this together with the operating partner.

The next scheduled update will be at 12:00..</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>07:33:48</var> GMT+0</small><br><strong>Identified</strong> -
  Update 09:30.

Still the same status for ID-porten. We will update info about the other solutions soon..</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>06:15:18</var> GMT+0</small><br><strong>Identified</strong> -
  The attack has been going on all night and is still ongoing. 

The status of the solutions is the same as we ended yesterday. It works for many, but there are still many who are experiencing problems.

The next update will be around 09:30.</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>21:49:05</var> GMT+0</small><br><strong>Identified</strong> -
  Some measures that worsened the situation for our solutions have been reversed. 

We are back to the same status as around 9 p.m. This means that it works for many, but there are also many who are still experiencing problems. 

The attacks are still ongoing, so we are going into the night with the restrictions that have been in place for most of the day today. 

There will be no more updates during the night. 

Thank you for your patience..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>20:03:24</var> GMT+0</small><br><strong>Identified</strong> -
  Update 22:01

We are experiencing a worsening of the situation..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>19:15:37</var> GMT+0</small><br><strong>Identified</strong> -
  Update 21:13
The shared solutions are still stable, but with the same limitations as at 16:00.

We will provide a new status update before 23:00..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>14:09:27</var> GMT+0</small><br><strong>Identified</strong> -
  Update at 4pm:
The attack is still ongoing, but the solutions are stable with the restrictions that have been set. 

We know that some people are still experiencing problems, and we are continuously assessing when we can relax some restrictions..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>12:51:50</var> GMT+0</small><br><strong>Identified</strong> -
  We are seeing some improvement again from around 2:14 PM. However, there will be some customers and services that will still experience operational disruptions and problems connecting..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>11:25:49</var> GMT+0</small><br><strong>Identified</strong> -
  We are seeing a deterioration in several solutions again..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>10:42:02</var> GMT+0</small><br><strong>Identified</strong> -
  As of 12:20 we see that it is stabilizing again. We are aware that there are still services and customers experiencing operational disruptions.

The next scheduled update is approximately 13:30.</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>10:08:28</var> GMT+0</small><br><strong>Identified</strong> -
  We are seeing a deterioration in the ID portal, the Employee portal, the Contact and Reservation Register..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>09:36:27</var> GMT+0</small><br><strong>Identified</strong> -
  The solutions still appear stable, but we are aware that some customers and services are still affected by the measures that have been taken.

The next scheduled update is approximately 1:30 PM..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>07:51:07</var> GMT+0</small><br><strong>Identified</strong> -
  We are seeing increased stability and availability in all solutions from approximately 08:50.

The next status update will be at 11:30 unless there are any major changes before then..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>06:11:53</var> GMT+0</small><br><strong>Identified</strong> -
  Our operating partner Vivicta confirms that this is a denial of service attack. We have been working closely with Vivicta on stabilizing measures since the attack began, and are now experiencing improvement. As of 07.25, the solutions are on the way up, and more people are able to log in via the ID-porten. We are continuing with additional stabilizing measures, and continue to monitor the solutions..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>05:29:55</var> GMT+0</small><br><strong>Investigating</strong> -
  Update as of 07:28

We are experiencing increased availability of the solutions as of 07:25. However, some may still experience issues..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>04:42:18</var> GMT+0</small><br><strong>Investigating</strong> -
  Update at 06:41

Digdir&#039;s shared solutions have been unavailable since 03:38. This applies to ID-porten, Employee Portal, Contact and Reservation Register, Min ID, Maskinporten, eFormidling, eInnsyn, ELMA, Self-service.
Altinn, eSignering and Digital mailbox for residents are also affected, as a result of login via ID-porten not being possible.
The same applies to login to public entities that use ID-porten. For some services, such as Helse Norge, you can use a mobile app to log in.
We are working together with our operations provider Vivicta to resolve the problems as quickly as possible..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>03:50:11</var> GMT+0</small><br><strong>Investigating</strong> -
  Update as of 05:48 

We are still experiencing problems with several solutions. This applies to ID-porten, Contact and reservation register, Maskinporten, MinID, eFormidling, ELMA, eInnsyn, Ansattporten, Self-service solutions, Altinn. 

The problems occurred from 03:38.</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>02:52:30</var> GMT+0</small><br><strong>Investigating</strong> -
  Update at 04:51. 

We are still experiencing problems with several solutions. 

Applies to ID-porten, Contact and reservation register, Maskinporten, MinID, eFormidling, ELMA, eInnsyn, Ansattporten, Self-service solutions, Altinn.</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>02:13:11</var> GMT+0</small><br><strong>Investigating</strong> -
  There are problems with several solutions as of 03:41. We are investigating the problems..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 24 Aug 2026 05:29:55 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmt8ews04014l1anp6rmd7ddb</link>
  <guid>https://status.strise.ai/incident/cmt8ews04014l1anp6rmd7ddb</guid>
</item>

<item>
  <title>Elevated errors in the portfolio</title>
  <description>
    Type: Incident
    Duration: 1 hour and 42 minutes

    Affected Components: Application
    Aug 13, 12:23:40 GMT+0 - Resolved - This incident has been resolved. Aug 13, 10:49:57 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Aug 13, 10:42:05 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 42 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>12:23:40</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>10:49:57</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Aug <var data-var='date'> 13</var>, <var data-var='time'>10:42:05</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 13 Aug 2026 10:42:05 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmsre2c0s09yk1co9lapspgcn</link>
  <guid>https://status.strise.ai/incident/cmsre2c0s09yk1co9lapspgcn</guid>
</item>

<item>
  <title>Maskinporten</title>
  <description>
    Type: Incident
    Duration: 11 hours and 2 minutes

    Affected Components: Application, API
    Aug 3, 16:50:10 GMT+0 - Resolved - This incident has been resolved. Aug 3, 12:29:59 GMT+0 - Monitoring - Maskinporten is recovering and we are currently monitoring the result. Aug 3, 05:47:47 GMT+0 - Identified - Maskinporten is currently experiencing an outage affecting our integration towards Norwegian Population Register (Folkeregistret) which affects private persons functionality. More info can be found at https://status.digdir.no/ 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 hours and 2 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>16:50:10</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>12:29:59</var> GMT+0</small><br><strong>Monitoring</strong> -
  Maskinporten is recovering and we are currently monitoring the result..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>05:47:47</var> GMT+0</small><br><strong>Identified</strong> -
  Maskinporten is currently experiencing an outage affecting our integration towards Norwegian Population Register (Folkeregistret) which affects private persons functionality. More info can be found at https://status.digdir.no/.</p>
]]>
  </content:encoded>
  <pubDate>Mon, 3 Aug 2026 05:47:47 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmsct5c0o06le0rswl8stapm3</link>
  <guid>https://status.strise.ai/incident/cmsct5c0o06le0rswl8stapm3</guid>
</item>

<item>
  <title>ID-porten, Contact and reservation register, Machine porten, MinID, eMediation, ELMA, eInnsyn, Employee porten, Self-service solutions, Altinn - Operational problems</title>
  <description>
    Type: Incident
    Duration: 22 days, 18 hours and 58 minutes

    Affected Components: Digdir → Maskinporten
    Aug 17, 07:54:46 GMT+0 - Resolved - # Report after denial of service attack 

This is an open report \(«post mortem»\) after the denial of service attack against ID-porten on August 3.

## 
The attack 

From 00:50 on Monday, August 3, to 13:03 on Tuesday, August 4, several of Digdir&#039;s shared solutions were completely or partially unavailable, as a result of a denial of service attack \(DDoS attack\). DDoS attacks overload digital services with artificial network traffic to make them unavailable. 

The attack was targeted at ID-porten. 

ID-porten has been subjected to two attacks in a short time. The attack on August 3 is the most powerful denial of service attack we have experienced against ID-porten. 

The attack started at 00:50 on August 3, and from that time on, continuous work was done to solve the problem. The attack came in several waves, and traffic showed improvement from 13:40 the same day, but some solutions experienced new problems throughout the afternoon and evening. From 01:26 the night of August 4, the solutions were partially available. From 13:03 the same day, the solutions were back in normal operation. 

ID-porten and several other of Digdir&#039;s joint solutions are operated on a common operating platform at our operations provider Vivicta. The attack therefore also affected eFormidling, ELMA, the Contact and Reservation Register, eInnsyn, Maskinporten and Ansattporten. Altinn, eSignering and Digital mailbox for residents were also affected as a result of the fact that logging in via ID-porten was not possible for periods.

## 
Handling during the attack

Continuous measures were taken during the attack to reduce the scope of the attack and stabilize the solutions, in collaboration with Vivicta. Once the attack was over, it was quick to stabilize traffic and restore normal operation. The Norwegian Data Protection Authority and the National Security Authority \(NSM\) were notified in accordance with current procedures. The incident has not led to a security breach or personal data being compromised. 

The entire incident is now being thoroughly reviewed, in line with our routines and practices. We are constantly working closely with our operating partners to improve incident handling.

## 
Information on the way

The denial of service attack caused problems for businesses and citizens, because it was not possible for users to log in to public services at times. 

Many of our customers and system suppliers have their own obligations to their customers when the common solutions are unavailable, and it is important that we sufficiently enable them to make their own risk and consequence assessments through as good and precise information as possible. 

In retrospect, we see that it took too long before we referred to the incident as a denial of service attack. At the same time, the need to provide information about the cause must be weighed against general recommendations not to publish details about ongoing attacks, both to avoid helping the attacker and to avoid giving the person in question the effect or attention that is sought. We are now reviewing routines for status messages for when and how the cause and status are communicated, so that users and customers can get a more accurate picture of the situation more quickly – 
especially in the case of long-term incidents. 

## Further work 

The services of the Directorate of Digitalisation are part of a socially critical infrastructure. It is crucial that the solutions work for citizens and businesses, and we therefore take operational disruptions very seriously. 

Dedicated security environments in Digdir are continuously working to ensure high availability and robustness in digital services that are important to society. Together with our operating partners, we have comprehensive security mechanisms in place. At the same time, attack methods are continuously developing, so that handling this type of attack requires 
ongoing adaptations. We are working to protect ourselves as much as possible against similar attacks in the future. Aug 5, 07:57:24 GMT+0 - Resolved - We are ending the outage. Customers who are still experiencing problems can contact the service desk.

You can read more about the incident here: https://www.digdir.no/felleslosninger/digdirs-felleslosninger-tilbake-i-normal-drift/8315 Aug 4, 11:03:50 GMT+0 - Monitoring - We are back to normal operation.

Please contact the service desk if you are still experiencing problems. Aug 4, 07:45:37 GMT+0 - Monitoring - We are changing back to yellow status for several solutions. We have received reports from several people who are unable to connect to services from data centers in various countries. 

As of now, we know that the following countries may experience problems connecting:
- Germany
- Switzerland
- Netherlands
- Belgium

We are working with our operating partner to resolve this. Aug 4, 07:02:26 GMT+0 - Monitoring - Status 04.08.2026 at 09:00

All solutions are back in normal operation as of approx. 01:30 tonight. 

We will keep this issue open for a while longer, and will provide more details as time goes on. Aug 4, 05:51:15 GMT+0 - Monitoring - Status 04.08.2026 at 07:45

As of approx. 01:26 last night, the shared solutions have been stable. We will return with more information approx. 08:30 Aug 3, 22:11:21 GMT+0 - Identified - Status 04.08.2026 at 00:08

Still a large number of errors in the ID-porten. Work is still underway to resolve it.

Most other solutions work, but instability and varying response times may still be experienced.

The next update will be at approximately 07:30. Aug 3, 20:52:22 GMT+0 - Identified - Status 03.08.2026 at 22:46

Large increase in the number of errors in the ID-porten. Mitigation measures are being worked on.

Most other solutions work, but instability and varying response times may still be experienced. Aug 3, 19:05:12 GMT+0 - Identified - Status 03.08.2026 at 21:00

Most solutions work, but instability and varying response times may still be experienced. Aug 3, 16:34:18 GMT+0 - Identified - We are experiencing problems again from approximately 17:55 Aug 3, 14:55:23 GMT+0 - Monitoring - Since 01:00 on Monday, August 3, a denial of service attack (DDoS) has been ongoing against the ID-porten operated by Digdir&#039;s operating partner Vivicta. This affects several of Digdir&#039;s solutions and causes users to experience problems logging in to public services. We are working with Vivicta on measures to resolve the issue. 

As of 13:40, traffic was on the rise again, but it may take some time before all services are available and back in normal operation. Aug 3, 11:53:59 GMT+0 - Monitoring - From approximately 1:40 PM, it appears that traffic is on the rise again on the affected routes. Aug 3, 11:36:08 GMT+0 - Investigating - We are still working to resolve the issue. 

The next update will be at 2:30 PM unless we have something new before then. Aug 3, 10:41:25 GMT+0 - Investigating - We are still working to resolve the issue. 

The next update will be at 1:30 PM unless we have something new before then. Aug 3, 09:43:13 GMT+0 - Investigating - We are still working to resolve the issue. 

The next update will be at 12:30 if we don&#039;t have anything new before then. Aug 3, 08:30:18 GMT+0 - Investigating - We are still working to resolve the issue. 

The next update will be at 11:30 AM unless we have something new before then. Aug 3, 07:28:44 GMT+0 - Investigating - We are still working to resolve the issue. 

The next status update will be at 10:30 AM. Aug 3, 05:20:49 GMT+0 - Investigating - Troubleshooting is still ongoing. Aug 3, 01:20:09 GMT+0 - Investigating - The problem appears to have started around 00:50. The operating partner is working to resolve the issue, we will update when we have something new to report. Aug 2, 22:50:26 GMT+0 - Investigating - There are problems with several solutions. We are investigating the problems. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 22 days, 18 hours and 58 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>07:54:46</var> GMT+0</small><br><strong>Resolved</strong> -
  # Report after denial of service attack 

This is an open report \(«post mortem»\) after the denial of service attack against ID-porten on August 3.

## 
The attack 

From 00:50 on Monday, August 3, to 13:03 on Tuesday, August 4, several of Digdir&#039;s shared solutions were completely or partially unavailable, as a result of a denial of service attack \(DDoS attack\). DDoS attacks overload digital services with artificial network traffic to make them unavailable. 

The attack was targeted at ID-porten. 

ID-porten has been subjected to two attacks in a short time. The attack on August 3 is the most powerful denial of service attack we have experienced against ID-porten. 

The attack started at 00:50 on August 3, and from that time on, continuous work was done to solve the problem. The attack came in several waves, and traffic showed improvement from 13:40 the same day, but some solutions experienced new problems throughout the afternoon and evening. From 01:26 the night of August 4, the solutions were partially available. From 13:03 the same day, the solutions were back in normal operation. 

ID-porten and several other of Digdir&#039;s joint solutions are operated on a common operating platform at our operations provider Vivicta. The attack therefore also affected eFormidling, ELMA, the Contact and Reservation Register, eInnsyn, Maskinporten and Ansattporten. Altinn, eSignering and Digital mailbox for residents were also affected as a result of the fact that logging in via ID-porten was not possible for periods.

## 
Handling during the attack

Continuous measures were taken during the attack to reduce the scope of the attack and stabilize the solutions, in collaboration with Vivicta. Once the attack was over, it was quick to stabilize traffic and restore normal operation. The Norwegian Data Protection Authority and the National Security Authority \(NSM\) were notified in accordance with current procedures. The incident has not led to a security breach or personal data being compromised. 

The entire incident is now being thoroughly reviewed, in line with our routines and practices. We are constantly working closely with our operating partners to improve incident handling.

## 
Information on the way

The denial of service attack caused problems for businesses and citizens, because it was not possible for users to log in to public services at times. 

Many of our customers and system suppliers have their own obligations to their customers when the common solutions are unavailable, and it is important that we sufficiently enable them to make their own risk and consequence assessments through as good and precise information as possible. 

In retrospect, we see that it took too long before we referred to the incident as a denial of service attack. At the same time, the need to provide information about the cause must be weighed against general recommendations not to publish details about ongoing attacks, both to avoid helping the attacker and to avoid giving the person in question the effect or attention that is sought. We are now reviewing routines for status messages for when and how the cause and status are communicated, so that users and customers can get a more accurate picture of the situation more quickly – 
especially in the case of long-term incidents. 

## Further work 

The services of the Directorate of Digitalisation are part of a socially critical infrastructure. It is crucial that the solutions work for citizens and businesses, and we therefore take operational disruptions very seriously. 

Dedicated security environments in Digdir are continuously working to ensure high availability and robustness in digital services that are important to society. Together with our operating partners, we have comprehensive security mechanisms in place. At the same time, attack methods are continuously developing, so that handling this type of attack requires 
ongoing adaptations. We are working to protect ourselves as much as possible against similar attacks in the future..</p>
<p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>07:57:24</var> GMT+0</small><br><strong>Resolved</strong> -
  We are ending the outage. Customers who are still experiencing problems can contact the service desk.

You can read more about the incident here: https://www.digdir.no/felleslosninger/digdirs-felleslosninger-tilbake-i-normal-drift/8315.</p>
<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>11:03:50</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are back to normal operation.

Please contact the service desk if you are still experiencing problems..</p>
<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>07:45:37</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are changing back to yellow status for several solutions. We have received reports from several people who are unable to connect to services from data centers in various countries. 

As of now, we know that the following countries may experience problems connecting:
- Germany
- Switzerland
- Netherlands
- Belgium

We are working with our operating partner to resolve this..</p>
<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>07:02:26</var> GMT+0</small><br><strong>Monitoring</strong> -
  Status 04.08.2026 at 09:00

All solutions are back in normal operation as of approx. 01:30 tonight. 

We will keep this issue open for a while longer, and will provide more details as time goes on..</p>
<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>05:51:15</var> GMT+0</small><br><strong>Monitoring</strong> -
  Status 04.08.2026 at 07:45

As of approx. 01:26 last night, the shared solutions have been stable. We will return with more information approx. 08:30.</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>22:11:21</var> GMT+0</small><br><strong>Identified</strong> -
  Status 04.08.2026 at 00:08

Still a large number of errors in the ID-porten. Work is still underway to resolve it.

Most other solutions work, but instability and varying response times may still be experienced.

The next update will be at approximately 07:30..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>20:52:22</var> GMT+0</small><br><strong>Identified</strong> -
  Status 03.08.2026 at 22:46

Large increase in the number of errors in the ID-porten. Mitigation measures are being worked on.

Most other solutions work, but instability and varying response times may still be experienced..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>19:05:12</var> GMT+0</small><br><strong>Identified</strong> -
  Status 03.08.2026 at 21:00

Most solutions work, but instability and varying response times may still be experienced..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>16:34:18</var> GMT+0</small><br><strong>Identified</strong> -
  We are experiencing problems again from approximately 17:55.</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>14:55:23</var> GMT+0</small><br><strong>Monitoring</strong> -
  Since 01:00 on Monday, August 3, a denial of service attack (DDoS) has been ongoing against the ID-porten operated by Digdir&#039;s operating partner Vivicta. This affects several of Digdir&#039;s solutions and causes users to experience problems logging in to public services. We are working with Vivicta on measures to resolve the issue. 

As of 13:40, traffic was on the rise again, but it may take some time before all services are available and back in normal operation..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>11:53:59</var> GMT+0</small><br><strong>Monitoring</strong> -
  From approximately 1:40 PM, it appears that traffic is on the rise again on the affected routes..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>11:36:08</var> GMT+0</small><br><strong>Investigating</strong> -
  We are still working to resolve the issue. 

The next update will be at 2:30 PM unless we have something new before then..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>10:41:25</var> GMT+0</small><br><strong>Investigating</strong> -
  We are still working to resolve the issue. 

The next update will be at 1:30 PM unless we have something new before then..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>09:43:13</var> GMT+0</small><br><strong>Investigating</strong> -
  We are still working to resolve the issue. 

The next update will be at 12:30 if we don&#039;t have anything new before then..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>08:30:18</var> GMT+0</small><br><strong>Investigating</strong> -
  We are still working to resolve the issue. 

The next update will be at 11:30 AM unless we have something new before then..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>07:28:44</var> GMT+0</small><br><strong>Investigating</strong> -
  We are still working to resolve the issue. 

The next status update will be at 10:30 AM..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>05:20:49</var> GMT+0</small><br><strong>Investigating</strong> -
  Troubleshooting is still ongoing..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>01:20:09</var> GMT+0</small><br><strong>Investigating</strong> -
  The problem appears to have started around 00:50. The operating partner is working to resolve the issue, we will update when we have something new to report..</p>
<p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>22:50:26</var> GMT+0</small><br><strong>Investigating</strong> -
  There are problems with several solutions. We are investigating the problems..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 2 Aug 2026 22:50:26 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmt8ews04014m1anpecba7ltp</link>
  <guid>https://status.strise.ai/incident/cmt8ews04014m1anpecba7ltp</guid>
</item>

<item>
  <title>Monitoring alerts unable to load (V2)</title>
  <description>
    Type: Incident
    Duration: 3 hours and 38 minutes

    Affected Components: Monitoring
    Jun 30, 11:57:53 GMT+0 - Resolved - This incident has been resolved. Jun 30, 08:19:24 GMT+0 - Identified - We have identified an issue blocking the release of new monitoring alerts. We are currently investigating the root cause.

**Note:** This incident only affects customers with Monitoring V2 enabled. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 38 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>11:57:53</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>08:19:24</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified an issue blocking the release of new monitoring alerts. We are currently investigating the root cause.

**Note:** This incident only affects customers with Monitoring V2 enabled..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 30 Jun 2026 08:19:24 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmr0dlcxw05sc0rrrnwc9ji8u</link>
  <guid>https://status.strise.ai/incident/cmr0dlcxw05sc0rrrnwc9ji8u</guid>
</item>

<item>
  <title>ID-porten, Contact and reservation register, Machine porten, MinID, eDissemination, ELMA, eInnsyn, Employee porten, Self-service solutions, Altinn - Unavailable from 1:16 PM - 8:05 AM</title>
  <description>
    Type: Incident
    Duration: 21 days, 7 hours and 31 minutes

    Affected Components: Digdir → Maskinporten
    Jun 23, 07:16:12 GMT+0 - Resolved - **Digdir&#039;s shared solutions back in normal operation after DDoS attack**

On Saturday, several of Digdir&#039;s shared solutions experienced complete or partial unavailability as a result of a denial of service attack (DDoS attack). The attack targeted ID-porten, through our supplier Vivicta&#039;s network infrastructure. All services were restored and in normal operation as of Monday at 07:30.

DDoS attacks overload digital services with artificial network traffic to make them unavailable.

The denial of service attack caused the services to be partially or completely unavailable for a period of time, but has not led to a security breach. No personal data is compromised, but the Norwegian Data Protection Authority has been routinely notified as a result of limited access to services that process personal data. The National Security Authority has also been notified in line with our routines related to such incidents.

— The services of the Digital Directorate are part of a socially critical infrastructure. We therefore take operational disruptions very seriously, and have good practices for this type of handling. Our response this weekend shows that the contingency plan is working well: The denial of service attack was identified, in close cooperation with Vivicta we were able to limit the consequences, and together we restored the services to normal operation. We are now conducting a thorough evaluation of the incident, in line with our routines, says Department Director Nina Munthe Olsen.

Facts about the incident:

* Duration: Saturday at 1:16 PM to Monday morning at 7:30 AM.
* Affected services: ID-porten, MinID, Maskinporten, Contact and reservation register, eFormidling, ELMA, eInnsyn, Ansattporten, Self-service solutions. Jun 22, 08:06:05 GMT+0 - Resolved - All services are back to normal as of 07:30, Monday, June 22. 

Solutions were available again as of 08:05 Sunday, and as of 18:20 Sunday evening, we had increased stability and good access to services.

Information on the root cause will be provided. Jun 21, 19:51:51 GMT+0 - Monitoring - Status at 21:45

After solutions were restored at 08:05, as of 18:20 tonight we have experienced increased stability and good access to services. We are still monitoring the situation closely. Jun 21, 14:38:19 GMT+0 - Monitoring - Status at 16:35

Services partially back up as of 08:05, but there is still instability, and some will still experience service outages. 

Network provider is still working on further bug fixes. Jun 21, 11:17:06 GMT+0 - Monitoring - Status at 13:15

As previously informed, as of 08:05, services are partially back up, but there is still instability, and some will still experience service unavailability. 

The network provider is still working on further bug fixes. Jun 21, 09:22:19 GMT+0 - Monitoring - Status as of 11:20

As of 08:05, services are partially back up, but there is still instability, and some will still experience service unavailability. The provider is continuing to work on further bug fixes. Jun 21, 06:50:03 GMT+0 - Monitoring - Status at 08:48: Solutions are available again. More information to come. Jun 21, 06:41:36 GMT+0 - Investigating - Status at 08:40

Solutions are still unavailable: ID-porten, Contact and reservation register, Maskinporten, MinID, ELMA, eInnsyn, Ansatporten, Self-service solutions

Troubleshooting is still ongoing at the supplier. Jun 21, 05:38:22 GMT+0 - Investigating - Status as of 07:35

Solutions are still unavailable. 
Troubleshooting is still ongoing at the vendor. Jun 21, 03:43:19 GMT+0 - Investigating - We observed that traffic was not going through the solutions after 05:16. 

Traffic was back to normal in the period 03:53 - 05:16 Jun 21, 03:03:16 GMT+0 - Investigating - As of 03:53, traffic has returned to normal. 

We continue to monitor the solutions. Jun 20, 22:40:18 GMT+0 - Investigating - Status as of 00:40

Solutions are still unavailable. 

Troubleshooting is still ongoing at the supplier and will continue through the night.

Next status: Probably Sunday morning. Jun 20, 21:16:56 GMT+0 - Investigating - Status as of 23:10: 

Solutions are still unavailable due to network issues. 

Downtime today has been from 13:16 - 16:58. And then from 17:55. 

Digdir&#039;s network service provider has located the area where the problems are. Continuous work is being done to troubleshoot and fix the problems. Jun 20, 19:24:31 GMT+0 - Investigating - We are continuing to investigate this issue. Jun 20, 19:22:36 GMT+0 - Investigating - Status 21:20:

Solutions are still unavailable.

Troubleshooting and bug fixes are still ongoing at the vendor. We will provide updated information in the next status update. Jun 20, 18:39:11 GMT+0 - Investigating - Status 20:35:

Solutions are still unavailable.

Troubleshooting and corrections are still ongoing at the vendor. Jun 20, 17:34:03 GMT+0 - Investigating - Status as of 19:30

Solutions are still unavailable. 

New status will be provided when we have more information. Jun 20, 16:50:56 GMT+0 - Investigating - Status as of 18:50:

Solutions are still unavailable again from 17:55 Jun 20, 16:03:39 GMT+0 - Investigating - We are experiencing problems again from 17:55 with the availability of solutions. 
Applies to ID-porten, Contact and reservation register, Maskinporten, MinID, ELMA, eInnsyn, Ansatporten, Self-service solutions, Altinn Jun 20, 15:19:24 GMT+0 - Monitoring - ID-porten, Contact and reservation register, Maskinporten, MinID, ELMA, eInnsyn, Ansattporten, Self-service solutions and Altinn are available again from 16:58

Downtime was in the period 13:16 - 16:58. 

The problems were due to network problems with a subcontractor. Jun 20, 15:03:18 GMT+0 - Investigating - As of 16:58, we are experiencing traffic returning to normal. 

We continue to monitor the solutions. 

We will provide an update as soon as we can fully verify that the solutions are back to normal. Jun 20, 14:26:23 GMT+0 - Investigating - Status as of 16:25

Solutions are still unavailable. Jun 20, 13:29:56 GMT+0 - Investigating - Status as of 15:27 
Solutions are still unavailable. Jun 20, 12:49:42 GMT+0 - Investigating - Status as of 14:50
Still unavailable: ID-porten, Contact and reservation register, Maskinporten, MinID, ELMA, eInnsyn, Employee portal, Self-service solutions, Altinn

New status will be provided as soon as we have more information. Jun 20, 12:33:37 GMT+0 - Investigating - Status at 14:32
Still unavailable: ID-porten, Contact and reservation register, Maskinporten, MinID, ELMA, eInnsyn, Ansatporten, Self-service solutions, Altinn

It is currently unknown how long it will take before solutions are available again. Jun 20, 12:10:31 GMT+0 - Investigating - Status at 14:08:

Still unavailable: 
ID-porten, Contact and reservation register, Machine porten, MinID, ELMA, eInnsyn, Employee porten, Self-service solutions. Jun 20, 11:34:34 GMT+0 - Investigating - Since 13:16 several solutions have been unavailable.
This applies to the ID-porten, the Contact and Reservation Register, the Machine Porten, MinID, ELMA, eInnsyn, the Employee Porten, Self-service solutions Jun 20, 11:32:57 GMT+0 - Investigating - We are continuing to investigate this issue. Jun 20, 11:29:35 GMT+0 - Investigating - We investigate problems with multiple solutions. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 days, 7 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>07:16:12</var> GMT+0</small><br><strong>Resolved</strong> -
  **Digdir&#039;s shared solutions back in normal operation after DDoS attack**

On Saturday, several of Digdir&#039;s shared solutions experienced complete or partial unavailability as a result of a denial of service attack (DDoS attack). The attack targeted ID-porten, through our supplier Vivicta&#039;s network infrastructure. All services were restored and in normal operation as of Monday at 07:30.

DDoS attacks overload digital services with artificial network traffic to make them unavailable.

The denial of service attack caused the services to be partially or completely unavailable for a period of time, but has not led to a security breach. No personal data is compromised, but the Norwegian Data Protection Authority has been routinely notified as a result of limited access to services that process personal data. The National Security Authority has also been notified in line with our routines related to such incidents.

— The services of the Digital Directorate are part of a socially critical infrastructure. We therefore take operational disruptions very seriously, and have good practices for this type of handling. Our response this weekend shows that the contingency plan is working well: The denial of service attack was identified, in close cooperation with Vivicta we were able to limit the consequences, and together we restored the services to normal operation. We are now conducting a thorough evaluation of the incident, in line with our routines, says Department Director Nina Munthe Olsen.

Facts about the incident:

* Duration: Saturday at 1:16 PM to Monday morning at 7:30 AM.
* Affected services: ID-porten, MinID, Maskinporten, Contact and reservation register, eFormidling, ELMA, eInnsyn, Ansattporten, Self-service solutions..</p>
<p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>08:06:05</var> GMT+0</small><br><strong>Resolved</strong> -
  All services are back to normal as of 07:30, Monday, June 22. 

Solutions were available again as of 08:05 Sunday, and as of 18:20 Sunday evening, we had increased stability and good access to services.

Information on the root cause will be provided..</p>
<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>19:51:51</var> GMT+0</small><br><strong>Monitoring</strong> -
  Status at 21:45

After solutions were restored at 08:05, as of 18:20 tonight we have experienced increased stability and good access to services. We are still monitoring the situation closely..</p>
<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>14:38:19</var> GMT+0</small><br><strong>Monitoring</strong> -
  Status at 16:35

Services partially back up as of 08:05, but there is still instability, and some will still experience service outages. 

Network provider is still working on further bug fixes..</p>
<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>11:17:06</var> GMT+0</small><br><strong>Monitoring</strong> -
  Status at 13:15

As previously informed, as of 08:05, services are partially back up, but there is still instability, and some will still experience service unavailability. 

The network provider is still working on further bug fixes..</p>
<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>09:22:19</var> GMT+0</small><br><strong>Monitoring</strong> -
  Status as of 11:20

As of 08:05, services are partially back up, but there is still instability, and some will still experience service unavailability. The provider is continuing to work on further bug fixes..</p>
<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>06:50:03</var> GMT+0</small><br><strong>Monitoring</strong> -
  Status at 08:48: Solutions are available again. More information to come..</p>
<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>06:41:36</var> GMT+0</small><br><strong>Investigating</strong> -
  Status at 08:40

Solutions are still unavailable: ID-porten, Contact and reservation register, Maskinporten, MinID, ELMA, eInnsyn, Ansatporten, Self-service solutions

Troubleshooting is still ongoing at the supplier..</p>
<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>05:38:22</var> GMT+0</small><br><strong>Investigating</strong> -
  Status as of 07:35

Solutions are still unavailable. 
Troubleshooting is still ongoing at the vendor..</p>
<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>03:43:19</var> GMT+0</small><br><strong>Investigating</strong> -
  We observed that traffic was not going through the solutions after 05:16. 

Traffic was back to normal in the period 03:53 - 05:16.</p>
<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>03:03:16</var> GMT+0</small><br><strong>Investigating</strong> -
  As of 03:53, traffic has returned to normal. 

We continue to monitor the solutions..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>22:40:18</var> GMT+0</small><br><strong>Investigating</strong> -
  Status as of 00:40

Solutions are still unavailable. 

Troubleshooting is still ongoing at the supplier and will continue through the night.

Next status: Probably Sunday morning..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>21:16:56</var> GMT+0</small><br><strong>Investigating</strong> -
  Status as of 23:10: 

Solutions are still unavailable due to network issues. 

Downtime today has been from 13:16 - 16:58. And then from 17:55. 

Digdir&#039;s network service provider has located the area where the problems are. Continuous work is being done to troubleshoot and fix the problems..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>19:24:31</var> GMT+0</small><br><strong>Investigating</strong> -
  We are continuing to investigate this issue..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>19:22:36</var> GMT+0</small><br><strong>Investigating</strong> -
  Status 21:20:

Solutions are still unavailable.

Troubleshooting and bug fixes are still ongoing at the vendor. We will provide updated information in the next status update..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>18:39:11</var> GMT+0</small><br><strong>Investigating</strong> -
  Status 20:35:

Solutions are still unavailable.

Troubleshooting and corrections are still ongoing at the vendor..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>17:34:03</var> GMT+0</small><br><strong>Investigating</strong> -
  Status as of 19:30

Solutions are still unavailable. 

New status will be provided when we have more information..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>16:50:56</var> GMT+0</small><br><strong>Investigating</strong> -
  Status as of 18:50:

Solutions are still unavailable again from 17:55.</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>16:03:39</var> GMT+0</small><br><strong>Investigating</strong> -
  We are experiencing problems again from 17:55 with the availability of solutions. 
Applies to ID-porten, Contact and reservation register, Maskinporten, MinID, ELMA, eInnsyn, Ansatporten, Self-service solutions, Altinn.</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>15:19:24</var> GMT+0</small><br><strong>Monitoring</strong> -
  ID-porten, Contact and reservation register, Maskinporten, MinID, ELMA, eInnsyn, Ansattporten, Self-service solutions and Altinn are available again from 16:58

Downtime was in the period 13:16 - 16:58. 

The problems were due to network problems with a subcontractor..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>15:03:18</var> GMT+0</small><br><strong>Investigating</strong> -
  As of 16:58, we are experiencing traffic returning to normal. 

We continue to monitor the solutions. 

We will provide an update as soon as we can fully verify that the solutions are back to normal..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>14:26:23</var> GMT+0</small><br><strong>Investigating</strong> -
  Status as of 16:25

Solutions are still unavailable..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>13:29:56</var> GMT+0</small><br><strong>Investigating</strong> -
  Status as of 15:27 
Solutions are still unavailable..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>12:49:42</var> GMT+0</small><br><strong>Investigating</strong> -
  Status as of 14:50
Still unavailable: ID-porten, Contact and reservation register, Maskinporten, MinID, ELMA, eInnsyn, Employee portal, Self-service solutions, Altinn

New status will be provided as soon as we have more information..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>12:33:37</var> GMT+0</small><br><strong>Investigating</strong> -
  Status at 14:32
Still unavailable: ID-porten, Contact and reservation register, Maskinporten, MinID, ELMA, eInnsyn, Ansatporten, Self-service solutions, Altinn

It is currently unknown how long it will take before solutions are available again..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>12:10:31</var> GMT+0</small><br><strong>Investigating</strong> -
  Status at 14:08:

Still unavailable: 
ID-porten, Contact and reservation register, Machine porten, MinID, ELMA, eInnsyn, Employee porten, Self-service solutions..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>11:34:34</var> GMT+0</small><br><strong>Investigating</strong> -
  Since 13:16 several solutions have been unavailable.
This applies to the ID-porten, the Contact and Reservation Register, the Machine Porten, MinID, ELMA, eInnsyn, the Employee Porten, Self-service solutions.</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>11:32:57</var> GMT+0</small><br><strong>Investigating</strong> -
  We are continuing to investigate this issue..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>11:29:35</var> GMT+0</small><br><strong>Investigating</strong> -
  We investigate problems with multiple solutions..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 20 Jun 2026 11:34:34 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmt8ewrzy014j1anpipvndin0</link>
  <guid>https://status.strise.ai/incident/cmt8ewrzy014j1anpipvndin0</guid>
</item>

<item>
  <title>ID-porten, Machineporten, Employeeporten, KRR, eFormidling, MinID, eFormidling, eInnsyn, ELMA - scheduled maintenance June 11 at 23:00 - 02:00</title>
  <description>
    Type: Maintenance
    Duration: 3 hours

    Affected Components: Digdir → Maskinporten
    Jun 12, 00:00:10 GMT+0 - Completed - The scheduled maintenance has been completed. Jun 11, 21:00:08 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun 11, 20:00:14 GMT+0 - Planned - Maintenance will begin as scheduled in 60 minutes. Jun 9, 06:55:41 GMT+0 - Planned - Maintenance is planned for June 11th at 23:00 - 02:00 CET. 

This affects the solutions ID-porten, Maskinporten, Ansattporten, KRR, eFormidling, MinID, eFormidling, eInnsyn, ELMA and self-service. 

Approximately 10-15 minutes of downtime is expected during the maintenance period. 
  </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>Jun <var data-var='date'> 12</var>, <var data-var='time'>00:00:10</var> GMT+0</small><br><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>21:00:08</var> GMT+0</small><br><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>20:00:14</var> GMT+0</small><br><strong>Planned</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>06:55:41</var> GMT+0</small><br><strong>Planned</strong> -
  Maintenance is planned for June 11th at 23:00 - 02:00 CET. 

This affects the solutions ID-porten, Maskinporten, Ansattporten, KRR, eFormidling, MinID, eFormidling, eInnsyn, ELMA and self-service. 

Approximately 10-15 minutes of downtime is expected during the maintenance period..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 11 Jun 2026 21:00:00 +0000</pubDate>
  <link>https://status.strise.ai/maintenance/cmt8ews4w014n1anpgm4qrb4i</link>
  <guid>https://status.strise.ai/maintenance/cmt8ews4w014n1anpgm4qrb4i</guid>
</item>

<item>
  <title>More monitoring alerts than usual today</title>
  <description>
    Type: Incident
    Duration: 1 day and 33 minutes

    Affected Components: Monitoring
    Jun 12, 13:52:21 GMT+0 - Resolved - This incident has been resolved. Jun 11, 13:19:24 GMT+0 - Monitoring - There might be more alerts than usual today. We&#039;ve restored screening coverage for a small group of companies and improved the precision of our sanctions matching. Accumulated and corrected changes are being delivered as a one-time batch.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day and 33 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>13:52:21</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 11</var>, <var data-var='time'>13:19:24</var> GMT+0</small><br><strong>Monitoring</strong> -
  There might be more alerts than usual today. We&#039;ve restored screening coverage for a small group of companies and improved the precision of our sanctions matching. Accumulated and corrected changes are being delivered as a one-time batch. .</p>
]]>
  </content:encoded>
  <pubDate>Thu, 11 Jun 2026 13:19:24 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmq9ixzl0007qqswqrn3dvzp4</link>
  <guid>https://status.strise.ai/incident/cmq9ixzl0007qqswqrn3dvzp4</guid>
</item>

<item>
  <title>Elevated errors in review processing</title>
  <description>
    Type: Incident
    Duration: 8 hours and 45 minutes

    Affected Components: Application, API
    Jun 10, 18:35:00 GMT+0 - Resolved - This incident has been resolved. Jun 10, 09:54:58 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 10, 09:49:35 GMT+0 - Investigating -  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>18:35:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>09:54:58</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Jun <var data-var='date'> 10</var>, <var data-var='time'>09:49:35</var> GMT+0</small><br><strong>Investigating</strong> -
  .</p>
]]>
  </content:encoded>
  <pubDate>Wed, 10 Jun 2026 09:49:35 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmq7w0an2015kpflr6orl7u40</link>
  <guid>https://status.strise.ai/incident/cmq7w0an2015kpflr6orl7u40</guid>
</item>

<item>
  <title>Global companies misssing from Portfolio</title>
  <description>
    Type: Incident
    Duration: 5 hours and 16 minutes

    Affected Components: Application, Sandbox, Monitoring, API
    Jun 9, 14:10:49 GMT+0 - Resolved - This incident has been resolved and all portfolios and monitoring alerts should work as normal. Jun 9, 12:04:27 GMT+0 - Identified - All companies should showing in the portfolio. We are still working to resolve the incorrrectly sent monitoring alerts Jun 9, 08:55:05 GMT+0 - Identified - Some global companies may be missing from team portfolios. Empty monitoring alerts have been created for these missing global companies The issue has been identified and we are working on a fix. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 16 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    <p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>14:10:49</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved and all portfolios and monitoring alerts should work as normal..</p>
<p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>12:04:27</var> GMT+0</small><br><strong>Identified</strong> -
  All companies should showing in the portfolio. We are still working to resolve the incorrrectly sent monitoring alerts.</p>
<p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>08:55:05</var> GMT+0</small><br><strong>Identified</strong> -
  Some global companies may be missing from team portfolios. Empty monitoring alerts have been created for these missing global companies The issue has been identified and we are working on a fix..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 9 Jun 2026 08:55:05 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmq6emcpg0347qn9wr6sj4a2l</link>
  <guid>https://status.strise.ai/incident/cmq6emcpg0347qn9wr6sj4a2l</guid>
</item>

<item>
  <title>Application, API outage</title>
  <description>
    Type: Incident
    

    Affected Components: Application, API
    Jun 3, 13:23:38 GMT+0 - Resolved - Application, API is now operational! This update was created by an automated monitoring service. Jun 3, 13:23:18 GMT+0 - Investigating - Application, API cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>13:23:38</var> GMT+0</small><br><strong>Resolved</strong> -
  Application, API is now operational! This update was created by an automated monitoring service..</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>13:23:18</var> GMT+0</small><br><strong>Investigating</strong> -
  Application, API cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 3 Jun 2026 13:23:18 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmpy3k5v00103qosxux4uhv98</link>
  <guid>https://status.strise.ai/incident/cmpy3k5v00103qosxux4uhv98</guid>
</item>

<item>
  <title>ID port, Employee port, Machine port: cases of occasional short timeout</title>
  <description>
    Type: Incident
    Duration: 13 days, 2 hours and 20 minutes

    Affected Components: Digdir → Maskinporten
    May 28, 20:29:05 GMT+0 - Resolved - This incident has been resolved. May 28, 15:14:45 GMT+0 - Monitoring - We have observed and received reports today that you may occasionally experience short timeouts against the Machine Port in particular, but also the ID Port and the Employee Port. 

This appears to be an issue outside of our solutions, and is likely due to issues with some Internet Service Providers (ISPs). 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 13 days, 2 hours and 20 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 28</var>, <var data-var='time'>20:29:05</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>May <var data-var='date'> 28</var>, <var data-var='time'>15:14:45</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have observed and received reports today that you may occasionally experience short timeouts against the Machine Port in particular, but also the ID Port and the Employee Port. 

This appears to be an issue outside of our solutions, and is likely due to issues with some Internet Service Providers (ISPs)..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 28 May 2026 15:14:45 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmt8ews02014k1anp2na47pw2</link>
  <guid>https://status.strise.ai/incident/cmt8ews02014k1anp2na47pw2</guid>
</item>

<item>
  <title>App slowness</title>
  <description>
    Type: Incident
    

    Affected Components: Application
    May 20, 08:31:33 GMT+0 - Resolved -  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 20</var>, <var data-var='time'>08:31:33</var> GMT+0</small><br><strong>Resolved</strong> -
  .</p>
]]>
  </content:encoded>
  <pubDate>Wed, 20 May 2026 08:31:33 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmpdsz1lg01htqim7gyneqgrz</link>
  <guid>https://status.strise.ai/incident/cmpdsz1lg01htqim7gyneqgrz</guid>
</item>

<item>
  <title>Issues with document upload</title>
  <description>
    Type: Incident
    Duration: 45 minutes

    Affected Components: Application
    Apr 30, 14:44:54 GMT+0 - Resolved - This incident has been resolved. Apr 30, 14:00:00 GMT+0 - Identified - Issue is identified and a fix will be deployed shortly 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 45 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>14:44:54</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  Issue is identified and a fix will be deployed shortly.</p>
]]>
  </content:encoded>
  <pubDate>Thu, 30 Apr 2026 14:00:00 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmolkq4230dy1zrsonzoa7xpj</link>
  <guid>https://status.strise.ai/incident/cmolkq4230dy1zrsonzoa7xpj</guid>
</item>

<item>
  <title>Empty monitoring alerts (V2)</title>
  <description>
    Type: Incident
    Duration: 4 hours and 3 minutes

    Affected Components: Monitoring
    Apr 29, 12:48:11 GMT+0 - Resolved - This incident has been resolved. Apr 29, 11:42:16 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 29, 09:50:59 GMT+0 - Identified - We are continuing to work on a fix for this incident. Apr 29, 08:45:33 GMT+0 - Investigating - We have identified an issue with monitoring alerts lacking any data. We are currently investigating the root cause.

**Note:** This incident only affects customers with Monitoring V2 enabled. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 3 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>12:48:11</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>11:42:16</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>09:50:59</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>08:45:33</var> GMT+0</small><br><strong>Investigating</strong> -
  We have identified an issue with monitoring alerts lacking any data. We are currently investigating the root cause.

**Note:** This incident only affects customers with Monitoring V2 enabled..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 29 Apr 2026 08:45:33 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmojt86k3001s3hu95zry3iqn</link>
  <guid>https://status.strise.ai/incident/cmojt86k3001s3hu95zry3iqn</guid>
</item>

<item>
  <title>Monitoring alerts unable to load (V2)</title>
  <description>
    Type: Incident
    Duration: 45 minutes

    Affected Components: Monitoring
    Apr 17, 08:47:34 GMT+0 - Resolved - This incident has been resolved. Apr 17, 08:14:40 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 17, 08:02:20 GMT+0 - Investigating - We have identified an issue with displaying new monitoring alerts. We are currently investigating the root cause.

**Note:** This incident only affects customers with Monitoring V2 enabled. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 45 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>08:47:34</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>08:14:40</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>08:02:20</var> GMT+0</small><br><strong>Investigating</strong> -
  We have identified an issue with displaying new monitoring alerts. We are currently investigating the root cause.

**Note:** This incident only affects customers with Monitoring V2 enabled..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 17 Apr 2026 08:02:20 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmo2medrr0c6z13ntthstvr54</link>
  <guid>https://status.strise.ai/incident/cmo2medrr0c6z13ntthstvr54</guid>
</item>

<item>
  <title>Degraded data freshness for Finnish and Swedish UBO data</title>
  <description>
    Type: Incident
    Duration: 10 days and 22 hours

    Affected Components: Data Freshness
    Apr 8, 09:00:00 GMT+0 - Resolved - This incident has been resolved. Apr 8, 07:11:14 GMT+0 - Identified - We received a full dump of Finnish data yesterday but are still not receiving delta updates. We are continuing to push our provider to solve this issue as quickly as possible. Mar 28, 11:00:00 GMT+0 - Identified - No new updates received on Finnish and Swedish UBOs since 30th and 28th of March, respectively. We&#039;ve reported the issue to our data vendor and are awaiting a fix on their end. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 days and 22 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>07:11:14</var> GMT+0</small><br><strong>Identified</strong> -
  We received a full dump of Finnish data yesterday but are still not receiving delta updates. We are continuing to push our provider to solve this issue as quickly as possible..</p>
<p><small>Mar <var data-var='date'> 28</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  No new updates received on Finnish and Swedish UBOs since 30th and 28th of March, respectively. We&#039;ve reported the issue to our data vendor and are awaiting a fix on their end..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 28 Mar 2026 11:00:00 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmnfxeq4o00ry66yxws7h3pvu</link>
  <guid>https://status.strise.ai/incident/cmnfxeq4o00ry66yxws7h3pvu</guid>
</item>

<item>
  <title>Sandbox unavailable</title>
  <description>
    Type: Incident
    Duration: 4 hours and 2 minutes

    Affected Components: Sandbox
    Mar 24, 12:02:29 GMT+0 - Resolved - This incident has been resolved. Mar 24, 11:26:39 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 24, 08:00:28 GMT+0 - Identified - We are continuing to work on a fix for this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 2 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>12:02:29</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>11:26:39</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>08:00:28</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 24 Mar 2026 08:00:28 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmn4e7vw2080nia7o9ce91q7c</link>
  <guid>https://status.strise.ai/incident/cmn4e7vw2080nia7o9ce91q7c</guid>
</item>

<item>
  <title>Application, API outage</title>
  <description>
    Type: Incident
    

    Affected Components: Application, API
    Mar 23, 09:06:10 GMT+0 - Resolved - Application, API is now operational! This update was created by an automated monitoring service. Mar 23, 09:06:00 GMT+0 - Investigating - Application, API cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>09:06:10</var> GMT+0</small><br><strong>Resolved</strong> -
  Application, API is now operational! This update was created by an automated monitoring service..</p>
<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>09:06:00</var> GMT+0</small><br><strong>Investigating</strong> -
  Application, API cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 23 Mar 2026 09:06:00 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmn2yny17106a4iurxii13u18</link>
  <guid>https://status.strise.ai/incident/cmn2yny17106a4iurxii13u18</guid>
</item>

<item>
  <title>Application, API outage</title>
  <description>
    Type: Incident
    

    Affected Components: Application, API
    Mar 23, 09:05:39 GMT+0 - Resolved - Application, API is now operational! This update was created by an automated monitoring service. Mar 23, 09:05:34 GMT+0 - Investigating - Application, API cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>09:05:39</var> GMT+0</small><br><strong>Resolved</strong> -
  Application, API is now operational! This update was created by an automated monitoring service..</p>
<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>09:05:34</var> GMT+0</small><br><strong>Investigating</strong> -
  Application, API cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 23 Mar 2026 09:05:34 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmn2ynegp10k9wzchxsnzffmd</link>
  <guid>https://status.strise.ai/incident/cmn2ynegp10k9wzchxsnzffmd</guid>
</item>

<item>
  <title>Application, API outage</title>
  <description>
    Type: Incident
    

    Affected Components: Application, API
    Mar 23, 09:05:14 GMT+0 - Resolved - Application, API is now operational! This update was created by an automated monitoring service. Mar 23, 09:05:04 GMT+0 - Investigating - Application, API cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>09:05:14</var> GMT+0</small><br><strong>Resolved</strong> -
  Application, API is now operational! This update was created by an automated monitoring service..</p>
<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>09:05:04</var> GMT+0</small><br><strong>Investigating</strong> -
  Application, API cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 23 Mar 2026 09:05:04 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmn2ymr5g10e4hvwrewuzusdi</link>
  <guid>https://status.strise.ai/incident/cmn2ymr5g10e4hvwrewuzusdi</guid>
</item>

<item>
  <title>Application, API outage</title>
  <description>
    Type: Incident
    

    Affected Components: Application, API
    Mar 23, 09:04:42 GMT+0 - Resolved - Application, API is now operational! This update was created by an automated monitoring service. Mar 23, 09:04:30 GMT+0 - Investigating - Application, API cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>09:04:42</var> GMT+0</small><br><strong>Resolved</strong> -
  Application, API is now operational! This update was created by an automated monitoring service..</p>
<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>09:04:30</var> GMT+0</small><br><strong>Investigating</strong> -
  Application, API cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 23 Mar 2026 09:04:30 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmn2ym10610d3hvwrxbeqhavd</link>
  <guid>https://status.strise.ai/incident/cmn2ym10610d3hvwrxbeqhavd</guid>
</item>

<item>
  <title>Application, API outage</title>
  <description>
    Type: Incident
    

    Affected Components: Application, API
    Mar 23, 09:04:17 GMT+0 - Resolved - Application, API is now operational! This update was created by an automated monitoring service. Mar 23, 09:04:07 GMT+0 - Investigating - Application, API cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>09:04:17</var> GMT+0</small><br><strong>Resolved</strong> -
  Application, API is now operational! This update was created by an automated monitoring service..</p>
<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>09:04:07</var> GMT+0</small><br><strong>Investigating</strong> -
  Application, API cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 23 Mar 2026 09:04:07 +0000</pubDate>
  <link>https://status.strise.ai/incident/cmn2ylj4a101q77usvib7pir9</link>
  <guid>https://status.strise.ai/incident/cmn2ylj4a101q77usvib7pir9</guid>
</item>

<item>
  <title>Database migration</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Application, API
    Aug 31, 14:20:24 GMT+0 - Completed - The scheduled maintenance has been completed. Aug 31, 14:17:06 GMT+0 - Identified - Verification is currently underway for the maintenance items. Aug 31, 12:20:23 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug 31, 11:20:21 GMT+0 - Identified - Maintenance will begin as scheduled in 60 minutes. Aug 27, 12:21:19 GMT+0 - Identified - We will be undergoing database migration during this time. Estimated downtime of the app and api is about 40 minutes. 
  </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>Aug <var data-var='date'> 31</var>, <var data-var='time'>14:20:24</var> GMT+0</small><br><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>14:17:06</var> GMT+0</small><br><strong>Identified</strong> -
  Verification is currently underway for the maintenance items..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>12:20:23</var> GMT+0</small><br><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>11:20:21</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>12:21:19</var> GMT+0</small><br><strong>Identified</strong> -
  We will be undergoing database migration during this time. Estimated downtime of the app and api is about 40 minutes..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 31 Aug 2025 12:20:00 +0000</pubDate>
  <link>https://status.strise.ai/maintenance/cmk6q41zc00ktmiqg52mo4klv-t4q3n5z9dmxz</link>
  <guid>https://status.strise.ai/maintenance/cmk6q41zc00ktmiqg52mo4klv-t4q3n5z9dmxz</guid>
</item>

<item>
  <title>Scheduled maintenance on NO ownership data</title>
  <description>
    Type: Maintenance
    Duration: 8 hours

    Affected Components: Application
    May 27, 22:15:02 GMT+0 - Completed - The scheduled maintenance has been completed. May 27, 14:15:02 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. May 27, 13:15:04 GMT+0 - Identified - Maintenance will begin as scheduled in 60 minutes. May 27, 13:10:35 GMT+0 - Identified - We will be undergoing scheduled maintenance during this time. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 8 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 27</var>, <var data-var='time'>22:15:02</var> GMT+0</small><br><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>14:15:02</var> GMT+0</small><br><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>13:15:04</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>May <var data-var='date'> 27</var>, <var data-var='time'>13:10:35</var> GMT+0</small><br><strong>Identified</strong> -
  We will be undergoing scheduled maintenance during this time..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 27 May 2024 14:15:00 +0000</pubDate>
  <link>https://status.strise.ai/maintenance/cmk6q41zf00obmiqg7mlx0prh-c4rj9kn6whjl</link>
  <guid>https://status.strise.ai/maintenance/cmk6q41zf00obmiqg7mlx0prh-c4rj9kn6whjl</guid>
</item>

<item>
  <title>Database upgrade</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: API
    May 8, 16:43:35 GMT+0 - Completed - The scheduled maintenance has been completed. May 8, 16:00:02 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. May 8, 15:00:07 GMT+0 - Identified - Maintenance will begin as scheduled in 60 minutes. May 2, 09:30:38 GMT+0 - Identified - We will be doing some maintenance on the database infrastructure used for private persons. All other services should be 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>May <var data-var='date'> 8</var>, <var data-var='time'>16:43:35</var> GMT+0</small><br><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>16:00:02</var> GMT+0</small><br><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>15:00:07</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>May <var data-var='date'> 2</var>, <var data-var='time'>09:30:38</var> GMT+0</small><br><strong>Identified</strong> -
  We will be doing some maintenance on the database infrastructure used for private persons. All other services should be unaffected..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 8 May 2024 16:00:00 +0000</pubDate>
  <link>https://status.strise.ai/maintenance/cmk6q41zf00ojmiqgd5oo57lc-rv4xwqfzmdz0</link>
  <guid>https://status.strise.ai/maintenance/cmk6q41zf00ojmiqgd5oo57lc-rv4xwqfzmdz0</guid>
</item>

<item>
  <title>Move API traffic to new load balancer</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: API
    Jan 18, 21:01:06 GMT+0 - Completed - The scheduled maintenance has been completed. Jan 18, 20:00:34 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan 18, 19:00:13 GMT+0 - Identified - Maintenance will begin as scheduled in 60 minutes. Jan 15, 13:54:48 GMT+0 - Identified - API might be unavailable during this window. 
  </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>Jan <var data-var='date'> 18</var>, <var data-var='time'>21:01:06</var> GMT+0</small><br><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Jan <var data-var='date'> 18</var>, <var data-var='time'>20:00:34</var> GMT+0</small><br><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Jan <var data-var='date'> 18</var>, <var data-var='time'>19:00:13</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>13:54:48</var> GMT+0</small><br><strong>Identified</strong> -
  API might be unavailable during this window..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 18 Jan 2024 20:00:00 +0000</pubDate>
  <link>https://status.strise.ai/maintenance/cmk6q41zg00r0miqg1y3a9tus-mz40f6xj0xgx</link>
  <guid>https://status.strise.ai/maintenance/cmk6q41zg00r0miqg1y3a9tus-mz40f6xj0xgx</guid>
</item>

<item>
  <title>Infrastructure upgrade</title>
  <description>
    Type: Maintenance
    Duration: 4 hours

    Affected Components: Application, API
    Nov 11, 23:00:15 GMT+0 - Completed - The scheduled maintenance has been completed. Nov 11, 19:01:44 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Nov 11, 17:59:56 GMT+0 - Identified - Maintenance will begin as scheduled in 60 minutes. Nov 9, 09:40:10 GMT+0 - Identified - We will be undergoing maintenance during this time 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>23:00:15</var> GMT+0</small><br><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>19:01:44</var> GMT+0</small><br><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>17:59:56</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Nov <var data-var='date'> 9</var>, <var data-var='time'>09:40:10</var> GMT+0</small><br><strong>Identified</strong> -
  We will be undergoing maintenance during this time.</p>
]]>
  </content:encoded>
  <pubDate>Sat, 11 Nov 2023 19:00:00 +0000</pubDate>
  <link>https://status.strise.ai/maintenance/cmk6q41zg00rfmiqg779c63dz-h5l86b1c1fbx</link>
  <guid>https://status.strise.ai/maintenance/cmk6q41zg00rfmiqg779c63dz-h5l86b1c1fbx</guid>
</item>

<item>
  <title>Infrastructure upgrade</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Application, API
    Nov 7, 21:00:28 GMT+0 - Completed - The scheduled maintenance has been completed. Nov 7, 20:00:33 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Nov 7, 19:00:03 GMT+0 - Identified - Maintenance will begin as scheduled in 60 minutes. Nov 6, 10:22:32 GMT+0 - Identified - We will be undergoing scheduled maintenance during this period. 
  </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>Nov <var data-var='date'> 7</var>, <var data-var='time'>21:00:28</var> GMT+0</small><br><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>20:00:33</var> GMT+0</small><br><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>19:00:03</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Nov <var data-var='date'> 6</var>, <var data-var='time'>10:22:32</var> GMT+0</small><br><strong>Identified</strong> -
  We will be undergoing scheduled maintenance during this period..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 7 Nov 2023 20:00:00 +0000</pubDate>
  <link>https://status.strise.ai/maintenance/cmk6q41zg00rnmiqg6cs86vfs-y2sh7ph3dt8q</link>
  <guid>https://status.strise.ai/maintenance/cmk6q41zg00rnmiqg6cs86vfs-y2sh7ph3dt8q</guid>
</item>

<item>
  <title>Infrastructure upgrade</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Application, API
    Oct 28, 19:00:11 GMT+0 - Completed - The scheduled maintenance has been completed. Oct 28, 18:00:29 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct 28, 16:59:56 GMT+0 - Identified - Maintenance will begin as scheduled in 60 minutes. Oct 28, 11:48:21 GMT+0 - Identified - We will be upgrading our infrastructure during this time. 
  </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>Oct <var data-var='date'> 28</var>, <var data-var='time'>19:00:11</var> GMT+0</small><br><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>18:00:29</var> GMT+0</small><br><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>16:59:56</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>11:48:21</var> GMT+0</small><br><strong>Identified</strong> -
  We will be upgrading our infrastructure during this time..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 28 Oct 2023 18:00:00 +0000</pubDate>
  <link>https://status.strise.ai/maintenance/cmk6q41zg00rymiqggm47fsvw-803h962n9f37</link>
  <guid>https://status.strise.ai/maintenance/cmk6q41zg00rymiqggm47fsvw-803h962n9f37</guid>
</item>

<item>
  <title>Infrastructure upgrade</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Application, API
    Oct 27, 19:00:38 GMT+0 - Completed - The scheduled maintenance has been completed. Oct 27, 18:00:12 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct 27, 16:59:57 GMT+0 - Identified - Maintenance will begin as scheduled in 60 minutes. Oct 25, 17:30:56 GMT+0 - Identified - We will be undergoing maintenance during this time 
  </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>Oct <var data-var='date'> 27</var>, <var data-var='time'>19:00:38</var> GMT+0</small><br><strong>Completed</strong> -
  The scheduled maintenance has been completed..</p>
<p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>18:00:12</var> GMT+0</small><br><strong>Identified</strong> -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..</p>
<p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>16:59:57</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>17:30:56</var> GMT+0</small><br><strong>Identified</strong> -
  We will be undergoing maintenance during this time.</p>
]]>
  </content:encoded>
  <pubDate>Fri, 27 Oct 2023 18:00:00 +0000</pubDate>
  <link>https://status.strise.ai/maintenance/cmk6q41zh00s3miqgfojlasf5-ctkrpy937pgl</link>
  <guid>https://status.strise.ai/maintenance/cmk6q41zh00s3miqgfojlasf5-ctkrpy937pgl</guid>
</item>

  </channel>
  </rss>