Resolved after 49 minutes, affecting Visma Net and Visma Net API, on May 16, 2026.
Incident was caused by a failing maintenance operation that left one of our databases in an inconsistent state. We restored the data and were able to fix the problem. We agreed how to improve the process so that this can be avoided in the future
Affected components
Update timeline
- investigating May 16, 2026, 05:24 AM UTC
We are currently investigating this issue.
- investigating May 16, 2026, 05:48 AM UTC
We are continuing to investigate this issue.
- monitoring May 16, 2026, 06:09 AM UTC
A fix has been implemented and we are monitoring that all is back to normal
- resolved May 16, 2026, 06:14 AM UTC
This incident has been resolved.
- postmortem May 22, 2026, 01:46 PM UTC
Incident was caused by a failing maintenance operation that left one of our databases in an inconsistent state. We restored the data and were able to fix the problem. We agreed how to improve the process so that this can be avoided in the future
Your product runs on more than Visma
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