Scalepoint Outage History

Started Oct 14, 2026, 07:27 AM UTC· resolved Oct 14, 2026, 08:25 AM UTC

1. investigating Oct 14, 2026, 07:27 AM UTC

   Some of our users are currently experiencing issues in ClaimShop Settlement and the Shop. 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.

2. monitoring Oct 14, 2026, 07:34 AM UTC

   Shop is operational again. We are monitoring the status.

3. resolved Oct 14, 2026, 08:25 AM UTC

   The issue has been resolved.

Read the full incident report →

Started Sep 28, 2026, 02:35 PM UTC· resolved Sep 28, 2026, 05:04 PM UTC

1. identified Sep 28, 2026, 02:35 PM UTC

   We are currently having an issue with our Jira environment that affects access to issues and requests managed there. Our IT Operations team has found the cause and is working with our provider to fix it. Your Scalepoint products and services are **not affected**. They are running normally. The issue affects only Jira. While we work on this, you can still reach us through your usual support channels, such as email or phone. We'll handle your requests as normal and add them to Jira once it's back. We'll post an update here as soon as we have one. We're sorry for any inconvenience and thank you for your patience.

2. resolved Sep 28, 2026, 05:04 PM UTC

   Jira is working again. All issues and requests are available as normal. No data was lost. Thank you for your patience while we fixed this.

Read the full incident report →

Started Sep 28, 2026, 10:44 AM UTC· resolved Sep 28, 2026, 12:43 PM UTC

1. investigating Sep 28, 2026, 10:44 AM UTC

   Some of our users are experiencing issues working in Scalepoint 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.

2. monitoring Sep 28, 2026, 10:49 AM UTC

   A fix has been implemented and we are monitoring situation.

3. monitoring Sep 28, 2026, 11:51 AM UTC

   An issue with the product Catalogue has been identified and is currently being fixed. Otherwise all systems are back at their regular operation. We will update when final issues are resolved.

4. resolved Sep 28, 2026, 12:43 PM UTC

   The incident has been resolved.

Read the full incident report →

Started Sep 28, 2026, 08:40 AM UTC· resolved Sep 28, 2026, 09:25 AM UTC

1. investigating Sep 28, 2026, 08:40 AM UTC

   Some of our users are experiencing issues working in Sandbox environments for ClaimsCORE & HUB service. 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.

2. identified Sep 28, 2026, 09:17 AM UTC

   A fix is being implemented.

3. monitoring Sep 28, 2026, 09:20 AM UTC

   Fix has been implemented. Performance may still be degraded for some users. We are monitoring results and working to resolve any errors.

4. resolved Sep 28, 2026, 09:25 AM UTC

   This inicident has been resolved.

Read the full incident report →

Started Sep 28, 2026, 06:20 AM UTC· resolved Sep 28, 2026, 07:47 AM UTC

1. investigating Sep 28, 2026, 06:20 AM UTC

   Some of our users are experiencing issues working in ClaimsCORE & HUB system. 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.

2. identified Sep 28, 2026, 06:27 AM UTC

   Issue has been identified and we are working to resolve it.

3. monitoring Sep 28, 2026, 06:52 AM UTC

   A fix has been put in place and we are monitoring results.

4. resolved Sep 28, 2026, 07:47 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 09, 2026, 09:59 AM UTC· resolved Sep 09, 2026, 10:41 AM UTC

1. investigating Sep 09, 2026, 09:59 AM UTC

   Some claim handlers and users are unable to load Catalogue in Settlement tool. 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.

2. identified Sep 09, 2026, 10:01 AM UTC

   We have identified the cause and a working towards a solution.

3. monitoring Sep 09, 2026, 10:35 AM UTC

   A fix has been implemented. We are monitoring the results.

4. resolved Sep 09, 2026, 10:41 AM UTC

   Incident has been resolved.

Read the full incident report →

Started Sep 07, 2026, 09:45 AM UTC· resolved Sep 07, 2026, 11:42 AM UTC

1. monitoring Sep 07, 2026, 09:45 AM UTC

   Some our users have experienced issues creating claims in both ClaimsCORE & HUB and Claimshop via integration. A fix was recently introduced to eliminate issues. We are monitoring the situationen 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.

2. investigating Sep 07, 2026, 11:11 AM UTC

   We are still seeing some errors following latest fix. Work to resolve these issues is ongoing.

3. monitoring Sep 07, 2026, 11:17 AM UTC

   A fix has been implemented that should resolve the errors we still observed. We continue to monitor situation.

4. resolved Sep 07, 2026, 11:42 AM UTC

   Incident has been resolved.

Read the full incident report →

Started Aug 27, 2026, 11:07 AM UTC· resolved Aug 27, 2026, 01:16 PM UTC

1. investigating Aug 27, 2026, 11:07 AM UTC

   WE have identified an issue where Scalepoint ID is not available. Users get a '404 not found'

2. investigating Aug 27, 2026, 11:17 AM UTC

   Issue is starting to affect main systems, so many users will experience partial outages.

3. identified Aug 27, 2026, 11:26 AM UTC

   The issue has been identified and our team is actively working on a fix.

4. monitoring Aug 27, 2026, 11:28 AM UTC

   We have implemented a fix and are monitoring the results closely. Please note it may take a little time for the fix to take full effect for all users.

5. monitoring Aug 27, 2026, 11:41 AM UTC

   We are still experiences issues with access to Scalepoint ID. We are working to resolve it as quickly as possible.

6. monitoring Aug 27, 2026, 11:48 AM UTC

   We've resolved the underlying issue. Please refresh your browser (or perform a hard refresh/clear cache) to ensure you're on the latest version. We'll continue monitoring and post another update shortly.

7. monitoring Aug 27, 2026, 12:05 PM UTC

   Many users still experience issues with various system. We are monitoring situationen and working to resolve any issues that may arise.

8. monitoring Aug 27, 2026, 12:32 PM UTC

   We're seeing recovery across most systems. ClaimShop claimants remain affected, and we're continuing to work on this. Next update to follow.

9. resolved Aug 27, 2026, 01:16 PM UTC

   Incident has been resolved.

Read the full incident report →

Started Aug 19, 2026, 07:09 AM UTC· resolved Aug 19, 2026, 07:27 AM UTC

1. investigating Aug 19, 2026, 07:09 AM UTC

   Some of our users are currently experiencing issues in ClaimShop Settlement and the Shop. 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.

2. monitoring Aug 19, 2026, 07:19 AM UTC

   A fix has been implemented and we are monitoring results.

3. resolved Aug 19, 2026, 07:27 AM UTC

   Incident has been resolved.

Read the full incident report →

Started Aug 03, 2026, 06:06 AM UTC· resolved Aug 03, 2026, 06:37 AM UTC

1. investigating Aug 03, 2026, 06:06 AM UTC

   Our Sandbox environment for CORE & HUB is currently unavailable. We are investigating the issue at highest priority.

2. resolved Aug 03, 2026, 06:37 AM UTC

   (not set)

Read the full incident report →

Started Jul 07, 2026, 10:59 AM UTC· resolved Jul 07, 2026, 11:12 AM UTC

1. investigating Jul 07, 2026, 10:59 AM UTC

   We're investigating an issue affecting the ClaimShop Settlement module. Some customers are not receiving claim events since 09:06. Our team is actively investigating and will post an update as soon as we know more.

2. monitoring Jul 07, 2026, 11:04 AM UTC

   A fix has been implemented. We are monitoring the results.

3. resolved Jul 07, 2026, 11:12 AM UTC

   (not set)

Read the full incident report →

Started Jun 26, 2026, 09:44 AM UTC· resolved Jun 29, 2026, 12:53 PM UTC

1. investigating Jun 26, 2026, 09:44 AM UTC

   We are aware of an issue affecting some external service partners in HUB Property. It primarily impacts external service partner accounts when they are first granted access to a claim. We are investigating with the highest priority and will provide an update as soon as we have more information or the issue is resolved.

2. identified Jun 26, 2026, 12:58 PM UTC

   Issue has been identified and a fix is being worked on.

3. resolved Jun 29, 2026, 12:53 PM UTC

   (not set)

Read the full incident report →

Started Jun 26, 2026, 09:35 AM UTC· resolved Jun 29, 2026, 12:52 PM UTC

1. investigating Jun 26, 2026, 09:35 AM UTC

   We are aware of an issue affecting some external service partners in HUB Property. It primarily impacts external service partner accounts when they are first granted access to a claim. We are investigating with the highest priority and will provide an update as soon as we have more information or the issue is resolved.

2. identified Jun 26, 2026, 12:59 PM UTC

   We have identified the cause of the issue affecting service partner access to claims in HUB Property. A fix is being worked on now, and we will provide a further update once it has been deployed or we have more information

3. identified Jun 29, 2026, 07:24 AM UTC

   Work is still ongoing. Some external service partners may still experience issues with access to claims.

4. monitoring Jun 29, 2026, 09:12 AM UTC

   A fix has been implemented and we are monitoring results. All external service partners should be able to access claims once again.

5. resolved Jun 29, 2026, 12:52 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2026, 11:29 AM UTC· resolved Jun 12, 2026, 01:13 PM UTC

1. investigating Jun 12, 2026, 11:29 AM UTC

   Some of our claimshandlers are unable to complete work in Settlement Tool. 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.

2. monitoring Jun 12, 2026, 11:40 AM UTC

   A fix has been implemented, we are monitoring results.

3. resolved Jun 12, 2026, 01:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 03, 2026, 05:59 AM UTC· resolved Jun 03, 2026, 07:11 AM UTC

1. investigating Jun 03, 2026, 05:59 AM UTC

   Some of our users are currently experiencing working in CORE & HUB system. 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.

2. monitoring Jun 03, 2026, 06:27 AM UTC

   A fix has been implemented and we are monitoring situation.

3. resolved Jun 03, 2026, 07:11 AM UTC

   The incident has been resolved.

Read the full incident report →

Started May 22, 2026, 07:11 AM UTC· resolved May 22, 2026, 09:07 AM UTC

1. investigating May 22, 2026, 07:11 AM UTC

   Some of our users are currently experiencing issues in ClaimShop Settlement and the Shop. 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.

2. monitoring May 22, 2026, 07:29 AM UTC

   A fix has been introduced and we are monitoring the situation.

3. identified May 22, 2026, 08:51 AM UTC

   The issue has been identified and a fix is being implemented.

4. resolved May 22, 2026, 09:07 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 21, 2026, 06:49 AM UTC· resolved May 21, 2026, 09:29 AM UTC

1. identified May 21, 2026, 06:49 AM UTC

   Some customers may experience missing or non-updating messages in the Messages tab on certain claims. The issue is being investigated with the highest priority. We will provide further updates as soon as more information is available or the issue has been resolved. As a workaround, users can limit the displayed messages using the filter located at the top of the Messages tab, next to the search function.

2. identified May 21, 2026, 07:40 AM UTC

   We’ve identified the cause and are working on deploying a fix as soon as possible.

3. identified May 21, 2026, 09:28 AM UTC

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

4. resolved May 21, 2026, 09:29 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 27, 2026, 02:14 PM UTC· resolved Apr 27, 2026, 02:48 PM UTC

1. investigating Apr 27, 2026, 02:14 PM UTC

   Test incident on statuspage.

2. resolved Apr 27, 2026, 02:48 PM UTC

   There was no incident. This was a test.

Read the full incident report →

Started Apr 23, 2026, 11:07 AM UTC· resolved Apr 23, 2026, 12:31 PM UTC

1. investigating Apr 23, 2026, 11:07 AM UTC

   We are investigatin the issue.

2. investigating Apr 23, 2026, 11:33 AM UTC

   We are still investigating the issue.

3. investigating Apr 23, 2026, 11:48 AM UTC

   We are getting multiple reports of erros in CORE & HUB from users. Investigation continues.

4. resolved Apr 23, 2026, 12:31 PM UTC

   (not set)

Read the full incident report →

Started Apr 23, 2026, 11:00 AM UTC· resolved Apr 23, 2026, 08:32 PM UTC

1. investigating Apr 23, 2026, 11:00 AM UTC

   Some of our users are unable to gain access to their settlement and Shop purchases. 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.

2. investigating Apr 23, 2026, 11:33 AM UTC

   We are still investigating the issue.

3. investigating Apr 23, 2026, 11:47 AM UTC

   We are getting multiple reports of erros in CORE & HUB from users. Investigation continues.

4. monitoring Apr 23, 2026, 12:13 PM UTC

   A fix has been implemented and systems are back online. We are monitoring the results.

5. resolved Apr 23, 2026, 08:32 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 20, 2026, 08:17 AM UTC· resolved Apr 20, 2026, 08:27 AM UTC

1. investigating Apr 20, 2026, 08:17 AM UTC

   Some of our users are currently experiencing issues with Repair & Valuation. The issue has been identified and we are working towards a solution with the highest priority. We will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

2. investigating Apr 20, 2026, 08:21 AM UTC

   Here's a brief overview as of 10:21am CEST: • The main cause of disruption was missing or outdated Symantec root certificates on several application servers, leading to virus scanning failures and blocking the Repair & Valuation service for multiple customers. • Certificates were updated last Thursday. While some servers are now operational (ECC nodes restarted and green), a few users still report connection issues. FNOL is also affected by similar certificate-related scanning failures, and self-service is still experiencing problems as it hasn't yet been redeployed with the corrected certificates. • The sp-certs package was recently updated, but a redeploy is on hold while the release tagging is corrected. Once the correct package is available, deployments will proceed to finalize the fix across all impacted services. • Claim handlers at Topdanmark - IF Forsikring and several other customers have been unable to process claims for over an hour due to this issue.

3. investigating Apr 20, 2026, 08:22 AM UTC

   ECC part confirmed to be working again

4. resolved Apr 20, 2026, 08:27 AM UTC

   (not set)

5. monitoring Apr 20, 2026, 10:16 AM UTC

   Mikkel (charlie) Looks like there's still an issue with Widget solution Kacper Staniszewski

6. resolved Apr 20, 2026, 10:38 AM UTC

   (not set)

Read the full incident report →

Started Apr 20, 2026, 08:16 AM UTC· resolved Apr 20, 2026, 01:14 PM UTC

1. identified Apr 20, 2026, 08:16 AM UTC

   Some of our users are currently experiencing issues with Repair & Valuation. The issue has been identified and we are working towards a solution with the highest priority. We will provide an update as soon as we have additional information to provide and/or the issue has been resolved.

2. monitoring Apr 20, 2026, 08:22 AM UTC

   Fix has been implemented and we are monitoring the results.

3. monitoring Apr 20, 2026, 08:43 AM UTC

   We have observed erros in the Selfservice module, claimaints use to regristrer items. Work is ongoing to resolve the issue.

4. monitoring Apr 20, 2026, 08:53 AM UTC

   A fix has been introduced to Selfservice. We are monitoring the results.

5. identified Apr 20, 2026, 09:25 AM UTC

   We are continuing to observe errors affecting the Widget tool in Selfservice, and our investigation is ongoing. We apologize for the inconvenience this may be causing our users.

6. monitoring Apr 20, 2026, 10:19 AM UTC

   A fix has been implemeted for Widget tool. We are monitoring results.

7. resolved Apr 20, 2026, 01:14 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 16, 2026, 09:22 AM UTC· resolved Apr 16, 2026, 10:14 AM UTC

1. investigating Apr 16, 2026, 09:22 AM UTC

   A simple fix for users experiencing the "500 Server Error" on login, should reset their password. That should resolve the issue on the next login attempt. 1. Simply click "Forgot password? Click here" on the login page. 2. Enter "Username or email:" and click 'Send link'. 3. Follow link in email received and set a new password. 4. Login using the new password. Additional info. It seems there are users receiving multiple emails with verification code. The first email received should contain the correct code to login. If wrong code is used, "500 server error"-message will be displayed. User has to reset password again.

2. resolved Apr 16, 2026, 10:14 AM UTC

   (not set)

3. identified Apr 16, 2026, 12:25 PM UTC

   Unfortunately we are stil seeing issues with partner login. We are working towards a fix.

4. identified Apr 16, 2026, 02:03 PM UTC

   We are still working on resolve the issue with login, that many users on HUB Health are experiencing.

5. identified Apr 17, 2026, 07:10 AM UTC

   We are continuing to work on a fix for the current issue.

6. identified Apr 17, 2026, 07:42 AM UTC

   We are still working on a fix to login issue HUB Health service partners are experiencing.

7. resolved Apr 17, 2026, 08:53 AM UTC

   (not set)

Read the full incident report →

Started Apr 14, 2026, 09:45 AM UTC· resolved Apr 16, 2026, 09:24 AM UTC

1. investigating Apr 14, 2026, 09:45 AM UTC

   Some of our users are currently experiencing delays receiving e-mails. 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.

2. investigating Apr 15, 2026, 05:45 AM UTC

   We are in dialog with our supplier on why some users experience significant delays in delivery of email. Certain issues should be resolved yesterday. We will continue to monitor the situation in morning hours.

3. investigating Apr 15, 2026, 07:15 AM UTC

   We are currently investigating an issue affecting the delivery of certain system-generated emails in ClaimsCORE and HUB. Users may experience significant delays when receiving password reset emails. Additionally, some HUB partner emails are not being delivered, which may prevent users from logging into the Scalepoint system. Please note that manual email communications (e.g., claim handlers contacting claimants directly) are not affected.

4. investigating Apr 15, 2026, 01:16 PM UTC

   Our supplier is still working on investigating the issue. We continue to await their response and are monitoring any changes in email traffic.

5. monitoring Apr 16, 2026, 05:09 AM UTC

   Our supplier informs us a fix has been implemented. We will monitor the effectiveness of the solution.

6. monitoring Apr 16, 2026, 06:36 AM UTC

   We are unfortunately seeing some complications with the latest fix. Email traffic is using new routes to their destination, but these routes seem affected by the increase in traffic. We are working to resolve issues with our supplier.

7. monitoring Apr 16, 2026, 08:43 AM UTC

   Emails are finally being sent and received. Unfortunately many Service partner users in HUB Health are experiencing errors on login. We are working to resolve the issue.

8. monitoring Apr 16, 2026, 09:21 AM UTC

   A simple fix for users experiencing the "500 Server Error" on login, should reset their password. That should resolve the issue on the next login attempt. 1. Simply click "Forgot password? Click here" on the login page. 2. Enter "Username or email:" and click 'Send link'. 3. Follow link in email received and set a new password. 4. Login using the new password. Additional info. It seems there are users receiving multiple emails with verification code. The first email received should contain the correct code to login. If wrong code is used, "500 server error"-message will be displayed. User has to reset password again.

9. resolved Apr 16, 2026, 09:24 AM UTC

   (not set)

Read the full incident report →

Started Apr 14, 2026, 09:44 AM UTC· resolved Apr 17, 2026, 09:55 AM UTC

1. investigating Apr 14, 2026, 09:44 AM UTC

   Some of our users are currently experiencing delays receiving e-mails. 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.

2. monitoring Apr 14, 2026, 11:13 AM UTC

   Issue has been resolved. We are monitoring the situation.

3. monitoring Apr 14, 2026, 01:20 PM UTC

   We are still investigating delays on email delivery.

4. monitoring Apr 15, 2026, 05:44 AM UTC

   We are in dialog with our supplier on why some users experience significant delays in delivery of email. Certain issues should be resolved yesterday. We will continue to monitor the situation in morning hours.

5. investigating Apr 15, 2026, 07:14 AM UTC

   We are currently investigating an issue affecting the delivery of certain system-generated emails in ClaimsCORE and HUB. Servicepartner users may experience significant delays when receiving password reset emails. Additionally, many HUB Health partner emails are not being delivered, which may prevent users from logging into the Scalepoint system. Please note that manual email communications (e.g., claim handlers contacting claimants directly) are not affected.

6. identified Apr 15, 2026, 01:16 PM UTC

   Our supplier is still working on investigating the issue. We continue to await their response and are monitoring any changes in email traffic.

7. monitoring Apr 16, 2026, 05:03 AM UTC

   Our supplier informs us a fix has been implemented. We will monitor the effectiveness of the solution.

8. monitoring Apr 16, 2026, 06:35 AM UTC

   We are unfortunately seeing some complications with the latest fix. Email traffic is using new routes to their destination, but these routes seem affected by the increase in traffic. We are working to resolve issues with our supplier.

9. identified Apr 16, 2026, 07:58 AM UTC

   Emails are finally being sent and received. Unfortunately many Service partner users in HUB Health are experiencing errors on login. We are working to resolve the issue.

10. identified Apr 16, 2026, 09:03 AM UTC

    A simple fix for users experiencing the "500 Server Error" on login, should reset their password. That should resolve the issue on the next login attempt. 1. Simply click "Forgot password? Click here" on the login page. 2. Enter "Username or email:" and click 'Send link'. 3. Follow link in email received and set a new password. 4. Login using the new password.

11. identified Apr 16, 2026, 09:21 AM UTC

    A simple fix for users experiencing the "500 Server Error" on login, should reset their password. That should resolve the issue on the next login attempt. 1. Simply click "Forgot password? Click here" on the login page. 2. Enter "Username or email:" and click 'Send link'. 3. Follow link in email received and set a new password. 4. Login using the new password. Additional info. It seems there are users receiving multiple emails with verification code. The first email received should contain the correct code to login. If wrong code is used, "500 server error"-message will be displayed. User has to reset password again.

12. monitoring Apr 16, 2026, 10:12 AM UTC

    A fix has been implemented and once users have reset password, will be able to access systems. We are monitoring email and user traffic for the time being.

13. monitoring Apr 16, 2026, 12:24 PM UTC

    Unfortunately we are stil seeing issues with partner login. We are working towards a fix.

14. identified Apr 16, 2026, 02:02 PM UTC

    We are still working on resolve the issue with login, that many users on HUB Health are experiencing.

15. identified Apr 17, 2026, 05:15 AM UTC

    We are continuing to work on a fix for the current issue.

16. identified Apr 17, 2026, 07:42 AM UTC

    We are still working on a fix to login issue HUB Health service partners are experiencing.

17. monitoring Apr 17, 2026, 08:52 AM UTC

    Our fix has been released! Service partners on HUB Health should no longer get "500 server error" when accessing system.

18. resolved Apr 17, 2026, 09:55 AM UTC

    This incident has been resolved.

Read the full incident report →