Is Singlewire Software down?

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.

This incident has been resolved.

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.

This incident has been resolved.

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.

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

We are continuing to monitor for any further issues.

This incident has been resolved.

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.

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

This incident has been resolved.

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.

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.

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

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.

This incident has been resolved.

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.