Incident history
Incidents per month last 12 months
July 2026 · 3 incidents
Backup job failed on lbreeze.cloud
1 update ▾
An issue affected service and has been resolved. Reference: INC-2026-0281.
1 IP block failing on vss1.lbreeze.com — cpfence returned rc1
3 updates ▾
Resolved. Internal ref: INC-2026-0268.
Fix applied — monitoring for 30 minutes before we call this resolved. Internal ref: INC-2026-0268.
We're investigating an issue affecting service. Reference: INC-2026-0268.
CPU above 50% on vir.secfolk.com
6 updates ▾
Resolved. Internal ref: INC-2026-0217.
It’s been resolved
testing investigation
Resolved. Internal ref: INC-2026-0217.
Resolved. Internal ref: INC-2026-0217.
We're investigating an issue affecting service. Reference: INC-2026-0217.
June 2026 · 4 incidents
Backup job failed on backupd1.lbreeze.net
2 updates ▾
Resolved. Internal ref: INC-2026-0044.
We're investigating an issue affecting service. Reference: INC-2026-0044.
Inodes used > 60% on backupd2.lbreeze.com
5 updates ▾
Resolved.
We are currently investigating a storage usage issue on our backup servers. This may impact some backup processes. We will provide an update as soon as more information is available.
Resolved. Internal ref: INC-2026-0029.
Backup server storage is full
We're investigating an issue affecting service. Reference: INC-2026-0029.
8/27 monitors degraded
2 updates ▾
Auto-detected recovery at 17:35 UTC — all affected monitors back to OK.
Automatically opened by monitor detector. 8 monitors failed simultaneously, suggesting shared infrastructure issue.
3/7 monitors degraded
2 updates ▾
Auto-detected recovery at 05:21 UTC — all affected monitors back to OK.
Automatically opened by monitor detector. 3 monitors failed simultaneously, suggesting shared infrastructure issue.