Singlewire Software Outage History

Singlewire Software is up right now

Pingoru has recorded 52 incidents for Singlewire Software: 27 in the last 12 months and 5 in the last 90 days.

Source: status.singlewire.com

52incidents recorded
27last 12 months
5last 90 days
7 hourstypical duration
Incidents per month
036AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Singlewire Software in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202610 of 720 (0%)
May 202656 of 744 (1%)
June 202631 of 720 (0%)
July 2026211 of 744 (1%)
August 2026125 of 744 (3%)
September 202611 of 720 (0%)
October 2026346 of 744 (6%)
November 202600 of 26 (0%)

Incidents, newest first

Minor October 15, 2026 Emergency Calling Integration Errors 24m Emergency Calling

Started Oct 15, 2026, 02:59 PM UTC· resolved Oct 15, 2026, 03:23 PM UTC

  1. investigating Oct 15, 2026, 02:59 PM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. resolved Oct 15, 2026, 03:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 9, 2026 Emergency Calling Integration Errors 5h 52m Emergency Calling

Started Oct 09, 2026, 10:54 PM UTC· resolved Oct 10, 2026, 04:46 AM UTC

  1. investigating Oct 09, 2026, 10:54 PM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. resolved Oct 10, 2026, 04:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 5, 2026 iOS Tracking Events Fail to Start 1d 15h InformaCast for iOS

Started Oct 05, 2026, 10:26 PM UTC· resolved Oct 07, 2026, 01:43 PM UTC

  1. identified Oct 05, 2026, 10:26 PM UTC

    iOS users who start a Mobile Panic Button or choose a response that turns on location tracking are not having their location shared, and responders will not see them on the tracking map. A root cause has been identified and we plan to deploy a fix as soon as possible. We apologize for the disruption in service.

  2. monitoring Oct 06, 2026, 06:37 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Oct 06, 2026, 06:37 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Oct 07, 2026, 01:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 1, 2026 Elevated Telephony Error Rates 1h 23m Phone Call Notifications, SMS Notifications

Started Sep 01, 2026, 05:11 PM UTC· resolved Sep 01, 2026, 06:34 PM UTC

  1. identified Sep 01, 2026, 05:11 PM UTC

    We have received reports from Twilio of elevated errors that may prevent InformaCast from sending SMS and phone calls. Consider sending through other channels (such as email) for critical notifications. For additional information, please visit: https://status.twilio.com/ We will update this incident when more information is made available.

  2. monitoring Sep 01, 2026, 06:12 PM UTC

    A fix has been implemented and telephony services are operating normally. We will continue to monitor for any further impact.

  3. resolved Sep 01, 2026, 06:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 13, 2026 Channel Delivery Slowdowns and Failures 1d Android Push Notifications, Emergency Calling, iOS Push Notifications, Singlewire IDP Authentication and 7 more

Started Aug 13, 2026, 08:47 PM UTC· resolved Aug 14, 2026, 09:41 PM UTC

  1. investigating Aug 13, 2026, 08:47 PM UTC

    We've detected slowdowns and potential failures in notification delivery across many channels. Those channels include: - SMS messages - Phone calls - Emails - Push notifications to mobile apps - All on-premises devices, including speakers This may also impact authentication and general platform access. Our engineers are working to understand the scope of the issue and find a fix. We'll provide an update when we know more.

  2. monitoring Aug 13, 2026, 10:07 PM UTC

    We've failed over on the impacted service, and we believe service should be restored at this point. We'll continue to monitor overnight and provide an update in the morning when we have more information about the root cause of the service disruption.

  3. monitoring Aug 14, 2026, 01:54 PM UTC

    We're continuing to monitor to ensure we've completely recovered, and we'll give another update before 2PM CDT.

  4. monitoring Aug 14, 2026, 06:40 PM UTC

    Service has been restored, and we believe we've addressed the root cause. However, because of the intermittent nature of the issue, we're going to continue to monitor for the rest of the business day.

  5. resolved Aug 14, 2026, 09:41 PM UTC

    This incident has been resolved.

  6. postmortem Aug 24, 2026, 05:07 PM UTC

    On August 13th, we observed a few isolated occurrences of queries to our in-memory data store timing out. While we don't have a definitive root cause for the issue, we have been able to simulate similar cases with high query volume in our testing environments, and are making the following remediations to both hopefully prevent this issue from occurring again as well as mitigate it in the event that it does. First, we'll be upgrading the instance class of the machines this database runs on, which uses a more modern AWS hypervisor and processor architecture. Additionally, we'll be bolstering certain commands with retry and circuit breaker logic, such that in the rare case that this does happen again, the command will be immediately retried to a point, while allowing the queries to be skipped entirely if the database is truly unavailable. Lastly, we'll be tweaking our slow query logs in order to ensure we keep an eye on performance of this resource so that we can continue to tune our queries and ensure they don't place an undue amount of stress on this database. We apologize for any inconvenience this may have caused.

Read the full incident report →

Minor July 30, 2026 Distribution Lists Editing Unavailable for Non-Administrator Users 6h 1m Rest API

Started Jul 30, 2026, 03:41 PM UTC· resolved Jul 30, 2026, 09:42 PM UTC

  1. investigating Jul 30, 2026, 03:41 PM UTC

    We are currently investigating this issue.

  2. identified Jul 30, 2026, 05:19 PM UTC

    Recent updates to the distribution lists page have made it such that the page cannot be accessed by non-administrator users who otherwise would have permission to access the page, such as users with the Notification Sender permissions set attached via a policy. If any updates are immediately required to distribution lists, e.g. to update membership to ensure accurate notification recipients, make those changes via an administrator instead. We've implemented a fix and intend to release it as soon as we can.

  3. monitoring Jul 30, 2026, 08:03 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 30, 2026, 09:42 PM UTC

    This incident has been resolved.

  5. postmortem Jul 31, 2026, 01:44 PM UTC

    **What Happened** On July 30, 2026, non-administrative users who should have access to edit distribution lists could not do that via the InformaCast web application. Access to update distribution lists through the API or by administrative users was not impacted. **Root Cause** We made changes to the distribution lists pages that were released on July 29, 2026. These changes were intended as a simple update to the form, but they introduced a request to retrieve information inaccessible to most non-administrator users, including those with the Notification Sender permissions set. **Resolution** We updated the form to correctly gate information intended for administrators, which in turn restored the ability for non-administrators to access the form. To safeguard against similar issues with our permissions in the future, we will be updating our automated testing to better cover non-administrator access throughout our application.

Read the full incident report →

Major July 23, 2026 Emergency Calling Integration Errors 4h 50m Emergency Calling

Started Jul 23, 2026, 03:23 PM UTC· resolved Jul 23, 2026, 08:13 PM UTC

  1. investigating Jul 23, 2026, 03:23 PM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. resolved Jul 23, 2026, 08:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 29, 2026 Visitor Aware Impacted 2h 17m Visitor Aware

Started Jun 29, 2026, 04:34 PM UTC· resolved Jun 29, 2026, 06:52 PM UTC

  1. investigating Jun 29, 2026, 04:34 PM UTC

    We are currently experiencing an outage on app.visitor-aware.com. Attempts to access Visitor Aware result in the messages "Internal Service Error" or "Service Unavailable." We are investigating the root cause and will update this incident as we learn more.

  2. monitoring Jun 29, 2026, 05:38 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 29, 2026, 06:52 PM UTC

    This incident has been resolved.

  4. postmortem Jul 01, 2026, 05:10 PM UTC

    **What happened** On June 29, 2026, users attempting to log in to the Visitor Access web portal experienced performance degradation and timeouts. The Check In Kiosk iOS app was not affected. **Root cause** The login permission cache was storing too much data in a single entry, which exceeded the maximum allowed request size and made the web portal effectively unavailable. **Resolution** We have increased the granularity of our caching, which resolves the issue and improves overall performance for permission-gated requests throughout the application.

Read the full incident report →

Notice June 17, 2026 Emergency Calling Integration Errors 20h 4m

Started Jun 17, 2026, 08:30 PM UTC· resolved Jun 18, 2026, 04:34 PM UTC

  1. investigating Jun 17, 2026, 08:30 PM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. resolved Jun 18, 2026, 04:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 4, 2026 Emergency Calling Integration Errors 43m Emergency Calling

Started Jun 04, 2026, 02:54 PM UTC· resolved Jun 04, 2026, 03:37 PM UTC

  1. investigating Jun 04, 2026, 02:54 PM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. resolved Jun 04, 2026, 03:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 29, 2026 SMS Verification 5h 7m SMS Notifications

Started May 29, 2026, 07:25 AM UTC· resolved May 29, 2026, 12:32 PM UTC

  1. investigating May 29, 2026, 07:25 AM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. resolved May 29, 2026, 12:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 28, 2026 Emergency Calling Integration Errors 41m Emergency Calling

Started May 28, 2026, 03:18 PM UTC· resolved May 28, 2026, 03:59 PM UTC

  1. investigating May 28, 2026, 03:18 PM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. resolved May 28, 2026, 03:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 26, 2026 Live Agent Chat degraded performance 1h 22m

Started May 26, 2026, 05:11 PM UTC· resolved May 26, 2026, 06:34 PM UTC

  1. investigating May 26, 2026, 05:11 PM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. investigating May 26, 2026, 06:34 PM UTC

    We are continuing to investigate this issue.

  3. resolved May 26, 2026, 06:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 8, 2026 SMS Message Delivery 3h 23m SMS Notifications

Started May 08, 2026, 10:10 AM UTC· resolved May 08, 2026, 01:34 PM UTC

  1. investigating May 08, 2026, 10:10 AM UTC

    We're investigating an intermittent issue with SMS message delivery

  2. resolved May 08, 2026, 01:34 PM UTC

    This incident has been resolved.

  3. postmortem May 08, 2026, 06:12 PM UTC

    Our monitoring system triggered an alert that indicated a potential service disruption to SMS delivery. After investigation, we confirmed that all systems were operating normally throughout this period. The alert was caused by overly aggressive monitor thresholds, not an actual service issue. We are tuning our alerting to reduce false positives.

Read the full incident report →

Notice May 7, 2026 Emergency Calling Integration Degraded 2h 32m Emergency Calling

Started May 07, 2026, 01:41 AM UTC· resolved May 07, 2026, 04:13 AM UTC

  1. identified May 07, 2026, 01:41 AM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. investigating May 07, 2026, 01:45 AM UTC

    We are currently investigating this issue.

  3. monitoring May 07, 2026, 01:50 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 07, 2026, 04:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 9, 2026 Emergency Calling Integration Errors 11m Emergency Calling

Started Apr 09, 2026, 04:22 PM UTC· resolved Apr 09, 2026, 04:33 PM UTC

  1. investigating Apr 09, 2026, 04:22 PM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. resolved Apr 09, 2026, 04:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 24, 2026 Emergency Calling Integration Errors 33m Emergency Calling

Started Mar 24, 2026, 07:22 PM UTC· resolved Mar 24, 2026, 07:55 PM UTC

  1. investigating Mar 24, 2026, 07:22 PM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. monitoring Mar 24, 2026, 07:36 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 24, 2026, 07:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 19, 2026 Emergency Calling Integration Errors 16m Emergency Calling

Started Mar 19, 2026, 03:36 AM UTC· resolved Mar 19, 2026, 03:52 AM UTC

  1. investigating Mar 19, 2026, 03:36 AM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. resolved Mar 19, 2026, 03:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 9, 2026 On-Premises Server events may be delayed 22h 25m

Started Mar 09, 2026, 03:41 PM UTC· resolved Mar 10, 2026, 02:07 PM UTC

  1. monitoring Mar 09, 2026, 03:41 PM UTC

    We're experiencing an issue where events from on-premises servers may be delayed from reaching the cloud. This may include events intended to broadcast notifications to the cloud, such as using a phone to activate a DialCast Dialing Configuration. This is also presently impacting notification progress and completion reporting, as well as display of IDNs. For now, to ensure notification delivery to cloud devices, activating notifications from the web application or other cloud devices is encouraged. We've implemented a fix, and we're monitoring the results.

  2. monitoring Mar 09, 2026, 06:39 PM UTC

    We are continuing to monitor. At this point, notifications sent from on-premises servers should be received by the cloud and distributed correctly. Events related to on-premises devices such as speakers and IDNs are still being processed; there may be some delay before changes to such devices are visible in the cloud.

  3. monitoring Mar 09, 2026, 08:24 PM UTC

    Device updates are still facing delays, but we are starting to see our event processor catch up. We'll continue to monitor this overnight and update this tomorrow, 3/10.

  4. resolved Mar 10, 2026, 02:07 PM UTC

    This incident has been resolved.

  5. postmortem Mar 10, 2026, 05:52 PM UTC

    On Friday night, we deployed a small infrastructure change that required a reboot of our database. During this reboot, we encountered a bug in our event processor code that caused events not to be processed until service reboot. To compound this, our monitoring platform had invalidated the alarm we had in place to monitor errors with our event processor. This caused us to remain unaware of the issue until Monday morning, where we promptly fixed it by rebooting the service containing the event processors. At that point, the platform needed to catch up by processing all the events that had been building up over the weekend, which completed on Monday night. We will be taking a multi-pronged approach to ensuring this doesn’t happen again: 1. We have fixed our event monitors, and will be testing them every release going forward to ensure they remain operational. We are also following up with our monitoring platform to ensure future monitoring will not be disrupted. 2. We are augmenting our event processing code in the following ways: 1. We have switched to a more robust event processing pattern that is not vulnerable to the bug that caused consumers to stop polling after a database reboot. 2. We have increased the processing throughput such that if this _were_ to happen again, our consumers would catch up much more quickly than they did during this incident. We apologize for service disruptions caused by this incident.

Read the full incident report →

Minor March 2, 2026 Emergency Calling Integration Errors 16h 41m Emergency Calling

Started Mar 02, 2026, 10:43 PM UTC· resolved Mar 03, 2026, 03:25 PM UTC

  1. investigating Mar 02, 2026, 10:43 PM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. investigating Mar 02, 2026, 10:45 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 02, 2026, 10:45 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Mar 02, 2026, 10:46 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. monitoring Mar 02, 2026, 11:22 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Mar 03, 2026, 03:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 26, 2026 Emergency Calling Integration Errors 48m Emergency Calling

Started Feb 26, 2026, 01:03 AM UTC· resolved Feb 26, 2026, 01:52 AM UTC

  1. investigating Feb 26, 2026, 01:03 AM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. resolved Feb 26, 2026, 01:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 25, 2026 Emergency Calling Integration Errors 19m Emergency Calling

Started Feb 25, 2026, 11:53 PM UTC· resolved Feb 26, 2026, 12:13 AM UTC

  1. investigating Feb 25, 2026, 11:53 PM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. monitoring Feb 25, 2026, 11:56 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 26, 2026, 12:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 19, 2026 Emergency Calling Integration Errors 1h 43m Emergency Calling

Started Feb 19, 2026, 10:37 PM UTC· resolved Feb 20, 2026, 12:20 AM UTC

  1. investigating Feb 19, 2026, 10:37 PM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. resolved Feb 20, 2026, 12:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 7, 2026 Emergency Calling Integration Errors 25m Emergency Calling

Started Feb 07, 2026, 07:05 AM UTC· resolved Feb 07, 2026, 07:30 AM UTC

  1. monitoring Feb 07, 2026, 07:05 AM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. resolved Feb 07, 2026, 07:30 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 5, 2026 Emergency Calling Integration Errors 17h 13m Emergency Calling

Started Jan 05, 2026, 08:31 PM UTC· resolved Jan 06, 2026, 01:45 PM UTC

  1. investigating Jan 05, 2026, 08:31 PM UTC

    We have received reports from RapidSOS of elevated errors that may prevent Emergency Calling from working with InformaCast. For additional information, please visit: https://status.rapidsos.com/ We will update this incident when more information is made available.

  2. monitoring Jan 05, 2026, 09:35 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 06, 2026, 01:45 PM UTC

    This incident has been resolved.

Read the full incident report →