outages.live
Live
Sinch logoSinchMaintenance · 2026-12-01 07:00 UTC

Service Announcement & Maintenance: New SMSC Site & Whitelisting Requirements - US Region

MaintenanceOfficial update

We are writing to inform you that the concerned maintenance activity has been postponed to the below mentioned timeframe. Type: Service Announcement & Maintenance Previous Start Time: 2026-10-15 07:00 UTC Previous End Time: 2026-10-15 08:00 UTC New Start Time: 2026-12-01 07:00 UTC New End Time: 2026-12-01 08:00 UTC As part of our commitment to platform reliability, security, and scalability, Sinch is adding a brand-new, high-efficiency site to our core SMSC billing and messaging routing engine product. This site expansion introduces a next-generation, high-performance architecture to significantly increase our regional capacity, improve overall platform stability, and ensure robust message processing. New Regional Connection Endpoints that are planned to go live 2026-10-15 during the aforementioned time window. US SMPP: us6.smpp.api.sinch.com: US HTTP SMS: us6.httpsms.api.sinch.com US Lookup API: us6.httplookup.api.sinch.com Action Required: Firewall Whitelisting To ensure uninterrupte

The latest update from Sinch.

State

Scheduled

Starts

in 29 d

2026-12-01 07:00 UTC

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Sinch

Scheduled2026-11-01 17:18 UTC

We are writing to inform you that the concerned maintenance activity has been postponed to the below mentioned timeframe. Type: Service Announcement & Maintenance Previous Start Time: 2026-10-15 07:00 UTC Previous End Time: 2026-10-15 08:00 UTC New Start Time: 2026-12-01 07:00 UTC New End Time: 2026-12-01 08:00 UTC As part of our commitment to platform reliability, security, and scalability, Sinch is adding a brand-new, high-efficiency site to our core SMSC billing and messaging routing engine product. This site expansion introduces a next-generation, high-performance architecture to significantly increase our regional capacity, improve overall platform stability, and ensure robust message processing. New Regional Connection Endpoints that are planned to go live 2026-10-15 during the aforementioned time window. US SMPP: us6.smpp.api.sinch.com: US HTTP SMS: us6.httpsms.api.sinch.com US Lookup API: us6.httplookup.api.sinch.com Action Required: Firewall Whitelisting To ensure uninterrupte

Affected components

8
SMPP - USENUM USHTTP - USHTTP USMessaging APIs - SMPP - USMessaging APIs - HTTP - USLookup API Endpoints - ENUM USLookup API Endpoints - HTTP US

Follow Sinch

Your coding agent knows when Sinch is down, and tells you when a failure is theirs, not yours. You can also get Sinch 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 "sinch" and tell me if Sinch 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=sinch
Slack
/feed subscribe https://outages.cc/feed.xml?providers=sinch

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane