Snapshot 25385
Normalized text
Scripts and page chrome removed; this is what change detection compares.
All systems operational Refreshed Mobile Alerting. Anywhere Incident Response. API: Mail SMTP Outages (1) Uptime 490 days 9 hours 18 minutes 18 seconds Operational Outages Started: May 28, 2025 | 12:07 GMT+02:00 Ended: May 28, 2025 | 14:04 GMT+02:00 Length: 1 hour 57 minutes 27 seconds Maintenance API: Webhook Outages (2) Uptime 1959 days 5 hours 24 minutes 14 seconds Operational Outages Started: May 20, 2021 | 17:53 GMT+02:00 Ended: May 20, 2021 | 17:58 GMT+02:00 Length: 4 minutes 54 seconds Started: May 20, 2021 | 08:51 GMT+02:00 Ended: May 20, 2021 | 08:56 GMT+02:00 Length: 4 minutes 52 seconds Maintenance Web Portal Outages (2) Uptime 1959 days 14 hours 26 minutes 11 seconds Operational Outages Started: May 20, 2021 | 08:51 GMT+02:00 Ended: May 20, 2021 | 08:56 GMT+02:00 Length: 5 minutes 9 seconds Started: Apr 01, 2021 | 23:47 GMT+02:00 Ended: Apr 01, 2021 | 23:56 GMT+02:00 Length: 8 minutes 37 seconds Maintenance Incidents Connector applications issue Resolved | Dec 02, 2025 | 16:29 GMT+01:00 No further problems were noticed, and all connectors are functioning normally again. +Show history Monitoring | Dec 02, 2025 | 12:08 GMT+01:00 We are observing recovery in the affected third-party connectors and will continue to closely monitor the application. Resolution in progress | Dec 02, 2025 | 10:01 GMT+01:00 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. Investigating | Dec 01, 2025 | 16:31 GMT+01:00 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. Phone calls / call routing impaired Resolved | Nov 11, 2025 | 09:05 GMT+01:00 The issue affecting phone calls to call routing numbers in the +4915888 range has been resolved by the telephony infrastructure provider. +Show history Monitoring | Nov 10, 2025 | 17:57 GMT+01:00 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. Investigating | Nov 10, 2025 | 12:13 GMT+01:00 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. Voice and Text delivery impaired Resolved | Oct 21, 2025 | 10:30 GMT+02:00 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. +Show history Monitoring | Oct 20, 2025 | 15:20 GMT+02:00 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. Open | Oct 20, 2025 | 12:14 GMT+02:00 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. Email delivery impaired Resolved | May 30, 2025 | 12:19 GMT+02:00 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. Account Portal Issues Resolved | Mar 31, 2025 | 09:06 GMT+02:00 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. Issue with 3rd party connector for Microsoft Azure Monitor Resolved | Jan 10, 2025 | 13:30 GMT+01:00 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. +Show history Resolution in progress | Jan 10, 2025 | 00:00 GMT+01:00 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. Web portal/account portal login Resolved | Sep 20, 2024 | 11:01 GMT+02:00 Users experienced errors when logging into the web/account portal. We have identified the issue and have deployed a solution. We are currently monitoring the results. Connector applications in error status Resolved | Aug 29, 2024 | 11:00 GMT+02:00 The team was able to resolve the underlaying issue, all connector applications are healthy again. +Show history Investigating | Aug 29, 2024 | 10:13 GMT+02:00 We are currently investigating an issue with certain connector applications. Affected connectors have entered an error status and are currently unhealthy. You may also receive emails from SIGNL4 with health warnings for your connector. The issue does not affect all customers. Status Page powered by Admin Labs Subscribe to updates Get email notifications about status page updates. Thanks for subscribing. Something went wrong with your email address, please try again.