Notice history -

Mar 2025

Apr 2025

May 2025

Mar 2025

Apr 2025

May 2025

Mar 2025

Apr 2025

May 2025

Mar 2025

Apr 2025

May 2025

Mar 2025

Apr 2025

May 2025

Notice history

Resolved
May 16, 2025 at 1:18 PMUTC
Resolved
May 16, 2025 at 1:18 PMUTC
This incident has been resolved.
Update
May 16, 2025 at 11:26 AMUTC
Update
May 16, 2025 at 11:26 AMUTC
We are continuing to monitor for any further issues.
Monitoring
May 16, 2025 at 11:20 AMUTC
Monitoring
May 16, 2025 at 11:20 AMUTC
A fix has been implemented and we are monitoring the results.
Identified
May 16, 2025 at 6:16 AMUTC
Identified
May 16, 2025 at 6:16 AMUTC
We’ve updated Norwegian companies with new shareholder data from Aksjonærreegisteret 2024. Beneficial owners are still based on 2023 data, so there are inconsistencies between shareholders and beneficial owners. We expect to resolve the issue within today (Friday).

Resolved
April 02, 2025 at 12:19 PMUTC
Resolved
April 02, 2025 at 12:19 PMUTC
The application has remained stable following the identification of the root cause. The implemented improvements have been effective, and the incident is now resolved.
Monitoring
April 01, 2025 at 5:40 PMUTC
Monitoring
April 01, 2025 at 5:40 PMUTC
We have implemented several fixes that addressed how user settings were stored inside our database leading to high memory consumption of database queries. The application is running stably and we continue to monitor the situation.
Update
April 01, 2025 at 6:38 AMUTC
Update
April 01, 2025 at 6:38 AMUTC
We are continuing to investigate this issue.
Investigating
April 01, 2025 at 12:55 AMUTC
Investigating
April 01, 2025 at 12:55 AMUTC
We're experiencing instabilities in a database. As a result, our applications might be unstable.

Resolved
March 31, 2025 at 3:34 PMUTC
Resolved
March 31, 2025 at 3:34 PMUTC
We have experienced some API instability after a release. The issue was quickly identified and resolved.

Resolved
March 23, 2025 at 10:24 AMUTC
Resolved
March 23, 2025 at 10:24 AMUTC
This incident has been resolved. The outage has been caused by automatic Kubernetes infrastructure upgrade affecting available resources of our database servers. This has been now adjusted to accommodate the changes.
Investigating
March 23, 2025 at 9:57 AMUTC
Investigating
March 23, 2025 at 9:57 AMUTC
We are currently investigating this issue.

Resolved
March 20, 2025 at 2:11 PMUTC
Resolved
March 20, 2025 at 2:11 PMUTC
This incident has been resolved.
Investigating
March 20, 2025 at 11:08 AMUTC
Investigating
March 20, 2025 at 11:08 AMUTC
We are currently investigating this issue.

Resolved
March 06, 2025 at 12:48 PMUTC
Resolved
March 06, 2025 at 12:48 PMUTC
There was a bug in a beta feature that has been fixed, which fired off many error requests to our app server. The load was not handled properly which led to restarts, a fixed has been rolled out.
Update
March 06, 2025 at 10:34 AMUTC
Update
March 06, 2025 at 10:34 AMUTC
We have identified the problem and disabled the feature that was causing the issue - we are still investigating what the root cause is.
Investigating
March 06, 2025 at 10:01 AMUTC
Investigating
March 06, 2025 at 10:01 AMUTC
We are currently investigating the issue

Mar 2025 to May 2025