Visma Nmbrs incident
Sandbox not accessible for specific set of clients
Resolved after 7 days 3 hours, affecting Sandbox and Sandbox, on October 16, 2025.
A fix has been implemented and we are monitoring the results.
Affected components
Update timeline
- investigating Oct 16, 2025, 08:58 AM UTC
We are currently investigating this issue.
- identified Oct 16, 2025, 02:47 PM UTC
The issue has been identified and a fix will be implemented with the Sandbox reset tonight.
- investigating Oct 17, 2025, 06:22 AM UTC
Unfortunately, the previous fix did not resolve the issue. We have restarted our investigation and are working to identify the root cause.
- identified Oct 17, 2025, 03:36 PM UTC
The issue has been identified and a fix will be implemented during this weekend.
- investigating Oct 20, 2025, 07:44 AM UTC
Unfortunately, the previous solutions did not fully resolve the issue. We have resumed our investigation to identify the underlying cause and are working on a permanent fix.
- identified Oct 22, 2025, 09:51 AM UTC
We've identified the issue and a fix will be implemented. We'll keep you updated on the progress.
- monitoring Oct 22, 2025, 08:49 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 23, 2025, 12:09 PM UTC
This incident has been resolved.
Your product runs on more than Visma Nmbrs
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services