SmartDok Outage History

SmartDok is up right now

SmartDok had 5 outages in the last 2 years totaling 21h 37m of downtime, averaging 0.2 incidents per month.

There were 5 SmartDok outages since February 20, 2025 totaling 21h 37m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.smartdok.com

Major September 22, 2026

Issues submitting forms through the app

Detected by Pingoru
Sep 22, 2026, 09:42 AM UTC
Resolved
Sep 22, 2026, 04:10 PM UTC
Duration
6h 28m
Affected: Mobile Apps
Timeline · 3 updates
  1. identified Sep 22, 2026, 09:42 AM UTC

    We are aware of an issue with submitting forms through the iOS app (1.0.6) when the project-form connection is enabled. We've got a fix scheduled to be released as soon as possible. We recommend not updating your app while we wait for this release (1.0.7). If you experience such issue please contact support to have the issue fixed for your company while the new iOS app (v1.0.7) releases.

  2. monitoring Sep 22, 2026, 01:20 PM UTC

    We have fixed the issue. No app updates are needed.

  3. resolved Sep 22, 2026, 04:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 4, 2026

Delays in email delivery to Microsoft-hosted domains

Detected by Pingoru
Sep 04, 2026, 12:23 PM UTC
Resolved
Sep 04, 2026, 03:39 PM UTC
Duration
3h 16m
Affected: SmartDok Norway Web (web.smartdok.no)SmartDok Sweden Web (web.smartdok.se)Mobile AppsAPI
Timeline · 3 updates
  1. identified Sep 04, 2026, 12:23 PM UTC

    Our email provider, Twilio SendGrid, is reporting issues delivering email to Microsoft-hosted mail servers. Emails sent from SmartDok to these recipients are being queued and retried automatically. We apologize for the inconvenience.

  2. monitoring Sep 04, 2026, 02:12 PM UTC

    We are seeing recovery in email traffic to MS365 supported recipients. We will continue to monitor the situation.

  3. resolved Sep 04, 2026, 03:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 19, 2026

SmartDok opplever problemer / SmartDok upplever problem / SmartDok is experiencing issues

Detected by Pingoru
Jun 19, 2026, 11:54 AM UTC
Resolved
Jun 19, 2026, 06:40 PM UTC
Duration
6h 45m
Affected: SmartDok Norway Web (web.smartdok.no)SmartDok Sweden Web (web.smartdok.se)Mobile Apps
Timeline · 5 updates
  1. identified Jun 19, 2026, 11:54 AM UTC

    Vi opplever problemer med SMS tjenesten som resultat av at vår leverandør har problemer. Vi har problem med SMS-tjänsten på grund av att vår leverantör har problem. We are experiencing problems with the SMS service as a result of our provider having problems.

  2. identified Jun 19, 2026, 01:27 PM UTC

    Tjenester som er avhengige av SMS skal være delvis gjenopprettet, men leveringen av SMS-meldinger kan være treg. Vi overvåker situasjonen med tjenesteleverandøren vår. Tjänster som är beroende av SMS bör vara delvis återställda, men leveransen av SMS-meddelanden kan vara långsam. Vi övervakar situationen med vår tjänsteleverantör. Services relying on SMS should be partially restored, however SMS message delivery might be slow. We are monitoring the situation with our service provider.

  3. identified Jun 19, 2026, 03:32 PM UTC

    Tjenester som er avhengige av SMS skal være delvis gjenopprettet, men leveringen av SMS-meldinger kan være treg eller ustabil. Vi overvåker situasjonen med tjenesteleverandøren vår. Tjänster som är beroende av SMS bör vara delvis återställda, men leveransen av SMS-meddelanden kan vara långsam. Vi övervakar situationen med vår tjänsteleverantör. Services relying on SMS should be partially restored, however SMS message delivery might be slow. We are monitoring the situation with our service provider.

  4. monitoring Jun 19, 2026, 04:06 PM UTC

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

  5. resolved Jun 19, 2026, 06:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 28, 2026

Problemer med web.smartdok.se / SmartDok down

Detected by Pingoru
Jan 28, 2026, 08:48 AM UTC
Resolved
Jan 28, 2026, 11:02 AM UTC
Duration
2h 14m
Affected: SmartDok Sweden Web (web.smartdok.se)
Timeline · 4 updates
  1. investigating Jan 28, 2026, 08:48 AM UTC

    Problemer med web.smartdok.se / SmartDok down Vi opplever problemer med vårt system. Våre utviklere er på saken, og vi holder denne siden oppdatert videre. Vi upplever för närvarande problem. Våra utvecklare jobbar på saken, och vi kommer att hålla den här sidan uppdaterad. We are experiencing issues. Our developers are working on it, and we will update this page with any changes.

  2. identified Jan 28, 2026, 09:41 AM UTC

    Feilkilden er funnet, og det jobbes med å rette denne. Felkällan har identifierats och arbete pågår med att åtgärda den. The source of the error has been identified, and work is underway to fix it.

  3. monitoring Jan 28, 2026, 10:27 AM UTC

    En fiks er implementert, og vi overvåker resultatet nå. En fix har implementerats och vi övervakar resultatet nu. A fix has been implemeted and we are monitoring the result now.

  4. resolved Jan 28, 2026, 11:02 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 20, 2025

Smartdok er delvis nede

Detected by Pingoru
Feb 20, 2025, 09:56 AM UTC
Resolved
Feb 20, 2025, 12:49 PM UTC
Duration
2h 53m
Affected: SmartDok Norway Web (web.smartdok.no)SmartDok Sweden Web (web.smartdok.se)Mobile Apps
Timeline · 7 updates
  1. investigating Feb 20, 2025, 09:56 AM UTC

    Vår leverandør Microsoft opplever problemer med sin tjeneste, som igjen påvirker oss. Systemet kan oppleves som ustabilt, og noen tjenester er midlertidig utilgjengelig. Vi er på saken og oppdaterer fortløpende.

  2. investigating Feb 20, 2025, 10:01 AM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 20, 2025, 10:05 AM UTC

    We are continuing to investigate this issue.

  4. investigating Feb 20, 2025, 10:23 AM UTC

    We are continuing to investigate this issue.

  5. investigating Feb 20, 2025, 11:06 AM UTC

    We are continuing to investigate this issue.

  6. investigating Feb 20, 2025, 12:49 PM UTC

    We are continuing to investigate this issue.

  7. resolved Feb 20, 2025, 12:49 PM UTC

    This incident has been resolved.

Read the full incident report →