Scalepoint had 50 outages in the last 2 years totaling 304h 28m of downtime — averaging 2.1 incidents per month.
There were 50 Scalepoint outages since July 18, 2025 totaling 304h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
A fix has been implemented. We are monitoring the results.
(not set)
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.
Issue has been identified and a fix is being worked on.
(not set)
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.
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
Work is still ongoing. Some external service partners may still experience issues with access to claims.
A fix has been implemented and we are monitoring results. All external service partners should be able to access claims once again.
This incident has been resolved.
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.
A fix has been implemented, we are monitoring results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring situation.
The incident has been resolved.
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.
A fix has been introduced and we are monitoring the situation.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
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.
We’ve identified the cause and are working on deploying a fix as soon as possible.
We are continuing to work on a fix for this issue.
This incident has been resolved.
Some of our users are currently experiencing issues in access to Sandbox environment for ClaimShop. 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.
This incident has been resolved.
Test incident on statuspage.
There was no incident. This was a test.
We are investigatin the issue.
We are still investigating the issue.
We are getting multiple reports of erros in CORE & HUB from users. Investigation continues.
(not set)
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.
We are still investigating the issue.
We are getting multiple reports of erros in CORE & HUB from users. Investigation continues.
A fix has been implemented and systems are back online. We are monitoring the results.
This incident has been resolved.
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.
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.
ECC part confirmed to be working again
(not set)
Mikkel (charlie) Looks like there's still an issue with Widget solution Kacper Staniszewski
(not set)
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.
Fix has been implemented and we are monitoring the results.
We have observed erros in the Selfservice module, claimaints use to regristrer items. Work is ongoing to resolve the issue.
A fix has been introduced to Selfservice. We are monitoring the results.
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.
A fix has been implemeted for Widget tool. We are monitoring results.
This incident has been resolved.
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.
(not set)
Unfortunately we are stil seeing issues with partner login. We are working towards a fix.
We are still working on resolve the issue with login, that many users on HUB Health are experiencing.
We are continuing to work on a fix for the current issue.
We are still working on a fix to login issue HUB Health service partners are experiencing.
(not set)
Some of our users are currently experiencing issues with degraded performance in ClaimShop. 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.
A fix has been implemented. We are monitoring results.
Issue looks to be resolved. We continue to monitor whilst we are investigating root cause.
Some users may still experience issues. We are working to resolve issues for a while yet.
This incident has been resolved.
Claimshop is experiencing issues.
(not set)
test
(not set)
Some of our users are currently experiencing issues with access to ClaimShop and CORE & HUB Services. 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.
Issue has been resolved. We are monitoring situation.
This incident har been resolved.
Many users are experiencing issues with MitID. The issue is being reported by external provider as a general issue with MitID. We will provide an update as soon as we have additional information to provide and/or the issue has been resolved.
Still monitoring.
(not set)
Many users are experiencing issues with MitID. The issue is being reported by external provider as a general issue with MitID. We will provide an update as soon as we have additional information to provide and/or the issue has been resolved.
We continue to monitor the situation. Once word of MitID is working again, we will report back.
This incident has been resolved.
We are investigating the issue.
Issue seems to have resolved, we are now monitoring the situation.
(not set)
We are currently investigating this issue.
Issues seems to be resolved. We are monitoring the situation.
A small disturbance was identified at external supplier, causing a delay in SMS delivery. Once issue was resolved all text messages were released.
Some of our users are currently experiencing issues receiving SMS and / or 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.
Unscheduled disturbance towards Telenor Danmark, has been identified as the cause. We are monitoring the situation.
We continue to monitor situation and are in dialoge with relevant provider.
We are seeing SMS deliveries are starting to work again. We expect external provider to confirm soon.
No further disruption has been seen in internal logs. We are still monitoring situation.
This incident has been resolved.