---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/31930#article
headline: "31930: Stream - Media - Buffer Overflow"
url: https://www.twilio.com/docs/api/errors/31930
inLanguage: en
dateModified: 2026-04-29T19:18:40.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 31930: Stream - Media - Buffer Overflow

Log Type: APPLICATION

Log Level: WARNING

## Description

Twilio raises this warning when a Media Stream is sending call audio to your WebSocket server and the WebSocket upstream becomes congested. When restricted bandwidth prevents the stream from keeping up, Twilio discards audio.

### Possible causes

* Your server or network path has an upstream bandwidth restriction that causes congestion while Twilio is streaming audio over WebSockets.
* Your Media Streams application cannot reliably accept the real-time audio that Twilio sends to your WebSocket server.
* Network controls between Twilio and your WebSocket server are not fully configured for secure WebSocket traffic on port 443.

### Possible solutions

* Verify network load and available upstream bandwidth on the server that handles the Media Stream.
* Confirm that your WebSocket endpoint can accept secure WebSocket connections from Twilio on port 443 from any public IP address.
* Review how your application handles incoming Media Streams messages so it can continue receiving Twilio's real-time audio.
* Validate the `X-Twilio-Signature` header on your Media Streams endpoint while you troubleshoot connectivity and network configuration.

#### Additional resources

* [Media Streams Overview](/docs/voice/media-streams)
* [Media Streams WebSocket Messages](/docs/voice/media-streams/websocket-messages)
* [Media Streams Configuration](/docs/global-infrastructure/firewall-configurations/media-streams-configuration)