SIGNL4 incident

Issue with 3rd party connector for Microsoft Azure Monitor

Resolved after 13 hours 30 minutes, on January 9, 2025.

resolved Jan 10, 2025, 12:30 PM UTC

Azure Monitor REST API seems to be available again. Azure Monitor integrations in SIGNL4 should recover soon at their next scheduled reconnect attempt. You may trigger an immediate reconnect manually by disabling and enabling the corresponding integration in the SIGNL4 portal.

Started
Jan 09, 2025, 11:00 PM UTC
Resolved
Jan 10, 2025, 12:30 PM UTC
Duration
13h 30m
Detected by Pingoru
Jan 09, 2025, 11:00 PM UTC

Update timeline

  1. identified Jan 09, 2025, 11:00 PM UTC

    We have identified an issue with connector connectivity to Microsoft Azure Monitor. Since around 01/10/2025 00:10 CET time the Azure Monitor integration is unable to communicate with the Microsoft Azure Monitor API anymore (gets response timeouts). This issue is related to problems with “Microsoft Azure Alerts” and appears as confirmed issue in affected Microsoft Azure tenants under help and support. It may also be related to issues outlined here https://azure.status.microsoft/en-us/status. Microsoft is working on a resolution of this problem.

  2. resolved Jan 10, 2025, 12:30 PM UTC

    Azure Monitor REST API seems to be available again. Azure Monitor integrations in SIGNL4 should recover soon at their next scheduled reconnect attempt. You may trigger an immediate reconnect manually by disabling and enabling the corresponding integration in the SIGNL4 portal.

Your product runs on more than SIGNL4

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →