Russia SMS - Planned maintenance affecting Beeline
Between 16.11.2026 13:00 UTC and 14:00 UTC, the operator Beeline will be performing maintenance on their SMS platform. During this maintenance period, there may be difficulties in delivering messages to and from the subscribers of this Beeline operator. If you have any questions, please contact api.support.vonage.com
The latest update from Vonage API.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Vonage API
Between 16.11.2026 13:00 UTC and 14:00 UTC, the operator Beeline will be performing maintenance on their SMS platform. During this maintenance period, there may be difficulties in delivering messages to and from the subscribers of this Beeline operator. If you have any questions, please contact api.support.vonage.com
Between 16.11.2026 13:00 UTC and 14:00 UTC, the operator Beeline will be performing maintenance on their SMS platform. During this maintenance period, there may be difficulties in delivering messages to and from the subscribers of this Beeline operator. If you have any questions, please contact api.support.vonage.com
Affected components
2Vonage API in the last 90 days
Full historyIncidents in 90 days
80
Days with an incident
50
Median duration
3 h 26 min
This incident
Not comparable
Other Vonage API incidents
All incidentsVonage API·France SMS - Delivery Degradation towards Lebara France
Vonage API reported degraded SMS delivery to the Lebara France network. The incident affected SMS Europe and Global Connectivity - SMS Europe. Vonage API resolved the incident after 2 hours and 35 minutes.
Vonage API·USA SMS - Delivery degradation affecting 10DLC traffic towards AT&T operator
Vonage API reports SMS delivery degradation for 10DLC traffic towards the AT&T operator in the USA. The affected components are SMS North America and Global Connectivity - SMS North America. The incident is resolved and lasted about 3 hours and 25 minutes.
Vonage API·USA MMS - Delivery latency affecting MMS messages affecting multiple networks
Vonage API reports delayed MMS message delivery in North America. The issue affects MMS North America and Global Connectivity - MMS North America. Vonage API resolved the incident after about 16 hours and 12 minutes.
Vonage API·Issue with Spain Movistar RCS Delivery
Vonage API reported degraded RCS delivery for Spain Movistar on RCS Connectivity and Global Connectivity - RCS Connectivity. Vonage API resolved the incident. It lasted about 19 hours.
Vonage API·Issue with WhatsApp onboarding
Vonage API reports an issue with WhatsApp onboarding. The problem affects WhatsApp Connectivity and Global Connectivity - Whatsapp Connectivity. Vonage API states that the incident is resolved. The outage lasted 4 hours and 49 minutes.
Follow Vonage API
Your coding agent knows when Vonage API is down, and tells you when a failure is theirs, not yours. You can also get Vonage API 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 "vonage" and tell me if Vonage API 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=vonage/feed subscribe https://outages.live/feed.xml?providers=vonageFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane