---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/33004#article
headline: "33004: Service is unavailable\t"
url: https://www.twilio.com/docs/api/errors/33004
inLanguage: en
dateModified: 2026-06-08T11:29:20.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 33004: Service is unavailable	

Log Type: TWILIO

Log Level: ERROR

## Description

Twilio returns this error when an IoT request reaches a service that is temporarily unavailable. This usually means the service itself, or a downstream dependency it relies on, could not process the request at that time.

### Possible causes

* The Twilio IoT service handling the request is experiencing a temporary outage or degraded performance.
* A downstream service that your request depends on is temporarily unavailable.
* An active incident or a scheduled maintenance window is affecting the service or region handling your request.

### Possible solutions

* Retry the request after a short delay. This error is temporary and may clear once the service recovers.
* If you retry automatically, use exponential backoff so you do not send a burst of repeated requests while the service is recovering.
* Check the Twilio status page to confirm whether there is an active incident, degraded service, or scheduled maintenance affecting the platform.
* Create an Alarm for this specific error code so you can detect repeated failures quickly.
* If the error continues after the status page shows normal service, capture the `Twilio-Request-Id` response header and contact Support.

#### Additional resources

* [API best practices](/docs/usage/rest-api-best-practices)
* [Alarms](/docs/usage/troubleshooting/alarms)
* [Checking Twilio Service and API Status with the Status Page](https://help.twilio.com/articles/360013353193-Checking-Twilio-Service-and-API-Status-with-the-Status-Page)