Invoca had 17 outages in the last 2 years totaling 119h 9m of downtime — averaging 0.7 incidents per month.
There were 17 Invoca outages since September 3, 2025 totaling 119h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently working to resolve an issue affecting Smart Alerts. Customers subscribed to Smart Alerts may not be receiving the Smart Alert emails.
This issue has been resolved. Smart Alerts emails are now sending as expected.
June 2026 Invoca Availability Metrics Call Routing: 100% Web/API: 100%
We are currently investigating an issue affecting number swapping and call attribution across the Invoca platform. Customers may experience missing or delayed attribution data during this time. Our engineering teams are actively working to restore service.
Our engineering team has identified and resolved the underlying issue. Services have been restarted and number swapping and call attribution are being restored. We are actively monitoring to confirm full recovery
This incident has been resolved. The disruption was caused by a hardware failure on one of our servers, which temporarily took our Dynamic Number Insertion and call attribution services offline. Our engineering team replaced the affected hardware, restored services, and confirmed full recovery Impact Window: 5:50AM - 6:37AM PDT
Invoca is currently experiencing a delay in Signal file processing (both manual and automated file imports) beginning July 8, 2026 at 10:30 AM PT, with normal service expected to resume between 3:00–6:00 PM PT today. All files submitted during this window are queued and will process automatically with no action required. All other Signal-related services are operating normally.
Signal file processing has now been resumed and we are monitoring to ensure all queued files are processed as expected.
We are continuing to monitor for any further issues.
Signal uploads are processing successfully.
We are currently investigating an issue impacting access to EU Reports & Dashboards, as well as associated Webhooks. Users trying to view or generate reports in the EU region may experience slow loading times, timeouts, or error messages. Additionally, webhook deliveries related to reporting events are currently delayed or failing. Our engineering team is actively diagnosing the root cause. We apologize for the disruption and will provide our next update as soon as more information becomes available or within the next 30 minutes.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring results.
The incident has been resolved. Reports, dashboards and webhooks are firing as expected.
From 8:05 AM to 8:25 AM PT, users may have encountered latency or timeouts when accessing the Invoca UI and running reports. Our team identified and resolved the issue, and all systems have been fully operational since 8:25 AM PT.
We are aware of an ongoing AWS US-East-1 region outage. Our team is actively monitoring the situation. At this time, all Invoca services are fully operational and unaffected. We will continue to monitor and provide updates as the situation evolves.
AWS has not yet fully recovered from the ongoing US-East-1 outage. All Invoca services remain fully operational and unaffected. We are continuing to monitor the situation closely and will provide further updates as AWS works toward full recovery.
We're continuing to monitor the AWS incident until resolved, but our systems continue to remain completely functional. We will update as necessary
The regional AWS outage has been resolved. Invoca services were unaffected during this event and remained fully operational. We have successfully resumed standard traffic routing in the region.
We are currently investigating an issue impacting a large portion of inbound calls, which began at approximately 11:08 AM PST. The root cause has been identified, and our engineering team is actively implementing a fix. We will provide further updates as they become available.
This issue was mitigated at 11:41 am PST. Calls are routing as expected and our engineering team continues to monitor.
We are currently investigating reports of increased latency when accessing the Invoca platform. Please note that call processing and core platform features remain unaffected. We are working to resolve the slowdown and will provide an update as soon as more information is available.
Invoca.net is now loading normally. We continue to investigate the underlying issue and monitor the platform loading times. Call processing and core platform features remain unaffected.
Platform latency issue has been resolved.
We are currently investigating an issue that is preventing some users from accessing the Invoca Customer Support Portal. Our team is working to restore full access as quickly as possible. How to get help: Please send any technical requests or urgent issues to [email protected]
The Invoca Support Portal is now fully accessible.
We have identified an issue specifically affecting pre-transfer webhooks. Our engineering team is currently working to restore normal service. We will provide another update as soon as more information is available.
We have identified and reverted the changes that impacted our webhook services. All systems are fully operational as of 2:02 PM PST. Additionally, during investigation we uncovered that post-call webhooks were impacted for Google and Bing integrations, which service has also been restored for. While services are live, users may notice a delay in reporting for pre-transfer webhooks. We are currently processing a backlog of data and expect reporting to return to real-time shortly
Services continue operate as expected and our reporting backlog has cleared.
We are currently investigating intermittent user access to the Invoca UI based on the specific Invoca URL(www2.invoca.net) users are attempting to log in from. If you experience issues accessing the Invoca UI, please redirect and attempt to log in to Invoca.net. If you continue to experience access issues on Invoca.net, please notify our support team to further investigate.
While we continue to investigate and work towards a permanent solution specific to the www2.invoca.net Invoca URL, we have verified all users can successfully access and log into the Invoca UI through the workaround by going to Invoca.net. We will continue to provide updates as they become available.
We have successfully resolved the access issues impacting the www2.invoca.net URL. Users can now log in through their preferred access points without redirection. If you continue to experience any difficulties, please reach out to our support team.
We are currently investigating an issue that is preventing some users from accessing the Invoca Customer Support Portal. Our team is working to restore full access as quickly as possible. How to get help: Please send any technical requests or urgent issues to [email protected].
A fix has been implemented and we are monitoring results. Please resume accessing the Case Portal.
We are continuing to monitor for any further issues.
This incident has been resolved.
We have identified call connection failures specific to Toll Free destination lines owned by AT&T. At this time we have determined this to not be an Invoca specific issue and more broadly an AT&T issue. We have opened tickets with our downstream providers for awareness and are continuing to monitor the issue. Caller experience is long delays followed by a "number not in service" or "busy" message.
We are continuing to monitor the issue as we have not seen a reduction in the failure rate to Toll Free destination lines owned by this carrier and will continue to provide updates as more information becomes available.
We have observed normal call behavior to all Toll-Free destination lines for the past hour, and all services have returned to full stability. We are marking this incident as closed.
Invoca is aware of the ongoing issues with AWS and are monitoring closely. At this time, calls are performing as expected, although you may be experiencing some call connection issues with your call center/destinations line providers if they rely on AWS. Current Invoca Services Impacted * Training and labeling through Signal AI Studio * Sentiment analysis * Signal AI Processing * SMS 2FA codes failing to send for Platform Access * Reporting Delays
We are continuing to investigate this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
We are starting to see some of the impacted services restored while a few are still degraded but improving. We are continuing to monitor until the remaining services are fully restored and backlog is cleared. Services Impacted and Current State. * Training and labeling through Signal AI Studio * Degraded but improving * Sentiment analysis * Operational, processing backlog * Signal AI Processing * Operational * SMS 2FA codes failing to send for Platform Access * Degraded * Reporting Delays * Operational
All core services have been fully restored and operational. We are still experiencing an issue affecting SMS 2FA codes needed to access the Invoca platform. Our team is continuing to investigate and working toward a full resolution for the 2FA issue. Services Impacted and Current State. * Training and labeling through Signal AI Studio * Operational * Sentiment analysis * Operational * Signal AI Processing * Operational * SMS 2FA codes failing to send for Platform Access * Degraded * Reporting Delays * Operational
SMS 2FA codes to access the Invoca UI are now sending again and fully operational. We will continue to monitor through the evening to ensure stability on all previously impacted services.
All previously impacted services have remained stable. The incident is now officially resolved and closed.
We experienced a temporary issue with the Google Campaign Manager integration that has resulted in a delay in conversion reporting of up to 24 hours. The integration was paused as a precautionary measure, but we are currently re-queuing all calls and re-firing them to Google
The issue with the Google Campaign Manager integration is now fully resolved and reporting is fully caught up.
Yesterday, October 8th, 2025, from 14:15PT - 18:40PT, we experienced authentication errors with our transcription summary provider, which impacted summaries being processed and posted. For customers who access summaries through the Invoca UI, you can have the summary reran for each call/summary selected during the window. For users accessing summaries via the API, the team is further reviewing what options may be available.