# Cannot Change Phone Number Home Region in the Twilio Legacy Console

- Provider: [Twilio](https://down.guide/providers/twilio)
- Confidence: Confirmed
- Impact: Degraded
- lasted 1d 18h
- started 2026-06-21 06:28 UTC
- PHONE NUMBERS
- id: DWN-1b261205a4
- Official page: https://stspg.io/hxlx5k5fgn75

## Updates from Twilio
### 2026-06-21 06:28 UTC: investigating
Customers using the Legacy Twilio Console are currently unable to re-route phone numbers between the US1, AU1, and IE1 home regions. Customers using the API are unaffected.
Our engineers have been alerted and are actively investigating. We will provide another update in 1 hour, or as soon as more information becomes available.

### 2026-06-21 06:29 UTC: investigating
We are continuing to investigate this issue.

### 2026-06-21 07:35 UTC: investigating
Customers using the Legacy Twilio Console are currently unable to re-route phone numbers between the US1, AU1, and IE1 home regions. Customers using the API are unaffected.
Our engineers have been alerted and are actively investigating. We will provide another update in 2 hours, or as soon as more information becomes available.

### 2026-06-21 08:30 UTC: identified
We have identified the cause of the issue affecting phone number routing configuration updates in the Legacy Twilio Console. Customers using the Legacy Twilio Console may be unable to update phone number routing between home regions such as US1, IE1, and AU1, and may receive an error when saving changes.
The issue is isolated to the Legacy Console workflow. Customers using One Console or the API directly are not impacted and can use those options as a workaround.
Our engineering team is planning to apply a fix during regular business hours. We will provide another update once implementation begins or as more information becomes available

### 2026-06-23 01:01 UTC: resolved
The issue with customers using the Legacy Twilio Console being unable to update phone number routing between home regions such as US1, IE1, and AU1, and receiving an error when saving changes, has been resolved and this Phone Number feature is operating normally at this time.

From the builder: does your app depend on Twilio? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=twilio) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Twilio.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-1b261205a4), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.