SIGNL4 Outage History

SIGNL4 is up right now

Pingoru has recorded 8 incidents for SIGNL4: 2 in the last 12 months and 0 in the last 90 days.

Source: status.signl4.com

8incidents recorded
2last 12 months
0last 90 days
22 hourstypical duration

Incidents, newest first

Minor December 1, 2025 Connector applications issue 23h 58m

Started Dec 01, 2025, 03:31 PM UTC· resolved Dec 02, 2025, 03:29 PM UTC

  1. investigating Dec 01, 2025, 03:31 PM UTC

    We are investigating an issue with several third-party connectors that may intermittently fail to receive data or load their configuration in the web portal.

  2. identified Dec 02, 2025, 09:01 AM UTC

    The team is currently developing a procedure to restore the affected third-party connectors. We will provide further updates as soon as they become available.

  3. monitoring Dec 02, 2025, 11:08 AM UTC

    We are observing recovery in the affected third-party connectors and will continue to closely monitor the application.

  4. resolved Dec 02, 2025, 03:29 PM UTC

    No further problems were noticed, and all connectors are functioning normally again.

Read the full incident report →

Minor November 10, 2025 Phone calls / call routing impaired 20h 52m

Started Nov 10, 2025, 11:13 AM UTC· resolved Nov 11, 2025, 08:05 AM UTC

  1. investigating Nov 10, 2025, 11:13 AM UTC

    There are currently disruptions with call forwarding. However, this currently affects only SIGNL4 call forwarding numbers that begin with +49158. We are currently working together with the telephony infrastructure provider to resolve this issue.

  2. monitoring Nov 10, 2025, 04:57 PM UTC

    We've been notified by our telephony infrastructure provider that calls to numbers beginning with +49158 are recovering. We'll continue to monitor the situation and provide another update as soon as it becomes available.

  3. resolved Nov 11, 2025, 08:05 AM UTC

    The issue affecting phone calls to call routing numbers in the +4915888 range has been resolved by the telephony infrastructure provider.

Read the full incident report →

Minor October 20, 2025 Voice and Text delivery impaired 22h 16m

Started Oct 20, 2025, 10:14 AM UTC· resolved Oct 21, 2025, 08:30 AM UTC

  1. investigating Oct 20, 2025, 10:14 AM UTC

    We are currently investigating issues affecting Text and Voice Call functions, including call forwarding. The root cause has been identified as a problem with one of our communication providers. We are closely monitoring the situation and will provide updates as soon as they become available.

  2. monitoring Oct 20, 2025, 01:20 PM UTC

    We are observing partial recovery with improved delivery rates for Text and Voice Call messages. We will continue to monitor the situation and provide further updates as necessary.

  3. resolved Oct 21, 2025, 08:30 AM UTC

    Our communication provider has confirmed that all issues have been resolved. After extended monitoring, we are observing normal delivery rates for Text and Voice Call messages. The incident is now considered fully resolved.

Read the full incident report →

Minor May 30, 2025 Email delivery impaired –

Started May 30, 2025, 10:19 AM UTC· resolved May 30, 2025, 10:19 AM UTC

  1. resolved May 30, 2025, 10:19 AM UTC

    There are currently isolated problems with email delivery. We are working on a solution to the problem. We have changed the main outgoing email address IP to 132.220.132.233 but this IP is new to many mail servers. Update: While this IP and the main DNS of mail.signl4.com is not blacklisted anymore and outgoing email traffic has normalized, please make sure to explicitly whitelist the new IP with your mail server, if applicable.

Read the full incident report →

Minor March 31, 2025 Account Portal Issues –

Started Mar 31, 2025, 07:06 AM UTC· resolved Mar 31, 2025, 07:06 AM UTC

  1. resolved Mar 31, 2025, 07:06 AM UTC

    Some users may experience content loading issues on multiple pages of the account management portal. This is due to unavailability of external libraries. We expect service restauration shortly. We keep you updated on the resolution progress.

Read the full incident report →

Minor January 9, 2025 Issue with 3rd party connector for Microsoft Azure Monitor 13h 30m

Started Jan 09, 2025, 11:00 PM UTC· resolved Jan 10, 2025, 12:30 PM UTC

  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.

Read the full incident report →