Vonage: Service Issue in Jumper API Platform
Timeline of updates
- resolved
We have identified an issue impacting outbound messages via the Jumper developer API. Some customers may have experienced failures for the outbound messages sent via Jumper API between 2026-01-19 19:00 UTC and 2026-01-21 12:30 UTC The list of services that were impacted has been confirmed as: Jumper API A fix has been implemented, and the issue has been resolved. Please let support@api.vonage.com know if you continue to experience problems with this.
From Vonage’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on vonageapi.statuspage.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Vonage, started 2026-01-20 14:54 UTC, resolved after 0 min, 1 update(s).
- Title
- Service Issue in Jumper API Platform
- Vendor
- Vonage
- Date
- URL
- https://rewindex.com/company/vonage/incidents/3gg3pywjv6m8
Vonage profileRecent Vonage incidentsAll outages on January 20, 2026Vonage in January 2026MarkdownJSON