Current Outage History
6 incidents recorded over the last 365 days, 6 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Current Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 28, 2026 | [Azure ServiceHealth] Network Infrastructure - West Europe**Degraded connectivity in Azure West Europe** Since 17:36 UTC, customers may experience increased latency or intermittent connection issues when accessing databases hosted in Azure West Europe. Azure has identified a… | 1h 27m | Resolved |
| Oct 9, 2026 | Tiger Cloud Databases running on Azure West Europe RegionStarting at approximately 12:30 UTC, some Tiger Cloud database services running in our Azure West Europe region became unavailable. The disruption was caused by an incident on the Microsoft Azure platform (Azure… | 1h 31m | Resolved |
| Oct 8, 2026 | Azure VM stability issues in Germany West CentralCustomers may experience service availability issues in Germany West Central due to ongoing problems affecting Azure in the region. We are monitoring the situation and will provide updates as more information becomes… | 28 min | Resolved |
| Sep 24, 2026 | Azure services under new projects are taking longer to startWe have identified an issue affecting service provisioning in newly created Azure projects across all regions. | 38 min | Resolved |
| Sep 22, 2026 | Degraded state in Azure Germany West CentralImpact Statement: Starting at 12:04 UTC on 22 September 2026, you have been identified as a customer using Azure Virtual Machines (VMs) and Virtual Machine Scale Sets (VMSS) in Germany West Central who may experience… | 4h 9m | Resolved |
| Sep 16, 2026 | Support cases are not visible in the console due to a third-party outageWe are still awaiting resolution of the ongoing issue on Salesforce's side. For the latest updates and additional details, please refer to the [Salesforce Status… | 6h 15m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Current incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Current Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Current acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Current outage in this window ran 6h 15m, against a mean recovery of 2h 25m. If you depend on Current in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.