|
Cloudmore has five predefined severity levels in line with our SLAs. Incidents with severity level 1 and 2 are regarded as critical incidents and will be treated with absolute top priority.
(Non office time behind brackets)
|
|
Level
|
Description
|
Reaction
|
Incident report
|
|
1
|
Affects all users' access to one or more services. |
15 min
(1 h)
|
Yes, complete report |
|
2
|
Affects a large number of users from multiple organizations to access one or more services.. |
60 min
(2 h)
|
Yes, complete report |
|
3
|
Affects an individual user to access one or more services or a situation that affects the performance of the service for several users |
4 h
|
No, support feedback |
|
4
|
Affect the performance of the service for an individual user. |
8 h
|
No, support feedback |
|
5
|
General questions about improvements and features |
n/a
|
No, support feedback |
| * This update frequency is applicable only during the first 2 hours of the disruption. If the disruption length is longer than 2 hours the updates will be published as soon as new information is available. |
|
Incident reports
A complete incident report will be published on www.cloudmore.com under Hosting Network Status within 10 working days from when the incident was resolved.
Service Availability Incident Management
This document describes how service availability (SA) incidents are handled and how information is communicated between Cloudmore's support team, system technicians, other staff and Cloudmore's external Partners / Resellers. Download document
|
|
LinkedIn
Hosting Network Status