# 19057: Server unavailable or busy

Log Type: APPLICATION

Log Level: ERROR

## Description

This error indicates Twilio's API endpoint was temporarily unavailable or too busy to process the request. It commonly corresponds to transient server-side conditions such as HTTP `503 Service unavailable` or an internal `500 Server error`.

### Possible causes

* A transient outage or degradation causing Twilio to return HTTP `503 Service unavailable` for your API request.
* An internal Twilio error resulting in an HTTP `500 Server error`.

### Possible solutions

* Retry the request with exponential backoff. Transient server or connectivity issues often resolve on subsequent attempts.
* If you expect spikes or sustained high usage, slow down request rates and monitor for ongoing incidents. We recommend adjusting traffic and following status guidance.
* Capture and log the `Twilio-Request-Id` response header for each attempt. Include it when contacting Support to expedite investigation.
* Optionally specify a Twilio Edge Location for API requests to keep ingress close to your infrastructure, which can improve resilience and latency.

#### Additional resources

* [Twilio API responses](/docs/usage/twilios-response)
* [API best practices](/docs/usage/rest-api-best-practices)
* [Edge Locations](/docs/global-infrastructure/edge-locations)