Service Status¶
Welcome to Evam Status page. Here you’ll find live and historical data on system performance.
UK¶
Active Incidents¶
Note
All Systems Operational
Historical incidents¶
Below you’ll find a record of all incidents from the past 30 days.
Sweden¶
Active Incidents¶
Note
All Systems Operational
Historical incidents¶
Below you’ll find a record of all incidents from the past 30 days.
Confirming a new incident by pressing the confirm button will not send the associated status to the control room if the user is using automatic statuses.
Severity: S3
Affected Services: Confirming a new incident by pressing the confirm button will not send the associated status to the control room if the user is using automatic statuses.
Please note that is is still possible to send the status from the status menu in the operations app (Sv: Ärende)
Incident Updates
Investigating: We are currently investigating the issue and working to resolve it as quickly as possible.
As a mitigation we suggest that users send statuses from the shortcut center or the operations app until the issue is resolved.
Posted: 11 December 2025, 09:55 UTC
Update: The problem is smaller than what was initially communicated. The only impact is that when confirming a new incident by pressing the confirm button the associated status to the control room will not be sent if the user is using automatic statuses.
As a mitigation we suggest that users send the statuses from the operations app until the issue is resolved. Please not that all other autmatic statuses and notifications works as they should
Posted: 11 December 2025, 10:23 UTC
Monitoring: A fix has been implemented, and we are closely monitoring to ensure everything is stable. A fix has been provided in Vehicle Services 7.0.7. To resolve the issue, please update Vehicle Services by following this guide: Update Vehicle Services Manually
Posted: 12 December 2025, 11:41 UTC
Resolved: The issue has been resolved, and all systems are operating normally.
Posted: 12 December 2025, 16:39 UTC
Incident Categorisation¶
To ensure transparency and consistency in how we communicate issues, we classify incidents into different priority levels based on their urgency and impact. This helps our team respond appropriately and allows you to understand the severity of an incident at a glance.
S1 – Critical
These incidents represent the highest level of severity. They typically involve complete system outages or issues that prevent the majority of users from accessing core services. Our team responds immediately to resolve S1 incidents.
S2 – High
Incidents at this level cause a large-scale impact but do not fully take down the system. For example, a major feature may be unavailable or malfunctioning. These are addressed with urgency, though they may not require the same escalation as S1 events.
S3 – Moderate
These are issues with a limited or moderate impact, such as a minor feature not functioning as expected. While important, S3 incidents are prioritised alongside other ongoing work and may not be resolved as quickly as higher-severity incidents.