Scalepoint Technologies Status

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

Postmortem: Our production database environment experienced an unexpected outage. A failure at the storage layer caused a loss of quorum within our production SQL Server failover cluster, impacting the majority of its nodes. As a result, all production databases became temporarily unavailable.

Our team immediately initiated recovery procedures. All affected cluster nodes have since been fully restarted, and the SQL Server cluster is fully back online and operating normally.

We are already working on preventive measures to avoid similar incidents in the future.

Resolved: This incident has been resolved.

Monitoring: Maintanence work is ongoing.

Monitoring: We are still working to resolve minor issues in backend services. Critical services are all operational.

We expect to perform related maintance work to restore remaining services tonight at 21:00. This may result in a short downtime on ClaimShop or ClaimsCORE & HUB environments.

Monitoring: Work is still ongoing. We have identified issues related BI clusters.

Monitoring: ClaimShop Self Service is back online. Work is still ongoing.

Monitoring: Many users attempting to regristrer items through ClaimShop Self Service are still experiencing issues.

Monitoring: All systems are operational again. Investigation into the issue is ongoing.

We are monitoring the effects, especially in relation to automation processes.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: ClaimShop for norwegian users is now online as well. We continue to monitor the situation.

Monitoring: Whilst many systems are back online, users may still experience degraded performance.

Users of ClaimShop NO is still experiencing major outtage.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Systems are slowly coming back online. We continue to monitor the situation.

Monitoring: A fix is being implemented. All eyes on brining systems online and monitoring the effects.

Identified: We are continuing to work on a fix for this issue.

Identified: We are continuing to work on the issue at highest priority.

Identified: Users are experiencing issues accessing and working in CORE & HUB and ClaimShop systems.

The issue is being investigated with the highest priority, and we will provide an update as soon as we have additional information to provide and/or the issue has been resolved.