Subscribe to UpdatesSubscribe
Get email notifications whenever Checkit creates, updates or resolves an incident.
Get text message notifications whenever Checkit creates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get incident updates and maintenance status messages in Microsoft Teams channel.
By subscribing you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
All Systems Operational
About This Site
Welcome to the Checkit Service Status Page - here you can see the status of each of our products and subscribe for notifications.
Uptime over the past 90 days. View historical uptime.
Control Centre
Operational
90 days ago
99.93
% uptime
Today
CWM
Operational
90 days ago
100.0
% uptime
Today
CAM
Operational
90 days ago
100.0
% uptime
Today
CAM+
Operational
90 days ago
100.0
% uptime
Today
CBM
Operational
90 days ago
100.0
% uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Sep 2, 2026
No incidents reported today.
Sep 1, 2026
No incidents reported.
Aug 31, 2026
No incidents reported.
Aug 30, 2026
No incidents reported.
Aug 29, 2026
No incidents reported.
Aug 28, 2026
Resolved -
Logging for all affected sites has now been restored, and the data backfill process has been initiated to recover data that was not successfully recorded during the incident.
The issue was not immediately detected by our monitoring systems because the service health checks continued to report as healthy.
The monitoring checks are designed to confirm that sessions are being processed within expected timeframes. In this instance, the component responsible for managing session information continued to use an existing database connection that had been established before the network change. As a result, the health checks continued to operate successfully and did not identify the underlying connectivity issue.
At the same time, data collection services remained operational and continued attempting to collect data. However, they were unable to establish the new database connections required to store this data in the relevant caching and logging systems.
This resulted in a partial service degradation where the data collection processes themselves remained operational, but some of the collected data could not be successfully stored. Because the services did not enter a failed state, the issue was not immediately identified by automated monitoring and was subsequently detected through operational indicators and further investigation.
We are reviewing the monitoring and health-check mechanisms as part of our follow-up actions to improve our ability to detect similar partial service degradation in the future.
Services Not Impacted
The following services remained operational throughout the incident:
Alarm processing and alarm reception.
All other core services.
Next Steps
Continue monitoring the backfill process and validate recovered data.
Review and enhance monitoring to improve detection of partial service degradation.
Aug 28, 11:19 UTC
The issue was not immediately detected by our monitoring systems because the service health checks continued to report as healthy.
The monitoring checks are designed to confirm that sessions are being processed within expected timeframes. In this instance, the component responsible for managing session information continued to use an existing database connection that had been established before the network change. As a result, the health checks continued to operate successfully and did not identify the underlying connectivity issue.
At the same time, data collection services remained operational and continued attempting to collect data. However, they were unable to establish the new database connections required to store this data in the relevant caching and logging systems.
This resulted in a partial service degradation where the data collection processes themselves remained operational, but some of the collected data could not be successfully stored. Because the services did not enter a failed state, the issue was not immediately identified by automated monitoring and was subsequently detected through operational indicators and further investigation.
We are reviewing the monitoring and health-check mechanisms as part of our follow-up actions to improve our ability to detect similar partial service degradation in the future.
Services Not Impacted
The following services remained operational throughout the incident:
Alarm processing and alarm reception.
All other core services.
Next Steps
Continue monitoring the backfill process and validate recovered data.
Review and enhance monitoring to improve detection of partial service degradation.
Aug 28, 11:19 UTC
Identified -
We've implemented a fix for this issue, and a mass backfill of missing data is now underway. Data logging will resume shortly, and in turn, the 'Fault' status will clear from both the CAM+ website and WARP panels. Thank you for your patience while we work to resolve.
Aug 27, 10:58 UTC
Aug 27, 10:58 UTC
Investigating -
We're aware that some customers are currently experiencing unexpected WARP statuses and dashboard readings. This has been raised as a priority, and our team is working to resolve it - we'll provide a further update as soon as possible.
Aug 27, 10:01 UTC
Aug 27, 10:01 UTC
Resolved -
A network configuration change resulted in a network routing issue within our infrastructure. This caused periods of degraded connectivity between application services and backend databases.
As a result, some customers experienced intermittent monitoring issues and a temporary interruption to data collection services. During the same period, the CAM+ website was also unavailable for approximately three hours because application services were unable to establish connections to the required databases.
Core alarm processing remained operational during the incident. However, the impact to monitoring functionality was initially limited to a subset of customers and was not immediately identified.
As network connectivity was progressively restored between 17:12 BST and 20:45 BST, queued alarm traffic was released and a significant volume of alarms required processing. This temporary increase in traffic placed additional demand on the alarm receiving infrastructure, resulting in delays to alarm processing and intermittent failures for remote alarm calls on WARP devices.
Alarm processing returned to normal operation at 22:08 BST.
Customer Impact
Customers may have experienced the following during the incident:
CAM+ website: Unavailable for approximately three hours.
Data collection: Intermittent or failed data collection from DC2 between approximately 14:50 BST and 20:45 BST.
CAM+ Backfill: Degraded performance while outstanding data was being recovered.
Alarm processing: Intermittent processing delays and delayed alarm notifications between approximately 15:23 BST and 22:08 BST.
WARP remote alarm calls: Some calls may have failed or experienced delays while the alarm processing infrastructure was handling the backlog.
Services Not Impacted
The following services remained operational throughout the incident:
Automated backfill services.
Core alarm processing capabilities.
Recovery and Remediation
Once network connectivity was restored, recovery activities were initiated to process outstanding data and ensure services returned to normal operation.
A backfill process was initiated overnight and remains in progress to restore any outstanding data affected during the period of degraded connectivity. Engineering teams are continuing to monitor the recovery process and validate the integrity and completeness of the recovered data.
Next Steps
Our engineering teams will continue to monitor the platform closely while recovery and validation activities are completed. We will also review the incident in detail to identify further preventative actions and improvements to our change management and monitoring processes.
Aug 28, 11:17 UTC
As a result, some customers experienced intermittent monitoring issues and a temporary interruption to data collection services. During the same period, the CAM+ website was also unavailable for approximately three hours because application services were unable to establish connections to the required databases.
Core alarm processing remained operational during the incident. However, the impact to monitoring functionality was initially limited to a subset of customers and was not immediately identified.
As network connectivity was progressively restored between 17:12 BST and 20:45 BST, queued alarm traffic was released and a significant volume of alarms required processing. This temporary increase in traffic placed additional demand on the alarm receiving infrastructure, resulting in delays to alarm processing and intermittent failures for remote alarm calls on WARP devices.
Alarm processing returned to normal operation at 22:08 BST.
Customer Impact
Customers may have experienced the following during the incident:
CAM+ website: Unavailable for approximately three hours.
Data collection: Intermittent or failed data collection from DC2 between approximately 14:50 BST and 20:45 BST.
CAM+ Backfill: Degraded performance while outstanding data was being recovered.
Alarm processing: Intermittent processing delays and delayed alarm notifications between approximately 15:23 BST and 22:08 BST.
WARP remote alarm calls: Some calls may have failed or experienced delays while the alarm processing infrastructure was handling the backlog.
Services Not Impacted
The following services remained operational throughout the incident:
Automated backfill services.
Core alarm processing capabilities.
Recovery and Remediation
Once network connectivity was restored, recovery activities were initiated to process outstanding data and ensure services returned to normal operation.
A backfill process was initiated overnight and remains in progress to restore any outstanding data affected during the period of degraded connectivity. Engineering teams are continuing to monitor the recovery process and validate the integrity and completeness of the recovered data.
Next Steps
Our engineering teams will continue to monitor the platform closely while recovery and validation activities are completed. We will also review the incident in detail to identify further preventative actions and improvements to our change management and monitoring processes.
Aug 28, 11:17 UTC
Identified -
All customer-facing services have now been restored and are operating normally.
We are continuing work behind the scenes to fully restore network connectivity and resilience. A backfill process was initiated overnight and remains in progress to recover any data affected during the incident.
We’re sorry for the disruption caused and will continue to monitor service stability closely.
Aug 26, 09:57 UTC
We are continuing work behind the scenes to fully restore network connectivity and resilience. A backfill process was initiated overnight and remains in progress to recover any data affected during the incident.
We’re sorry for the disruption caused and will continue to monitor service stability closely.
Aug 26, 09:57 UTC
Update -
Services have been restored through temporary measures while we continue to investigate the underlying network issue.
Alarm processing and call notifications are operating normally, automated backfill for the outage period has been initiated, and data logging has been restored.
The CAM+ Backfill app, accessed through the CAM+ website, continues to experience degraded performance.
Our Networking Team remains on site and is continuing to investigate the underlying issue. We’re sorry for the inconvenience caused and will provide a further update by 10:30 BST on August 2026.
Aug 25, 19:04 UTC
Alarm processing and call notifications are operating normally, automated backfill for the outage period has been initiated, and data logging has been restored.
The CAM+ Backfill app, accessed through the CAM+ website, continues to experience degraded performance.
Our Networking Team remains on site and is continuing to investigate the underlying issue. We’re sorry for the inconvenience caused and will provide a further update by 10:30 BST on August 2026.
Aug 25, 19:04 UTC
Update -
We’re continuing to work towards a resolution, and we’re sorry for the inconvenience this is causing. Our Networking Team remains on site, and all previously reported services are still affected.
Please continue to monitor sensor readings and alarms manually via the WARP display panel, as alarm notifications are not currently being delivered.
We’ll share a further update as soon as we have meaningful progress.
Aug 25, 17:04 UTC
Please continue to monitor sensor readings and alarms manually via the WARP display panel, as alarm notifications are not currently being delivered.
We’ll share a further update as soon as we have meaningful progress.
Aug 25, 17:04 UTC
Update -
We are continuing to investigate this issue.
Aug 25, 15:05 UTC
Aug 25, 15:05 UTC
Investigating -
Due to an overrun on planned maintenance, we are experiencing network issues.
Issue Description
The network issues are causing degraded performance for several services.
Impact
• Access to the CAM+ website may be affected.
• Logging of CAM+ data may be affected. Backfill will be initiated as soon as is practical.
• Alarm and alert notifications will not be sent via call, email or SMS.
Next Steps
• Our Networking Team are on-site and currently attending to the issue.
What You Should Do
• Continue to monitor sensor readings and alarms using the WARP display panel.
• Be aware that alarm notifications will not be delivered until the issue has been resolved.
Next Update
We will aim to issue an update before 18:00 BST today.
Aug 25, 15:04 UTC
Issue Description
The network issues are causing degraded performance for several services.
Impact
• Access to the CAM+ website may be affected.
• Logging of CAM+ data may be affected. Backfill will be initiated as soon as is practical.
• Alarm and alert notifications will not be sent via call, email or SMS.
Next Steps
• Our Networking Team are on-site and currently attending to the issue.
What You Should Do
• Continue to monitor sensor readings and alarms using the WARP display panel.
• Be aware that alarm notifications will not be delivered until the issue has been resolved.
Next Update
We will aim to issue an update before 18:00 BST today.
Aug 25, 15:04 UTC
Resolved -
Issue Resolved
Aug 28, 11:15 UTC
Aug 28, 11:15 UTC
Update -
During periods of increased system demand, backend services may automatically scale as designed. In some circumstances though, these instances may be deployed on the same underlying host as an existing backend instance or alongside other services that place significant demand on available resources.
To improve infrastructure resilience and minimise the potential impact of resource contention, we are implementing a placement strategy that limits each host to a single backend API instance. This provides greater separation between backend services, helps distribute resource utilisation more evenly across the infrastructure, and reduces the potential for a single host to impact multiple production instances.
Aug 28, 11:12 UTC
To improve infrastructure resilience and minimise the potential impact of resource contention, we are implementing a placement strategy that limits each host to a single backend API instance. This provides greater separation between backend services, helps distribute resource utilisation more evenly across the infrastructure, and reduces the potential for a single host to impact multiple production instances.
Aug 28, 11:12 UTC
Monitoring -
We have identified an issue with our backend services and have implemented actions to mitigate. Performance has since returned to within acceptable levels and we are continuing to monitor the situation and work on a permanent fix.
Aug 4, 09:22 UTC
Aug 4, 09:22 UTC
Investigating -
We're currently investigating intermittent performance issues. Some users may experience slower response times when loading pages or running queries in Control Centre. We're monitoring closely and will post updates as we learn more.
Jul 31, 11:06 UTC
Jul 31, 11:06 UTC
Aug 27, 2026
Aug 26, 2026
Aug 25, 2026
Aug 24, 2026
No incidents reported.
Aug 23, 2026
No incidents reported.
Aug 22, 2026
No incidents reported.
Aug 21, 2026
No incidents reported.
Aug 20, 2026
Resolved -
Monitoring failure alerts affecting some UK and US data collection services have been resolved.
The issue was linked to services temporarily migrated during planned network infrastructure work. High storage latency degraded performance for a subset of services and generated monitoring alerts.
All affected services have been restored, with the last monitoring alert recorded at 17:07 BST 19th August. We will review the incident to help prevent recurrence.
Aug 20, 08:32 UTC
The issue was linked to services temporarily migrated during planned network infrastructure work. High storage latency degraded performance for a subset of services and generated monitoring alerts.
All affected services have been restored, with the last monitoring alert recorded at 17:07 BST 19th August. We will review the incident to help prevent recurrence.
Aug 20, 08:32 UTC
Aug 19, 2026
No incidents reported.