[DC2] Wireguard Server Migration
We will be doing a maintenance on wireguard server in the Ashburn (DC2) region. No IP addresses will be changed, so impact should be limited to client re-handshake with the server. No customer action required.
The latest update from Telnyx.
State
Scheduled
Started
46 d ago
2026-09-16 16:07 UTC
Ongoing for
46 days
Worst impact
Maintenance
Timeline
1 updateScheduled
46 days 100%
Updates
Times in UTCAs posted by Telnyx
We will be doing a maintenance on wireguard server in the Ashburn (DC2) region. No IP addresses will be changed, so impact should be limited to client re-handshake with the server. No customer action required.
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.
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.
https://outages.cc/feed.xml?providers=telnyx/feed subscribe https://outages.cc/feed.xml?providers=telnyxFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane