Singlewire Software had 16 outages in the last 2 years totaling 552h 57m of downtime — averaging 0.7 incidents per month.
There were 16 Singlewire Software outages since August 21, 2025 totaling 552h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
**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.
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 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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
**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.
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.
We are continuing to investigate this issue.
This incident has been resolved.
We're investigating an intermittent issue with SMS message delivery
This incident has been resolved.
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.
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.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Visitor Aware is currently down due to issues with our third party provider Cloudflare. They are working to get the issued resolved and we will keep you updated on their progress.
The issue has been identified and a fix is being implemented.
Cloudflare has implemented a fix. We will continue to post updates as we monitor their progress.
Cloudflare appears to resolved their issue but not yet given the all clear. We will continue to monitor their progress.
We are continuing to monitor Cloudflare as they make progress on their issue.
Cloudflare is continuing to make progress on their recovery.
We are still waiting to hear back from Cloudflare that they have resolved all issues. All indications are that everything is back to normal.
The Cloudflare issue has been resolved.
An increase of errors was detected starting shortly after 11:30am CDT. These failures were linked to the ongoing cloud provider outage.
Visitor Aware is currently experiencing extended processing times and inconsistent facial recognition matching due to the ongoing cloud provider outage. We are monitoring the situation and will update when we learn more.
We are monitoring the situation and will update when we learn more.
Our cloud provider is reporting that their service has recovered. While there may be some increased latency, we believe service should be back to normal soon. We'll continue to monitor for the next hour.
This incident has been resolved.
InformaCast Fusion is currently experiencing a service interruption due to a widespread incident reported by our cloud provider. At this time Fusion cannot send SMS messages, place phone calls, or send email. Our engineers are aware of the issue and are continuing to monitor the situation closely. We will update this incident when we learn more.
InformaCast Fusion is now able to send SMS messages and place calls reliably. Email send are succeeding, but inconsistent delivery times are noted. We will update this incident when we learn more.
All Fusion notification channels are responding normally. We will continue to monitor the situation for next hour to ensure there are no lingering issues.
All InformaCast Fusion functionality has been restored and returned to normal.
Visitor Aware is currently experiencing an issue with badges not being automatically printed through the Desktop Print Helper app. This impacts version 2.1.3 of Print Helper and 12.2.6 of the web portal. The team is investigating the issue.
With the release of version 12.2.6 last night, an update to the format of our visitor and student badges caused an error with current and previous Desktop Print Helper Versions (2.1.3 and previous). This resulted in certain dashboard updates to fail, and caused badges to not print automatically when using Desktop Print Helper to process print jobs. This change has been reverted so that Desktop Print Helper continues to work with version 12.2.6. To address this, we will update the badge formatting fix so that it is compatible with previous Desktop Print Helper versions.
This incident has been resolved.
We have identified an issue where some android devices are not receiving push notifications as a recipient of notifications in InformaCast Fusion. The issue is currently still under investigation.
We have swapped out a copy of one of our services, as we believe the issue is transient at this time. Both monitoring and root cause analysis are ongoing. We will resolve the incident when we are confident that Android pushes are no longer failing.
This incident has been resolved.
During our investigation of this issue, we discovered a programming error with our message delivery code, that, in certain instances, caused it to stall indefinitely. We have isolated the issue and are deploying a fix to prevent it from happening again. We apologize for service disruptions caused by this incident.
Users attempting to use the Microsoft Teams integration with InformaCast to send scenarios may experience a problem where dropdowns display options from previous questions in the sending workflow rather than the current question. This prevents the user from selecting a valid response and sending the scenario. We've investigated and currently believe this to be an issue within recent versions of Microsoft Teams clients, not an error within our integration. We'll continue to monitor and investigate, and we'll update here when we have more information.
Our engineers are in correspondence with Microsoft support about this issue. At this time, scenario sending from Microsoft Teams clients is still impacted. We'll update when we know more.
Microsoft has confirmed the unexpected behavior while sending scenarios from their Teams clients is a defect within their system. Because the issue is external to us, we don't have a timeline for this issue to be resolved. Please refer to this Singlewire Knowledge Base article for the most up-to-date status on this issue: https://support.singlewire.com/s/article/Unable-to-send-scenario-from-Microsoft-Teams-because-scenario-question-displays-incorrect-options