Service Announcement & Maintenance: New SMSC Site & Whitelisting Requirements - US Region
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 UTCAs posted by Sinch
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
8Sinch in the last 90 days
Full historyIncidents in 90 days
47
Days with an incident
33
Median duration
2 h 55 min
This incident
Not comparable
Other Sinch incidents
All incidents
Sinch·Delivery Issue United States - Google Voice
Sinch reports a delivery issue for SMS in the United States on Google Voice. The affected components are SMS - US - ShortCode and External Connectivity - SMS - US - ShortCode. Sinch is investigating the issue.
Sinch·Delivery Issue Belgium - VOOmobile & MobiStar
This incident has been resolved. Incident Start Time: 2026-10-28 15:06 UTC Incident End Time: 2026-10-28 20:25 UTC
Sinch·Delivery Issue United States - AT&T
This incident has been resolved. Incident Start Time: 2026-10-27 03:14 UTC Incident End Time: 2026-10-27 04:11 UTC
Sinch·Service Degradation - Customer Dashboard and Account Balance
At 2026-10-26 12:58, UTC a planned change caused unforeseen issues affecting the Sinch customer dashboard and our balance calculations. Our engineering teams immediately investigated the issue. Once identified, the change was successfully rolled back and functionality was restored. During the below time frame customers may have experienced issues reaching the Sinch customer dashboard, or experienced problems sending traffic over a subset of accounts due to a block caused by the balance calculation discrepancy. Incident Start Time: 2026-10-26 12:58 UTC Incident End Time: 2026-10-26 15:11 UTC For any inquiries, please contact support@sinch.com
Sinch·Service Degredation - Lookup API
This incident has been resolved. Incident Start Time: 2026-10-26 00:30 UTC Incident End Time: 2026-10-26 01:59 UTC
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.
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.live/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.
https://outages.live/feed.xml?providers=sinch/feed subscribe https://outages.live/feed.xml?providers=sinchFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane