Avoca logo

Is Avoca Down?

AI & Machine LearningLive status, outages, and incident history

No. Avoca is up right now.

Every monitored Avoca system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 7m agoLive · every 60s

Know the moment Avoca breaks

Avoca is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Avoca status page
How we know: the official Avoca status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Avoca Status Summary

As of 15:13 UTC on 14 November 2026, Avoca is operational. PulsAPI checked Avoca's official status page and found 8 of 8 components operational, with no active incidents. The latest incident, "Bookings delayed, in-call data loading failures", was on Oct 30, 2026 and lasted 2h 19m.

Cite as: PulsAPI, “Avoca status”, checked 14 November 2026, 15:13 UTC. https://www.pulsapi.com/services/avoca

Avoca Component Status

The main Avoca systems on this page. All 8 are operational right now.

8operational
Analytics
Operational
Calls
Operational
Dashboard
Operational

5 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Inbound, Live Chat, Outbound, Simple Scheduler, SMS.

See all of them free

Component statuses may change independently during partial outages.

Recent Avoca Outages & Incidents

Incident history from the official Avoca status page, including resolution updates.

Bookings delayed, in-call data loading failuresResolved Oct 30, 2026 · 2h 19mResolved

New calls are now processing normally. We have reprocessed calls from between 3:55pm ET/12:55pm PT and 4:28pm ET/1:28pm PT. We have discovered some errors when assistants tried to access external information as well. --- [2026-10-30T21:52:23Z] (monitoring) New call are now processing normally. We have reprocessed calls from between 3:55pm ET/12:55pm PT and 4:28pm ET/1:28pm PT. We have discovered some errors when assistants tried to access external information as well. --- [2026-10-30T20:48:26Z] (identified) New bookings are now processing normally. We are now reprocessing calls from between 3:55pm ET/12:55pm PT and 4:28pm ET/1:28pm PT. We have discovered some errors when assistants tried to access external information during this incident as well. --- [2026-10-30T20:35:41Z] (identified) New bookings are now processing normally. We are now reprocessing calls from between 3:55pm ET/12:55pm PT and 4:28pm ET/1:28pm PT. In-call experience is not affected. --- [2026-10-30T20:27:19Z] (investigating) Some bookings are delayed. Incident began approximately 3:55pm ET/12:55pm PT. In-call experience is not affected.

Delay in inbound bookingsResolved Oct 15, 2026 · 18 minResolved

Inbound bookings are now completing with normal latency --- [2026-10-15T22:47:12Z] (monitoring) We have identified the cause of the delay in bookings. We expect the delay to resolve shortly and are monitoring. --- [2026-10-15T22:39:29Z] (investigating) We are investigating a delay in inbound bookings

Voice orchestrator latencyResolved Oct 13, 2026 · 3h 21mResolved

Voice orchestrator latency has returned to normal levels --- [2026-10-13T15:05:09Z] (monitoring) We believe this issue is resolved and are no longer routing calls away from the voice orchestrator. We continue to monitor. --- [2026-10-13T14:49:59Z] (identified) We have failed away from one orchestrator due to high latency while receiving calls. This may impact voice quality. --- [2026-10-13T14:49:13Z] (identified) We have failed away from one orchestrator due to high latency while receiving calls. This may impact voice quality, especially Tucker. --- [2026-10-13T14:45:07Z] (identified) We have failed away from one orchestrator due to high latency while receiving calls. This may impact voice quality.

Avoca Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Avoca incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Avoca Outage Reports

Problems reported by engineers using Avoca. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Avoca problems reported yet.

Something wrong with Avoca on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Avoca

Avoca's status page at status.avoca.ai lists 8 components, such as Analytics, Calls and Dashboard. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Avoca's side or yours.

Avoca Status FAQ

Is Avoca down right now?

The verdict at the top of this page comes from the latest poll of the official Avoca status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Avoca is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Avoca recovers.

How do I check Avoca uptime history?

PulsAPI tracks Avoca uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Avoca changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Avoca outages?

PulsAPI reads the official Avoca status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Avoca components?

Yes. PulsAPI monitors 8 individual Avoca components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Avoca goes down?

Yes. Create a free account and subscribe to Avoca: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Avoca to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Avoca problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Avoca?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Avoca plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Avoca with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services