hotato
GitHub

VFA-2025-0001

After switching to neural voice-activity detection, the system takes an unusually long time to respond when the caller gives a short one-word reply.

open2 independent reportslast reported 2026-04-27seen on livekit, ultravox

What this is

Filed as Endpointing latency short reply, the name every report of this mode is collected under.

A failure mode is one named thing that goes wrong on a live call. This record carries every public report of it the atlas has found, in each reporter's own words, and a status that moves only when a re-check stores the artifact behind the move. Status open: reported and still open where it was reported.

Evidence

Every independent public report of this mode, newest first: who wrote it, where, when, what they said, and the link back to the post it came from.

  1. Sanchit_Singhon community.livekit.io2026-04-27livekit
    i’m seeing high eou delay and high turn detection inference i’m using multilingual turn detection model which claims 50-160 ms inference time but in my case it’s around 700-1 sec...

    https://community.livekit.io/t/high-turn-detection-latency-issue/958

    first seen 2026-04-27 · fetched 2026-07-25T18:25:37Z · body sha256 ba1655a942c9474b

  2. rojithaDevon GitHub issues2025-03-30ultravox
    Slow responses with short one word replies

    https://github.com/fixie-ai/ultravox/issues/290

    first seen 2025-03-30 · fetched 2026-07-25T17:50:37Z · body sha256 c7399707deeb5c2f

Each quote is at most 30 words around the reported failure and links to the post it came from. If you wrote one of these and want it off this page, the removal path takes it down within 24 hours.

Hit this one yourself? Add your call to this entry: the stack, the versions, and what the caller heard. It lands as another independent report on this page, with your handle and a link back to what you wrote.

Report another occurrence

The form is a GitHub issue on the hotato repo. Prefer email? [email protected] reaches a person either way.

What is measurable

Evidence tier: Tier 3 · single mixed channel: one mixed channel still measures what silence shows, and each finding carries its measured confidence.

What it establishes

  • The seconds of silence between the caller finishing and the agent answering, timestamped in the call.
  • Dead air is visible in a single mixed channel, so this one is measurable on a mono recording as well as a split one.

What your trace settles

  • Your latency spans for that turn name where the seconds went: transcription, the model, or speech synthesis.
bash
# The silence between the caller finishing and the agent responding. Printed as DEAD...
hotato autopsy ./call.wav

A shipped hotato subcommand maps to this mode, as detector kind long_response_gap. The silence between the caller finishing and the agent responding. Printed as DEAD AIR at 5 seconds or more, and as LATENCY SPIKE between 2 and 5 seconds. hotato is MIT and runs locally. getting started.

Status history

A daily re-check reads every source thread on this page. The status moves when that re-check stores the link, the quote and the date behind the move, so every state on this record is one you can open.

The record has carried one status since it opened: open, reported and still open where it was reported. A move lands here with the link, the quote and the date that show it.

Discussion

Reader discussion of this mode: what fixed it, what did not, and what the record here is missing. It is a conversation, not part of the evidence above. The reports on this page are attributed and linked to their sources, and a comment is a comment.

Open this discussion on GitHub

The record

Atlas id
VFA-2025-0001
Mode id
pat_d636db67e9409ac2a305794a
Content digest
sha256:d636db67e9409ac2a305794a46dc902bbec8407be69c7f247f693f878da6b4c5
First reported
2025-03-30
Last reported
2026-04-27
First seen by the atlas
2025-03-30T23:59:45Z
Last re-checked
2026-04-27T16:18:49.899Z
Reported on
livekitultravox
Sources
GitHub issues, community.livekit.io
Scope
2 independent public reports across 2 sources. This entry states where the mode has been reported; where else it can occur is what the next report settles.

References

Every link this entry stands on: the post behind each report, and the artifact behind each status move.

  1. reporthttps://community.livekit.io/t/high-turn-detection-latency-issue/958 · Sanchit_Singh · community.livekit.io · 2026-04-27
  2. reporthttps://github.com/fixie-ai/ultravox/issues/290 · rojithaDev · GitHub issues · 2025-03-30

Machine surfaces

This entry, for an agent:feed.jsonfeed.atomfeed.schema.jsonatlas.llms.txt

Removal

If you wrote something quoted on this page and want it gone, one email does it. The removal path takes the quote, the handle and the link off this page, out of the feeds and out of the llms.txt within 24 hours, and tombstones the id so the entry cannot quietly return at a new address.