Nigeria SMS - Delivery Degradation affecting MTN Nigeria Network
This incident has been resolved.
The latest update from Vonage API.
State
Resolved
Started
11 d ago
2026-10-22 01:10 UTC
Lasted
2 h 24 min
until 2026-10-22 03:33 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
1 h 39 min 69%
Monitoring
45 min 31%
Updates
Times in UTCAs posted by Vonage API
This incident has been resolved.
We are continuing to monitor for any further issues.
A fix has been implemented and we are monitoring the results.
Please be informed that we are currently observing SMS delivery degradation towards MTN Nigeria Network. We are working with our carrier partners to resolve the issue and will issue an update as soon as more information becomes available. If you have any questions, please contact api.support.vonage.com
Affected components
2Follow 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.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 "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.cc/feed.xml?providers=vonage/feed subscribe https://outages.cc/feed.xml?providers=vonageFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane