Invoca had 25 outages in the last 2 years totaling 315h 43m of downtime — averaging 1 incident per month.
There were 25 Invoca outages since June 4, 2024 totaling 315h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
April 2026 Invoca Availability Metrics Call Routing: 99.92% Web/API: 99.89%
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.
Google is having some minor issues related to the Google Ads and SA360 integrations. Impact at this time is delays in reported conversions. We are continuing to monitor the issue with Google.
Google is having some minor issues related to the Google Ads and SA360 integrations. Impact at this time is delays in reported conversions. We are continuing to monitor the issue with Google.
Error responses related to GoogleAds and Google SA360 have subsided, in addition to Google marking the issue resolved on their status page. We will continue to monitor through the evening and into the morning to ensure we continue to see services operating as expected.
Error responses related to GoogleAds and Google SA360 have subsided, in addition to Google marking the issue resolved on their status page. We will continue to monitor through the evening and into the morning to ensure we continue to see services operating as expected.
Google Ads and SA360 continue to operate as expected.
Due to an ongoing outage with GCP, we are seeing delays in transcription(signal, sentiment, summary) as well as a small amount of failures on new and in progress calls. We are continuing to monitor until delays are caught up and GCP has notified all services are restored.
Due to an ongoing outage with GCP, we are seeing delays in transcription(signal, summary) as well as a small amount of failures on new and in progress calls. We are continuing to monitor until delays are caught up and GCP has notified all services are restored.
We are now caught up on all transcription delays and all new calls are processing as expected. We are continuing to monitor.
We are now caught up on all transcription delays and all new calls are processing as expected. GCP has also confirmed all services are fully restored on their end.
Today(2025-04-21) from 2:56 to 3:46 PM PT, realtime routing and pre-transfer webhooks were delayed and or failed. This has since been resolved by rolling back a recent deploy. If you have any questions regarding this incident, please go to our support portal and submit a support ticket.
We have identified an issue where some callers that are calling Invoca Toll Free numbers are not able to successfully make a keypress when prompted within the Invoca IVR, resulting in some callers not being able to navigate through the IVR to connect to destination lines. We are actively engaged with our carrier to resolve the issue
We have resolved the issue with our upstream provider and keypresses are now successfully being recognized within the Invoca IVR and processing through to destination lines.
We have resolved the issue with our upstream provider and keypresses are now successfully being recognized within the Invoca IVR and processing through to destination lines.
Invoca deployed an update on Friday 2025-03-14 at 12.54 PM MT that inadvertently impacted dynamic number insertion on some customer websites via the Invoca Tag. This incident was identified and resolved as of today 2025-03-15 at 6:15 PM MT. Calls to static phone numbers or calls already in progress would not have been impacted by this incident. If you have any questions or continue to experience any issues with dynamic number insertion, please reach out to our support team for further review.
Currently, customers may experience some delays in reporting and call corrections in the Invoca UI.
Transaction API issues are resolved and reporting delays are currently catching up. We are currently monitoring until full caught up
Transaction API and Reporting delays are fully resolved and restored.
Transaction API and Reporting delays are fully resolved and restored.
We recently experienced some intermittent failures with access to the Invoca.net Homepage as well as API calls on the US Platform. This has since been mitigated and we are further investigating the root of the issue. The window of impact for the incident was 7:10 to 7:20 AM PT.
Update: Upon further investigation of the intermittent homepage and API call failures, we have identified the root of the issue relating to a substantial increase in number swapping request via API. We have since mitigated the issue with reducing thresholds and are working through 2 longer term solutions. Impact during this 10 minute window(7;10-7:20 AM PST) was intermittent access failures to the Invoca.net website and failure in automatically creating new ringpools.
We are currently investigating an issue with users' ability to access our EU platform's UI. Our US platform is not impacted.
This incident has been resolved.
We have identified an issue with Google's ability to successfully connect calls to Invoca over SIP. This primarily impacts Google Call Extension calls from connecting to Invoca tracking numbers. Google has identified the root cause and is working to resolve the issue. In the meantime, we are purposefully adjusting our routing methodology for all Google SIP calls to route over PSTN. This will ensure that calls made directly from Google ads continue to connect but will result in a loss of attribution data for any Google Call Extension calls.
To not disrupt any currently connected calls, we have elected to not swap Google SIP calls to route over to PSTN at this time. Currently, all calls routing over Google SIP are failing to connect to their destination.
Continued impact of ~40% of all Google Inbound GCE Calls not connecting. Google has stated a fix is being implemented shortly, but no specific ETA at the moment.
Google is continuing to resolve the issue. There have been recent improvements in successfully connecting Google Call Extension calls to their destinations, with 77% of their calls connecting over the last hour.
We have seen no call failures since 9:24pm ET. We will continue to monitor this issue into tomorrow.
This incident has been resolved.
We are currently investigating an issue whereby a small number of calls in progress to the platform were being disconnected while in flight.
We continue to investigate this issue. We have not experienced any additional drop in calls but are still investigating the root cause for those that were dropped in flight.
Our teams continue to investigate areas of our network and our providers to identify the root cause of in-flight calls dropping.
The incident is now mitigated and the teams are in monitoring status as we have seen stability in our network and providers for the last ~20 hours. We have seen no additional instances of dropped calls in this time. We are continuing to engage both our cloud and telecom provider for better monitoring and ability to avoid network connectivity issues going forward.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are experiencing intermittent delays in obtaining Enhanced Caller Profile data from our provider. As a result, ECP data is not populating in our User Interface and Reporting for a subset of our calls.
We are continuing to work with our partner to investigate this issue.
The investigation is still ongoing. We are continuing to work with our partner to understand the root cause.
We have identified that we have been successfully capturing and storing ECP data even though the response times from our provider have been delayed. The current impact of this ongoing issue is that ECP data is not ready in time for pre-transfer webhooks or if used in real-time routing scenarios.
We are continuing to experience high latency in receiving responses from our provider's endpoint. They are making progress toward a resolution.
Our provider has stated that they have mitigated the latency issue. We are monitoring the response times on our end to ensure that they meet our normal standards.
Response times from our provider's endpoint are aligned with our normal standards. The incident is now resolved.