I’m encountering what appears to be an inconsistency between my LiveKit Cloud project’s displayed STT quota and the quota enforced by the LiveKit Inference gateway.
My Quota and Limits dashboard shows:
- Model: Deepgram Nova-3 (Monolingual)
- Type: STT
- Limit: 5 concurrent connections
- Peak usage (past 7 days): 1/5
However, attempts to establish a LiveKit Inference STT connection are currently rejected with HTTP 429.
I captured the JSON error returned by the STT WebSocket upgrade:
type: inference_quota_exceeded
error: STT connection limit exceeded
category: MaxConcurrentGatewaySTT
remaining_limit: 0
current_usage: 0
status: QuotaStatusExceeded
The important inconsistency is that the gateway reports current_usage: 0 and remaining_limit: 0, while the project dashboard shows an STT concurrency limit of 5.
The integration was previously working. My September billing/usage page currently shows 216 minutes of Deepgram Nova-3 STT usage, so the model has successfully been used by this project before.
I have verified the client/agent audio path independently: the microphone track reaches the LiveKit agent, RTP packets are received, decoded PCM audio reaches the agent’s STT pipeline, and the failure occurs specifically when the LiveKit Inference STT WebSocket connection is established.
Could someone from LiveKit please check whether the effective MaxConcurrentGatewaySTT quota for this project is incorrectly set to zero or whether another account/project-level restriction is causing the gateway to return this quota error?
I can provide the affected project ID and gateway session ID privately if needed.
Thank you.
