SmartDok incident
SmartDok opplever problemer / SmartDok upplever problem / SmartDok is experiencing issues
SmartDok experienced a critical incident on October 29, 2025 affecting SmartDok Norway Web (web.smartdok.no) and SmartDok Sweden Web (web.smartdok.se), lasting 1h 56m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 29, 2025, 04:11 PM UTC
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.
- identified Oct 29, 2025, 04:28 PM UTC
Azure Portal Access Issues Our supplyer are investigating an issue with the Azure Portal where customers may be experiencing issues accessing the portal.
- identified Oct 29, 2025, 04:37 PM UTC
Starting at approximately 16:00 UTC, Azure began experiencing DNS issues resulting in availability degradation of some services. Customers may experience issues accessing the Azure Portal. We have taken action that is expected to address the portal access issues here shortly. We are actively investigating the underlying issue and additional mitigation actions. More information will be provided within 60 minutes or sooner. This message was last updated at 16:35 UTC on 29 October 2025
- identified Oct 29, 2025, 05:09 PM UTC
Azure are now actively assessing failover options of internal services from their AFD infrastructure. Their investigation into the contributing factors and additional recovery workstreams continues.
- monitoring Oct 29, 2025, 05:22 PM UTC
SmartDok Norway Web (web.smartdok.no) and SmartDok Sweden Web (web.smartdok.se) are now online again. Our developers have implemented a backup solution until Azure has fixed its challenges.
- monitoring Oct 29, 2025, 05:24 PM UTC
We are continuing to monitor for any further issues.
- resolved Oct 29, 2025, 06:08 PM UTC
This incident has been resolved.