---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/51108#article
headline: "51108: Twilsock: Service instance disabled"
url: https://www.twilio.com/docs/api/errors/51108
inLanguage: en
dateModified: 2026-06-09T11:00:42.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 51108: Twilsock: Service instance disabled

Log Level: ERROR

## Description

Twilsock could not connect because the Service instance you requested is disabled. This usually means the SID or configuration your client is using points to a Service instance that is no longer active for the Twilio product you are trying to reach.

### Possible causes

* The client is configured with a disabled Service instance SID.
* The Service instance was disabled in Console or through an API update.
* Your application is using an outdated configuration value from a previous environment, such as development or staging.
* The access token or client configuration points to a different Service instance than the one you intended to use.

### Possible solutions

* Confirm that your application is using the correct Service instance SID for the environment you want to access.
* Check the status of the Service instance in Twilio Console and make sure it is active.
* If the Service instance was intentionally disabled, update your application to use an active Service instance instead.
* Review your deployment configuration and token generation flow to make sure they reference the correct Twilio Service instance.
* If you no longer need the disabled Service instance, create or select an active one and update all client-side and server-side configuration values that reference it.

#### Additional resources

* [Chat documentation](/docs/chat)
* [Sync documentation](/docs/sync)
* [Notify documentation](/docs/notify)