e-Boks Outage History

e-Boks is up right now

e-Boks had 6 outages in the last 2 years totaling 13h 9m of downtime — averaging 0.2 incidents per month.

There were 6 e-Boks outages since August 27, 2025 totaling 13h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.e-boks.com

Notice June 24, 2026

Driftforstyrrelser på den offentlige Digital Post løsning / The public sector´s supplier of Digital Post experiences operational disruptions.

Detected by Pingoru
Jun 24, 2026, 02:41 AM UTC
Resolved
Jun 24, 2026, 05:27 AM UTC
Duration
2h 46m
Affected: NgDP Commercial Front End ClientPublic Digital Post
Timeline · 3 updates
  1. identified Jun 24, 2026, 02:41 AM UTC

    Udbyderen af offentlig Digital Post oplever i øjeblikket driftsforstyrrelser. e-Boks kan stadig tilgås for post fra private virksomheder. ------------------------------------------------- The public sector´s supplier of Digital Post experiences operational disruptions. e-Boks can still be accessed for mail from private companies.

  2. identified Jun 24, 2026, 02:42 AM UTC

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

  3. resolved Jun 24, 2026, 05:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 21, 2026

e-Boks are experiencing operational disturbances

Detected by Pingoru
May 21, 2026, 06:21 AM UTC
Resolved
May 21, 2026, 07:30 AM UTC
Duration
1h 8m
Affected: e-Boks App Denmarke-Boks web client users - Denmarke-Boks App Swedene-Boks web client company - Denmarke-Boks App Norway
Timeline · 3 updates
  1. investigating May 21, 2026, 06:21 AM UTC

    e-Boks har i øjeblikket driftsforstyrrelser. Der bliver arbejdet på at finde fejlen. Næste opdatering: kl. Vi beklager de gener, det måtte medføre. -------------------------------------- e-Boks is experiencing operational disruptions. Work is underway to investigate the problem. Next update at: We apologize for any inconvenience this may cause. Med venlig hilsen / Kind regards e-Boks

  2. monitoring May 21, 2026, 07:01 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 21, 2026, 07:30 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 31, 2026

Problemer på den offentlige NemLog-in / There are problems with the public NemLog-in solution

Detected by Pingoru
Mar 31, 2026, 07:01 AM UTC
Resolved
Mar 31, 2026, 12:28 PM UTC
Duration
5h 26m
Affected: Public login provider – Nemlog-in
Timeline · 4 updates
  1. investigating Mar 31, 2026, 07:01 AM UTC

    Der opleves problemer på den offentlige Digital Post løsning, hvilket betyder, at det ikke er muligt at logge på e-Boks via Nemlog-in. Fejlen er rapporteret til Digitaliseringsstyrelsen og afventer deres fejlrettelse. Det er muligt at logge på e-Boks via app. There are problems with the public digital mail solution, which means that it is not possible to log in to e-Boks via Nemlog-in. The problem has been reported to the Danish Agency for Digital Government and is awaiting their error correction. It is still possible to log in to e-Boks via the app.

  2. investigating Mar 31, 2026, 07:24 AM UTC

    We are continuing to investigate this issue.

  3. identified Mar 31, 2026, 07:30 AM UTC

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

  4. resolved Mar 31, 2026, 12:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 17, 2026

e-Boks oplever driftsforstyrrelser. Kom på via e-Boks mobile enheder / e-Boks operational disruptions. But available on mobile devices

Detected by Pingoru
Mar 17, 2026, 07:23 AM UTC
Resolved
Mar 17, 2026, 09:16 AM UTC
Duration
1h 53m
Affected: e-Boks web client users - DenmarkInternational REST APIe-Boks web client company - Denmarke-Boks web client users - Swedene-Boks web client users - Norway
Timeline · 5 updates
  1. investigating Mar 17, 2026, 07:23 AM UTC

    Der kan opleves driftsforstyrrelser på e-Boks. e-Boks kan dog tilgås via mobile enheder. Vi arbejder på at udbedre fejlen hurtigst muligt. Vi beklager de gener, det måtte medføre. Næste opdatering kl hh:mm. --------------------------- There may be some disruption to the operation of the e-Boks services. However, e-Boks is available on mobile devices. We are working to resolve the issue as quickly as possible. We apologize for any inconvenience this may cause. Next update at hh:mm. Med venlig hilsen / Kind regards e-Boks

  2. investigating Mar 17, 2026, 08:16 AM UTC

    We are continuing to investigate this issue.

  3. identified Mar 17, 2026, 08:36 AM UTC

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

  4. monitoring Mar 17, 2026, 08:59 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Mar 17, 2026, 09:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 12, 2025

e-Boks fejl identificeret / e-Boks Incident identified affecting the DEMO environment

Detected by Pingoru
Nov 12, 2025, 09:22 AM UTC
Resolved
Nov 12, 2025, 09:27 AM UTC
Duration
5m
Affected: e-Boks web client users - DenmarkDEMO DK environmente-Boks web client company - Denmark
Timeline · 2 updates
  1. identified Nov 12, 2025, 09:22 AM UTC

    Fejlen er identificeret, og en rettelse er under implementering. ------------------------------------ The issue has been identified and a fix is being implemented. Med venlig hilsen / Kind regards e-Boks

  2. resolved Nov 12, 2025, 09:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 1, 2025

e-Boks driftsforstyrrelser / e-Boks operational disruptions

Detected by Pingoru
Sep 01, 2025, 01:04 PM UTC
Resolved
Sep 01, 2025, 02:54 PM UTC
Duration
1h 49m
Affected: e-Boks App Denmarke-Boks web client users - DenmarkInternational REST APIe-Boks App Swedene-Boks web client company - DenmarkPublic REST API - Denmarke-Boks App Norwaye-Boks web client users - SwedenEBMS API - Norwaye-Boks web client users - NorwayS/MIMEFile interface
Timeline · 3 updates
  1. identified Sep 01, 2025, 01:04 PM UTC

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

  2. monitoring Sep 01, 2025, 02:54 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 01, 2025, 02:54 PM UTC

    This incident has been resolved.

Read the full incident report →