Incidents reported on status page for SQLWATCH https://status.sqlwatch.cloud/ https://d1lppblt9t2x15.cloudfront.net/logos/66a09b43706d105971b8d6c6acca33d1.png https://status.sqlwatch.cloud/ en https://status.sqlwatch.cloud/incident/886434 Tue, 05 May 2026 16:09:00 -0000 https://status.sqlwatch.cloud/incident/886434#7b5485bd32609d61c8b6ba8cf27b745d36937eb5d0591781523fdd5ed6cbc4b6 Resolved - Service Disruption Final Update May 5, 2026 - 16:00 UTC SQLWATCH monitoring services in West Europe are now fully restored and operating normally. Incident summary: - Initial impact: 14:25 UTC May 3, 2026 - Complete outage: 14:25 UTC May 3 to approximately 22:00 UTC May 3 (~7.5 hours) - Degraded performance: 22:00 UTC May 3 to 16:00 UTC May 5 (~42 hours) - Full restoration: 16:00 UTC May 5, 2026 - Total impact duration: approximately 50 hours Despite the severity and duration of the Azure incident, only 2 customers were directly affected, thanks to our architecture, which distributes customers across independent deployments across multiple availability zones. All other customers experienced no disruption throughout the incident The root cause was an Azure platform failure affecting Virtual Machines and underlying storage infrastructure in the West Europe region, which Azure formally confirmed ran from 14:12 UTC May 3 to 11:45 UTC May 5 - over 45 hours. The failure caused a complete loss of storage connectivity. Following Azure's recovery, an unrelated configuration issue on our side caused continued IO saturation and performance degradation. When our platform remained degraded after Azure declared their incident resolved, we began investigating independently and identified and resolved the configuration issue by 16:00 UTC May 5. We will be publishing a full post-incident review shortly, covering what happened in detail, what we got wrong, and what we are doing to prevent a recurrence. We sincerely apologise for the disruption. Azure tracking IDs: KHF9-2HG / GPR8-2LG https://status.sqlwatch.cloud/incident/888177 Tue, 05 May 2026 15:30:11 -0000 https://status.sqlwatch.cloud/incident/888177#e53d2de5c15222643e3331d3b4b7abb79ac923132d8d1586951ff16eefe2b9c5 We will be conducting maintenance on our West Europe infrastructure to implement improvements following yesterday's service disruption. During this window, monitoring services for West Europe customers may be briefly interrupted or experience degraded performance. This maintenance is part of our ongoing efforts to improve platform resilience. We will update this notice once maintenance is complete. We apologise for the short notice. https://status.sqlwatch.cloud/incident/886434 Tue, 05 May 2026 08:50:00 -0000 https://status.sqlwatch.cloud/incident/886434#2beaa386270b8b520300312999eb3315d7de7f1ad31d9d715fddafbbb4e6442a Monitoring - Monitoring Service Disruption (Update 6) May 5, 2026 - 10:00 BST Despite earlier signs of recovery, we have been made aware that the underlying Azure platform incident remains partially unresolved. Microsoft has confirmed that a subset of Virtual Machines using Premium SSD v2 disks in West Europe continue to be affected, with recovery still in progress as of this morning. Our services are currently operational however we are experiencing storage performance degradation as a result of the ongoing infrastructure issue. This is affecting platform responsiveness and data processing speed for West Europe customers. In parallel with waiting for Microsoft to resolve the underlying infrastructure issue, we are actively exploring additional measures to restore full performance independently of Azure's recovery timeline. Microsoft has indicated their next update will be within 12 hours. We will post an update sooner if our service status changes. Azure tracking IDs: KHF9-2HG / GPR8-2LG https://status.sqlwatch.cloud/incident/886434 Sun, 03 May 2026 23:25:00 -0000 https://status.sqlwatch.cloud/incident/886434#f328a9d9058aa443aff2cd9dd3180468d73c528c03dd1c2fd7405a5115e11633 Monitoring – Monitoring Service Disruption (Update 5) May 4, 2026 – 00:25 BST Azure has confirmed the West Europe platform incident is fully mitigated. Our services have recovered and data collection has resumed. We are continuing to monitor performance closely and will confirm full resolution once we are satisfied everything is operating normally. Azure tracking IDs: KHF9-2HG / GPR8-2LG https://status.sqlwatch.cloud/incident/886434 Sun, 03 May 2026 22:00:00 -0000 https://status.sqlwatch.cloud/incident/886434#e96aa95b4e023d070815dc80bab66718e67a2a6a1fc24e6a6484dfb35ec4bd4b Recovering – Monitoring Service Disruption (Update 4) May 3, 2026 – 23:00 BST Our West Europe infrastructure has recovered following the Azure platform incident. Services are recovering and data collection has resumed, however dashboards and queries may be slow to respond while the underlying storage infrastructure stabilises. We are monitoring performance closely and expect full recovery as Azure completes remediation of the affected storage layer. No data has been lost. We will post a final update once performance has returned to normal. All other SQLWATCH regions remain fully operational. Azure tracking IDs: KHF9-2HG / GPR8-2LG https://status.sqlwatch.cloud/incident/886434 Sun, 03 May 2026 21:30:00 -0000 https://status.sqlwatch.cloud/incident/886434#48a9c9b87e4c712bbbce47c542847cbe5444d1854485a56e574f397d5a929eee Investigating – Monitoring Service Disruption (Update 3) May 3, 2026 – 22:35 BST Azure has provided a further update on the ongoing platform incident affecting our West Europe infrastructure. Recovery is progressing for many affected resources, with some VM and disk operations now succeeding. However, Azure has identified a subset of storage infrastructure requiring a longer recovery path and has isolated it for targeted remediation. Resources associated with this isolated infrastructure - which may include ours - do not have an estimated recovery time. Some of our West Europe services remain unavailable. We will continue monitoring and post a further update as soon as there is meaningful progress to report. All other SQLWATCH regions remain fully operational. Azure tracking IDs: KHF9-2HG / GPR8-2LG https://status.sqlwatch.cloud/incident/886434 Sun, 03 May 2026 17:35:00 -0000 https://status.sqlwatch.cloud/incident/886434#7ccefe7b6ef29170c8d5f57680c9d96e3454b1140f374fdf20a35edaafc16798 Investigating - Monitoring Service Disruption (Update 2) May 3, 2026 - 18:35 BST Azure has provided an update on the ongoing platform incident (tracking ID: KHF9-2HG) affecting our West Europe infrastructure. The incident has been traced to degraded storage infrastructure (Azure Direct Drive) underpinning Virtual Machines in the West Europe region, with impact beginning at 15:12 BST. Azure has begun restarting affected infrastructure but has not provided an estimated time to resolution. We will share a further update once Azure confirms recovery is complete. All other SQLWATCH regions remain fully operational. Azure tracking ID: KHF9-2HG https://status.sqlwatch.cloud/incident/886434 Sun, 03 May 2026 15:58:00 -0000 https://status.sqlwatch.cloud/incident/886434#89bab2c4979c019ff92219a334c0a36c7bbbf58824480a87974348f17a4ec905 Investigating - Monitoring Service Disruption May 3, 2026 - 16:00 UTC We are currently experiencing a disruption to our monitoring infrastructure hosted in Azure West Europe. This is caused by an active Azure platform incident (tracking ID: KHF9-2HG) affecting Virtual Machines in the West Europe region, which began at approximately 14:25 UTC. Data collection and alerting may be impaired for some or all monitored servers during this period. We are monitoring the Azure incident and will post updates as the situation develops. You can track the Azure incident directly via the Azure Service Health portal. https://status.sqlwatch.cloud/incident/886434 Sun, 03 May 2026 14:35:00 -0000 https://status.sqlwatch.cloud/incident/886434#66912f8302e854b31cb227d6e091d8b850a6054ef1a7130acbcdb22707c5016e Investigating - Service Disruption May 3, 2026 - 14:35 UTC We are investigating a disruption to our monitoring infrastructure in West Europe. We became aware of the issue at 14:26 UTC and are currently assessing the impact. Data collection and alerting may be impaired during this period. We will post a further update as soon as we have more information. https://status.sqlwatch.cloud/incident/801571 Fri, 09 Jan 2026 22:00:06 -0000 https://status.sqlwatch.cloud/incident/801571#1e96e160c00e5c055b813cfb2801c2004ff929d2624be8853da157954cf04bf2 We will be conducting essential maintenance to upgrade our systems. This maintenance window is necessary to enhance our services and ensure better performance and security. During this time, our services may be intermittently unavailable. We appreciate your understanding and patience as we work to improve your experience. If you have any questions or concerns, please contact our support team. https://status.sqlwatch.cloud/incident/801295 Fri, 09 Jan 2026 11:00:13 -0000 https://status.sqlwatch.cloud/incident/801295#52722139532eb414a23ca5f4217edcfc03fc34e1a4e573a5c07005eafa1f1bbc We will be conducting essential maintenance to upgrade our systems. This maintenance window is necessary to enhance our services and ensure better performance and security. During this time, our services may be intermittently unavailable. We appreciate your understanding and patience as we work to improve your experience. If you have any questions or concerns, please contact our support team. https://status.sqlwatch.cloud/incident/800934 Thu, 08 Jan 2026 22:00:33 -0000 https://status.sqlwatch.cloud/incident/800934#1694290fbfb680f6f3e538c4398cbb723d0bc9d26bb902c68c6d59216b6374c0 We will be conducting essential maintenance to upgrade our systems. This maintenance window is necessary to enhance our services and ensure better performance and security. During this time, our services may be intermittently unavailable. We appreciate your understanding and patience as we work to improve your experience. If you have any questions or concerns, please contact our support team. https://status.sqlwatch.cloud/incident/800678 Thu, 08 Jan 2026 13:00:39 -0000 https://status.sqlwatch.cloud/incident/800678#d68d091ac2578cb5062478d1bdc1647fb6d2200f95574f12c4682d257e99fd30 We will be conducting essential maintenance to upgrade our systems. This maintenance window is necessary to enhance our services and ensure better performance and security. During this time, our services may be intermittently unavailable. We appreciate your understanding and patience as we work to improve your experience. If you have any questions or concerns, please contact our support team. https://status.sqlwatch.cloud/incident/798667 Mon, 05 Jan 2026 10:45:00 -0000 https://status.sqlwatch.cloud/incident/798667#452764f091bcc5ac6d6dabd2826b7d807c64bcbbf3e10dbafd911db3db218fb2 We will be conducting essential maintenance to upgrade our systems. This maintenance window is necessary to enhance our services and ensure better performance and security. During this time, our services may be intermittently unavailable. We appreciate your understanding and patience as we work to improve your experience. If you have any questions or concerns, please contact our support team. https://status.sqlwatch.cloud/incident/792730 Tue, 23 Dec 2025 01:00:30 -0000 https://status.sqlwatch.cloud/incident/792730#e50a841a90a8044a880272db720a12d995e70b41e8f7a2ae800ad5dbba7fb6fc We will be conducting essential maintenance to upgrade our systems. This maintenance window is necessary to enhance our services and ensure better performance and security. During this time, our services may be intermittently unavailable. We appreciate your understanding and patience as we work to improve your experience. If you have any questions or concerns, please contact our support team. https://status.sqlwatch.cloud/incident/792692 Mon, 22 Dec 2025 23:30:40 -0000 https://status.sqlwatch.cloud/incident/792692#6907fd0065f9c5ec6ff6d782013f8b3b5e55c4e0f4c9bf5f25805596f69d1ee2 We will be conducting essential maintenance to upgrade our systems. This maintenance window is necessary to enhance our services and ensure better performance and security. During this time, our services may be intermittently unavailable. We appreciate your understanding and patience as we work to improve your experience. If you have any questions or concerns, please contact our support team. https://status.sqlwatch.cloud/incident/792651 Mon, 22 Dec 2025 21:45:11 -0000 https://status.sqlwatch.cloud/incident/792651#9a533bea25486d683427b379add741b543947d2e56a61ee82ea9cce9ae0b3469 We will be conducting essential maintenance to upgrade our systems. This maintenance window is necessary to enhance our services and ensure better performance and security. During this time, our services may be intermittently unavailable. We appreciate your understanding and patience as we work to improve your experience. If you have any questions or concerns, please contact our support team. https://status.sqlwatch.cloud/incident/792394 Mon, 22 Dec 2025 12:00:00 -0000 https://status.sqlwatch.cloud/incident/792394#9bcecd0197642a8564455f62eee5615eaedf034553e4633ef914af0ae434de67 We will be conducting essential maintenance to upgrade our systems. This maintenance window is necessary to enhance our services and ensure better performance and security. During this time, our services may be intermittently unavailable. We appreciate your understanding and patience as we work to improve your experience. If you have any questions or concerns, please contact our support team. https://status.sqlwatch.cloud/incident/792374 Mon, 22 Dec 2025 11:00:27 -0000 https://status.sqlwatch.cloud/incident/792374#28228f0e29dbb752c9d656b5c807af929ae8f70f8498aa82d8bbd71fc8123e30 Maintenance completed https://status.sqlwatch.cloud/incident/792374 Mon, 22 Dec 2025 10:00:27 -0000 https://status.sqlwatch.cloud/incident/792374#e7ce6b6c46ac20567d9b9c1dcf4952cd71f1df89289a13f23c43e7cc55ab03c4 We will be conducting essential maintenance to upgrade our systems. This maintenance window is necessary to enhance our services and ensure better performance and security. During this time, our services may be intermittently unavailable. We appreciate your understanding and patience as we work to improve your experience. If you have any questions or concerns, please contact our support team. https://status.sqlwatch.cloud/incident/786490 Mon, 15 Dec 2025 00:00:00 -0000 https://status.sqlwatch.cloud/incident/786490#3ccf6185790b790b1ac8b539b7b626a2fa9b013e501f409524b03668c7d095d1 We will be conducting essential maintenance to upgrade our systems. This maintenance window is necessary to enhance our services and ensure better performance and security. During this time, our services may be intermittently unavailable. We appreciate your understanding and patience as we work to improve your experience. If you have any questions or concerns, please contact our support team. https://status.sqlwatch.cloud/incident/785455 Sat, 13 Dec 2025 00:00:08 -0000 https://status.sqlwatch.cloud/incident/785455#4194a2e4e2908d1d63025c5d2a4290a859e4c316affce6af89a34b78635614fd We will be conducting essential maintenance to upgrade our systems. This maintenance window is necessary to enhance our services and ensure better performance and security. During this time, our services may be intermittently unavailable. We appreciate your understanding and patience as we work to improve your experience. If you have any questions or concerns, please contact our support team. https://status.sqlwatch.cloud/incident/768846 Tue, 18 Nov 2025 15:19:00 -0000 https://status.sqlwatch.cloud/incident/768846#23ec42eecb9382d9e0b62da79e86b818c44bb5fe88f929ecc0b84f1fdd8da1a6 Cloudflare has confirmed they have resolved the issue https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 https://status.sqlwatch.cloud/incident/768846 Tue, 18 Nov 2025 12:13:00 -0000 https://status.sqlwatch.cloud/incident/768846#a738c26b478b113a3885adef5b15a14b0350a78738b5f4316344d618fe8d733d We are aware of a global Cloudflare outage affecting our services. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 https://status.sqlwatch.cloud/incident/742665 Mon, 13 Oct 2025 12:42:00 -0000 https://status.sqlwatch.cloud/incident/742665#13fc01b4c298d557476d90b71ccf928d553d2b87b38c1a2a8670395bd0dca268 We have received confirmation from FortiNet that they have updated the categorisation, but it may take some time for the network devices to reflect this change. https://status.sqlwatch.cloud/incident/742665 Mon, 13 Oct 2025 11:55:00 -0000 https://status.sqlwatch.cloud/incident/742665#ca39b3d7ec9b0f70455b489a18596e1404b017d61f8eb4b93794cee896893eb4 We are aware that FortiGuard is currently preventing connections to our endpoints. We raised this issue with FortiNet. In the meantime, customers who use FortiGuard should whitelist *.sqlwatch.cloud domain. https://status.sqlwatch.cloud/incident/732766 Fri, 26 Sep 2025 09:45:00 -0000 https://status.sqlwatch.cloud/incident/732766#3ea25b09cc352cd20760ebbd596580f396ddeebfec75ef06f2cb8964f68d6ac0 Service may be briefly unavailable whilst we carry out essential upgrades. https://status.sqlwatch.cloud/incident/603939 Mon, 16 Jun 2025 14:17:00 -0000 https://status.sqlwatch.cloud/incident/603939#5cb94926786b9a76c0e047855f894a24a3dc61051a300bd8d38ad599e47fac54 Data collection and retrieval may be temporarily disrupted whilst we carry out maintenance. https://status.sqlwatch.cloud/incident/533792 Mon, 24 Mar 2025 22:00:24 -0000 https://status.sqlwatch.cloud/incident/533792#0ccd8727f13a0ab08abd2439b1edd2b7fb31bc160db45007e73e3d877775a15d During this maintenance window, data collection may be temporarily interrupted, and the web application may be unavailable briefly. https://status.sqlwatch.cloud/incident/524616 Sat, 08 Mar 2025 02:30:51 -0000 https://status.sqlwatch.cloud/incident/524616#a65b0937e526f5446cbe881c1fb491190c2867a883f0b9e2528d776c357f9cd7 Data collection may be interrupted during maintenance https://status.sqlwatch.cloud/incident/524615 Sat, 08 Mar 2025 02:00:00 -0000 https://status.sqlwatch.cloud/incident/524615#9fc444d23c6aba87d99ada685178ba1c8afac7158a48e4c1bfee60944ff13208 Data collection may be interrupted during maintenance https://status.sqlwatch.cloud/incident/523958 Thu, 06 Mar 2025 23:00:17 -0000 https://status.sqlwatch.cloud/incident/523958#17014c4596123eba1e75d501423f1564e76a0ca9a47152b90e567910d7e2a916 Data collection may be interrupted whilst we carry out essential upgrades and maintenance. https://status.sqlwatch.cloud/incident/479315 Tue, 17 Dec 2024 00:00:00 -0000 https://status.sqlwatch.cloud/incident/479315#a552a136c5b3facf940e3b38962fc01d85b7d08c1c3ef950353a0908d767f9d9 We are upgrading our infrastructure in Europe West. As a result, data collection may be delayed, and dashboards may be unavailable for a short period.