Incidents reported on status page for Gorelo https://status.gorelo.io/ https://d1lppblt9t2x15.cloudfront.net/logos/2a07330ceefd30ff84135bbcf215ccb3.png https://status.gorelo.io/ en https://status.gorelo.io/incident/922294 Sat, 20 Jun 2026 12:38:29 -0000 https://status.gorelo.io/incident/922294#7ac8544c823f7daedd96a074c4980fbc79d2232b8c8a6e8941eeffcf941eb985 Maintenance completed https://status.gorelo.io/incident/922294 Sat, 20 Jun 2026 07:00:00 -0000 https://status.gorelo.io/incident/922294#0905642494bd8738cea0301b3be3eee1625e15b9f31f8f615f427b13a6657263 As part of our Australia East region migration, we will be migrating data for tenants that opted into the AU migration. Important: Please do not create, update, or post any data during this window — changes made during this period will be lost. Incoming data from external integrations (inbound emails, invoice webhooks, automations, and triggers) will not be processed during the window. After the switchover, Public API users must update their endpoint from https://api.usw.gorelo.io/ to https://api.aue.gorelo.io/ We will confirm once the migration is complete. https://status.gorelo.io/incident/922291 Fri, 19 Jun 2026 07:00:00 -0000 https://status.gorelo.io/incident/922291#01d65676b1c2015213c4760cb2d6897eadc61f8bd186e22be6b3cc09ced041de As part of our Australia East region migration, we will be performing Asset Migration for tenants that opted into the AU migration. To ensure a smooth migration, please have as many of your assets online as possible. If any devices are currently offline, try to bring them online over the coming days so they can migrate across — any assets offline during the window will migrate automatically the next time they come online. No outage is expected and no action is required. Users actively working during this window may experience an automatic app refresh, and native application users will be logged out and need to sign in again. Application performance may be temporarily degraded until the data cutover completes on 20 June. https://status.gorelo.io/incident/908083 Fri, 29 May 2026 21:51:00 -0000 https://status.gorelo.io/incident/908083#bf27f957ce5583064204d0e81be052a19b659aa89cbf026791bee524aee7edeb Microsoft has confirmed the underlying infrastructure issue in West US 2 has been mitigated, with the vast majority of downstream services restored. Log Analytics remains in active mitigation upstream, which continues to limit some of our internal observability, but all customer-facing services have returned to normal operation. We are marking this incident resolved. https://status.gorelo.io/incident/908083 Fri, 29 May 2026 21:01:00 -0000 https://status.gorelo.io/incident/908083#46009d3244aa678253a50a6c5c6fdc5e3e9e59efc8c0534ef6cf98ff68d0a763 Microsoft has confirmed that datacenter utility power in West US 2 has been fully restored. Cooling has normalized, and the majority of upstream network and storage infrastructure has recovered. Two storage components are still completing final recovery and data integrity validation, with Microsoft estimating full restoration within the next couple of hours. On our side, service metrics remain within baseline range and we have not observed any further degradation since this morning. We are continuing to monitor closely as the remaining upstream components finish validation, and will confirm full mitigation once Azure declares the event resolved. https://status.gorelo.io/incident/908083 Fri, 29 May 2026 18:00:00 -0000 https://status.gorelo.io/incident/908083#6c7a54b8b8f961a69c84494b0cdac1c874c4c868bbc2e0559729d5b9067bf0f6 We are not out of the woods yet. Azure has provided a more detailed update. Cause: Severe thunderstorm hit the West US 2 datacenter at ~04:27 UTC. Complete utility power loss, generator failover partially failed (synchronization + thermal protection issues), cooling systems also failed. Cascading failure exceeded N+1 redundancy. This has been ongoing for 13+ hours. Services still impacted: Azure SQL - DB Redis - Cache Azure Functions - Webhooks, edge compute Storage Application Insights/Log Analytics VMs/Container Apps - Compute We are monitoring metrics available for each of the above services. Log Analytics is the only service no longer live for us. The rest of the services are within range of baseline metrics. https://status.gorelo.io/incident/908083 Fri, 29 May 2026 15:30:00 -0000 https://status.gorelo.io/incident/908083#5b1ff30bb089d8c026ee357e3424b7008f94ce3858db01ea7e47decc92ed282f Although we do not have an "all clear" from Azure, we have seen most service metrics return to baseline. The logging service is still down (Log Analytics) so we aren't able to see traces and errors. We do not believe this outage caused any loss of data in transit or at rest. Timeline: Though Azure reported their power event at 4:30 UTC, we started to see first impacts to our service at around 8am UTC. We then saw intermittent impact to emails, connectivity and backend performance until 17:30 UTC. Since then, we have seen metrics return to normal. We will provide a more detailed outage report once the event is clearly behind us. https://status.gorelo.io/incident/908083 Fri, 29 May 2026 13:00:00 -0000 https://status.gorelo.io/incident/908083#30509535e7bbe98de5ef2822161bdedea24e895e363b22746772aa28b5b1c8b0 We are monitoring a power outage related incident currently underway at the Azure USW region. We have noticed elevated error rates in email delivery and device authentication. We will post updates as they are made available. Further details about the incident and it's recovery are also available here. https://azure.status.microsoft/en-us/status https://status.gorelo.io/incident/901139 Fri, 22 May 2026 01:35:00 -0000 https://status.gorelo.io/incident/901139#8d173bec529a1a0c4e3d2257628c01e59c1552bacad87faaffff2637e37b4996 A summary of the recent IoT Hub disruption is now available at the link below. Appreciate your patience throughout. https://gorelo.notion.site/IoT-Hub-Connectivity-May-20-2026-36664c67933980e4be7fccbf15efd94d https://status.gorelo.io/incident/901139 Wed, 20 May 2026 22:50:00 -0000 https://status.gorelo.io/incident/901139#74d15eb6832ca8d9609df01ea2eef4234c2b2fcd1f122bf27213956761e94edc The issue has been resolved following the changes applied by Microsoft on the Azure IoT Hub platform. Assets have reconnected and status reporting is back to normal. You can now re-add the Connectivity check to your Base Server policy (or equivalent). Appreciate your patience and a post incident report will follow in the coming days. https://status.gorelo.io/incident/901139 Wed, 20 May 2026 22:31:00 -0000 https://status.gorelo.io/incident/901139#fbc7167e9fcc897c43c0dd4329dc0a10a9da49c4a93c309001c320d3f5a305c3 Microsoft support engineers have applied changes on the Azure IoT Hub side, and assets are beginning to recover. We're monitoring as connectivity restores across the fleet. If you applied the Connectivity check workaround, please hold off on reverting until we confirm full recovery. A final update will follow. https://status.gorelo.io/incident/901139 Wed, 20 May 2026 20:51:00 -0000 https://status.gorelo.io/incident/901139#e839d75f9b26c27f4969c58ee2183f65d229d6598c4f474b8ea61d2965c78c97 We are now actively engaged with a Microsoft support engineer who is investigating the issue on the Azure IoT Hub platform. We'll continue to share progress as we receive it. Workaround: To reduce alert fatigue, we recommend temporarily removing the Connectivity check from your Base Server policy (or equivalent) until the issue is resolved. Please note that affected assets will need to come online long enough for the policy change to be distributed, which may be intermittent given the current connectivity issues. We are also investigating options to suppress these false positive Connectivity alerts globally on our side. Further updates to follow. https://status.gorelo.io/incident/901139 Wed, 20 May 2026 20:49:00 -0000 https://status.gorelo.io/incident/901139#f7768adef0bd89754e6498cc261f8d9508896c21ed1f5b7ba5999be317c96856 The connectivity issue has been traced to a throttling error on the Azure IoT Hub platform. A support case has been raised with Microsoft Azure. Workaround: To reduce alert fatigue, we recommend temporarily removing the Connectivity check from your Base Server policy (or equivalent) until this is resolved. Updates to follow. https://status.gorelo.io/incident/901139 Wed, 20 May 2026 20:05:00 -0000 https://status.gorelo.io/incident/901139#992158e5b4538e62828e53f818aa7ab94a7499f76795e904b98ec0f15cb7bcc2 We are currently investigating an outage affecting our IoT Hub, which has caused a number of assets to disconnect and is resulting in inaccurate offline status reporting across the platform. Underlying device functionality is not impacted. Updates to follow.