Monthio incident

Datafordeler degraded performance (CPR-registry) [RESOLVED]

Major Resolved View vendor source →

Monthio experienced a major incident on March 10, 2026 affecting Datafordeler / CPR-registry, lasting 1d 2h. The incident has been resolved; the full update timeline is below.

Started
Mar 10, 2026, 02:12 PM UTC
Resolved
Mar 11, 2026, 04:21 PM UTC
Duration
1d 2h
Detected by Pingoru
Mar 10, 2026, 02:12 PM UTC

Affected components

Datafordeler / CPR-registry

Update timeline

  1. investigating Mar 10, 2026, 02:12 PM UTC

    ENGLISH Datafordeler, where we retrieve information from the CPR-registry from, has had degraded performance since 15:05 today. This means that it is possible that some cases will miss information we receive from the CPR-registry (e.g. name, CPR number, address and credit warnings). As we use an applicants CPR number for looking up properties/cars in Tinglysning, cases might also miss Tinglysning data. We recommend that applicants do not fill in their applications during this time. We will set up a banner in the application flow, advising applicants to finish their application after the incident has been solved. 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. DANISH Datafordeler, hvor vi indhenter data fra CPR-registret, har siden kl. 15:05 i dag oplevet driftsforstyrrelser. 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. Vi anbefaler at ansøgere 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. 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.

  2. resolved Mar 11, 2026, 04:21 PM UTC

    This incident has been resolved.