CHYP.ai · ORBIT // Cloudy_Day Security Suite

APIs: messaging, media, analytics

Degraded / minor incident Vonage API status

vonage.com · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

Vonage API's status page shows “Degraded / minor incident” in Voice API and SIP Trunking; the vendor is resolved. User reports haven't spiked, so wide impact isn't visible yet. Amazon Web Services, a provider it may run on (inferred), also reports trouble. Coincidence, not causation.

confidence: low Vendor: minor issue · users: normal · routing: no data · upstream providers: major.

Vendor status vs. reality: Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal)

Regions mentioned: Voice API, SIP Trunking, SMS Europe

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started22 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the change1 h 20 min

Evidence

  • Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
  • Vendor stage: resolved on “Service issue in Voice platform”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low
  • Amazon Web Services reports an issue. Vonage API may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low

What we don't know: what is happening inside Vonage API's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.

Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .

Cloudy_Day's take

Stage vs. health

The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: no data · upstream providers: major. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).

Who depends on whom

Vonage API may run on Amazon Web Services (inferred). We don't map other services that depend on Vonage API. Dependency chains are where single points of failure hide.

Identity & trust lens

Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.

For users

Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.

For security teams

Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Vonage API or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).

What to watch next

The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Vonage API. No blame or attack claims without an official source. Generated .

INCIDENT REPLAY

Service issue in Voice platform

minor resolved · started · resolved

3 updates

  1. investigating

    We are aware of issues that may be impacting PSTN/SIP connectivity in the APAC region. We are actively investigating and working to resolve this as quickly as possible. We will provide a further update within 2 hours. Thank you for your patience and understanding. If you have any questions in the meantime, please contact our support team at https://api.support.vonage.com.

  2. monitoring

    Vonage services continue to show signs of recovery following today's interruption to PSTN/SIP connectivity in the APAC region. We are continuing to monitor closely to confirm full stability. We will continue to provide further updates here within 2 hours and once full service is restored. Thank you for your patience and understanding as we work to restore services as quickly as possible. If you have any questions in the meantime, please contact our support team at https://api.support.vonage.com.

  3. resolved

    Vonage services have been fully restored following today's service interruption to PSTN/SIP connectivity in the APAC region, which began at 2026-11-10 09:47 UTC. Full resolution has been confirmed effective at 2026-11-10 10:11 UTC. Thank you for your patience and understanding as we worked to restore services as quickly as possible. If you have any questions, please contact api.support.vonage.com.

Official incident page ↗

Community comments (0)

Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.

No approved comments yet.

How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.

Where to next