Singlewire Software Outage History
Singlewire Software is up right nowPingoru has recorded 52 incidents for Singlewire Software: 27 in the last 12 months and 6 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 0 of 720 (0%) |
| May 2026 | 5 | 13 of 744 (2%) |
| June 2026 | 3 | 23 of 720 (3%) |
| July 2026 | 2 | 11 of 744 (1%) |
| August 2026 | 1 | 25 of 744 (3%) |
| September 2026 | 1 | 1 of 720 (0%) |
| October 2026 | 3 | 46 of 517 (9%) |
Incidents, newest first
Critical December 5, 2024 Conference Call Outage 15h 9m Conference Call
Started Dec 05, 2024, 11:20 PM UTC· resolved Dec 06, 2024, 02:30 PM UTC
- identified Dec 05, 2024, 11:20 PM UTC
We have identified an issue where creating a conference call PIN fails. We have identified a fix and should be deploying that fix shortly.
- monitoring Dec 05, 2024, 11:58 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 09, 2024, 02:30 PM UTC
This incident has been resolved.
Major December 4, 2024 Scheduled tasks (Scheduled notifications and Phone gathering jobs) outage 17h 56m Android Push Notifications, iOS Push Notifications, Email Notifications, Phone Call Notifications and 4 more
Started Dec 04, 2024, 08:36 PM UTC· resolved Dec 05, 2024, 02:33 PM UTC
- identified Dec 04, 2024, 08:36 PM UTC
Tasks set up to run on a schedule, namely Scheduled Notifications and Phone Gathering jobs, are non-functional at this time. We've identified the issue and are preparing a fix.
- monitoring Dec 04, 2024, 10:08 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 05, 2024, 02:33 PM UTC
This incident has been resolved.
Notice December 4, 2024 Visitor Aware Performance and Timeout Issue –
Started Dec 04, 2024, 05:30 PM UTC· resolved Dec 04, 2024, 05:30 PM UTC
- resolved Dec 06, 2024, 04:10 PM UTC
Singlewire has noticed a temporary downgraded performance due to backend query processes with law enforcement databases. This has since been resolved.
Notice November 27, 2024 Some Fusion servers reporting as disconnected 1h 27m
Started Nov 27, 2024, 08:03 PM UTC· resolved Nov 27, 2024, 09:30 PM UTC
- investigating Nov 27, 2024, 08:03 PM UTC
We have received reports of Fusion servers reporting as disconnected. We are investigating to determine the cause of the disconnected status and what, if any, impact this might have on notification reliability.
- identified Nov 27, 2024, 08:18 PM UTC
We have identified an issue with the service that reports on server state and are working to resolve it. Notification deliverability is not affected.
- monitoring Nov 27, 2024, 09:20 PM UTC
After restarting the affected service, we observe that affected servers are now reporting as being connected. We will continue to monitor for any abnormalities.
- resolved Nov 27, 2024, 09:30 PM UTC
After restarting the affected service, we observe that affected servers are now reporting as being connected. We will continue to work to identify the root cause and prevent similar future issues.
- postmortem Dec 20, 2024, 03:37 PM UTC
The service that determines Fusion server health uses a distributed data store to track the state of each Fusion server in a way that is meant to be resilient to loss of a single node in our system. This service was configured differently from other services in which we use the same technology, and in such a way that the system required data to match on every node in order to process it. As part of a normal system maintenance operation, we replaced several nodes in our system on November 27, including the ones holding this Fusion server health data. Because of this misconfiguration, the system temporarily stopped processing Fusion server health data. To solve the immediate problem, we restarted the service, which put it back into a good working state. We are also planning a longer-term fix correcting the configuration such that future losses of one node cannot result in the same problem occurring, either in this service or other future services using the same technology.