Datafordeler degraded performance (CPR-registry) [RESOLVED]

Update timeline

1. investigating Mar 23, 2026, 09:05 AM UTC

   ENGLISH Datafordeler, where we retrieve information from the CPR-registry, has reported that they experience instability issues, which are related to the downtimes from the past week. This means some cases may miss information we receive from the CPR-registry (e.g., name, CPR number, address, and credit warnings). As we use an applicant's CPR number for looking up properties/cars in Tinglysning, cases might also miss Tinglysning data. There is currently no timeframe for a potential fix, so we will continue to monitor the situation and update as soon as the issue has been resolved. If the information is missing in certain cases, then we recommend that applicants try again or wait until the issue has been resolved. We will inform the applicants about this through a banner in the flow. DANISH Datafordeler, hvor vi indhenter data fra CPR-registret, har rapporteret, at de oplever udfordringer med diverse forbindelser, hvilket er forbundet med de driftsforstyrrelser, der forekom i forrige uge. Dette betyder, at det er muligt, at nogle sager som færdiggøres imens driftsforstyrrelserne pågår, mangler data som vi modtager fra CPR-registret. Fx. ansøgers fulde navn, CPR-nummer, bopæl og evt. kreditadvarsler. Da vi bruger ansøgeres CPR-numre til at slå op i tinglysning, er det derfor også muligt, at nogle sager kan mangle Tinglysning data. Der er pt. ikke muligt at sige noget om, hvornår dette er løst. Vi holder løbende øje med situationen og opdaterer, når situationen er løst. Hvis informationen mangler i specifikke sager, så anbefaler vi, at ansøgere forsøger en gang til eller venter med at udfylde deres ansøgning, indtil problemet er løst. Vi vil videreformidle direkte til ansøgere via et banner øverst i ansøgningsflowet.

2. monitoring Mar 24, 2026, 08:41 AM UTC

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

3. monitoring Mar 25, 2026, 10:28 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Mar 25, 2026, 10:29 PM UTC

   This incident has been resolved.