# March 3, 2021

## Improved Error Reporting for Realtime Streaming

Deepgram has released a change to how we report errors during Realtime Streaming. Now, we will return a WebSocket Close frame and the body of the Close frame will indicate the reason for closing using one of the specification's [pre-defined status codes](https://tools.ietf.org/html/rfc6455#section-7.4.1) followed by a UTF-8-encoded payload that represents the reason for the error.

[Read about the error handling here.](/guides/self-hosted-deployments-2-reference-speech-to-text-listen-streaming#error-handling)

Deepgram support, [**support@deepgram.com**](mailto\:support@deepgram.com), is always available to help.

Read more about Deepgram’s Realtime Streaming capabilities in the [Deepgram Documentation](/guides/self-hosted-deployments-2-reference-speech-to-text-listen-streaming).

## Related pages

- [Amazon SageMaker](./amazon-sagemaker-index.md)
- [Aura](./aura-index.md)
- [Changelog](../changelog.md)
- [Custom Vocabulary](./custom-vocabulary-index.md)
- [Deepgram's Docs](../index.md)
- [Deployment](./deployment-index.md)
- [Docker/Podman](./docker-podman-index.md)
- [Features](./features-index.md)
- [Flux TTS](./flux-tts-index.md)
- [Formatting](./formatting-index.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.