Telnyx reported "Cloud Storage us-west-1 Region Temporarily Unavailable" on its status page at 2026-10-02 14:20 UTC.

Telnyx did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-10-02 14:20 UTC and ended at 2026-10-02 15:06 UTC. It lasted 46 min.

How do I get alerts for Telnyx?

Subscribe to the Telnyx live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Telnyx. outages.live reads it every few minutes and keeps every update.

TTelnyxIncident · 2026-10-02 14:20 UTC

Cloud Storage us-west-1 Region Temporarily Unavailable

ResolvedOfficial update

All cloud storage operations in us-west-1 are fully available.

The latest update from Telnyx.

State

Resolved

Started

30 d ago

2026-10-02 14:20 UTC

Lasted

46 min

until 2026-10-02 15:06 UTC

Worst impact

Partial outage

Timeline

3 updates

14:2014:3214:4314:5515:06

Partial outageUpdate postedTimes in UTC

Investigating

40 min 87%

Monitoring

6 min 13%

Updates

Times in UTC

As posted by Telnyx

Resolved2026-10-02 15:06 UTC

All cloud storage operations in us-west-1 are fully available.

Monitoring2026-10-02 15:01 UTC

Cloud Storage read and write operations should be fully available in us-west-1 region now.

Investigating2026-10-02 14:20 UTC

All cloud storage read and write operations in us-west-1 might be temporarily unavailable. We're actively working on resolving the issue.

Telnyx in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

2 h 34 min

This incident

70% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

31 h 37 min

median 2 h 34 min

90 days agoToday

Other Telnyx incidents

All incidents

Telnyx·Messaging Webhook Delays

We believe the issue is now resolved

Resolvedresolved 2 d ago

Telnyx·Delays with Messaging Webhooks, Mission Control Number and Porting ordering/configurations

Our team found the root cause of this issue to be due to a network blip leading to various service issues. It was confirmed to be brief and all services are now caught up as of 15:15UTC.

Resolvedresolved 3 d ago

Telnyx·Telephony tokens 503s error

A rollback was applied at ~15:54 UTC and credential creation has been healthy since 15:58 UTC.

Resolvedresolved 4 d ago

Telnyx·Unexpected wireless voice usage and charges

Resolved

Resolvedresolved 3 d ago

Telnyx·Wireless session drops in DC2

NAT errors resulted in user-plane issues for some users.

Resolvedresolved 4 d ago

Follow Telnyx

Your coding agent knows when Telnyx is down, and tells you when a failure is theirs, not yours. You can also get Telnyx incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "telnyx" and tell me if Telnyx has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=telnyx

Slack

/feed subscribe https://outages.cc/feed.xml?providers=telnyx

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane