Vonage Business incident

Admin Portal Login issues.

Minor Resolved View vendor source →

Vonage Business experienced a minor incident on October 20, 2025 affecting Admin Portal and Desktop App and 1 more component, lasting 12h 34m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 11:35 AM UTC
Resolved
Oct 21, 2025, 12:09 AM UTC
Duration
12h 34m
Detected by Pingoru
Oct 20, 2025, 11:35 AM UTC

Affected components

Admin PortalDesktop AppMobile App (Android™)Mobile App (iOS)Vonage Meetings

Update timeline

  1. identified Oct 20, 2025, 10:42 AM UTC

    Some Vonage Business customers may be experiencing issues accessing their online account at app.vonage.com. Our engineers are working to quickly resolve the issue.

  2. identified Oct 20, 2025, 10:42 AM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Oct 20, 2025, 11:35 AM UTC

    Following a service disruption reported by Amazon Web Services (AWS), we are monitoring the impact to some Vonage services, which may have affected your VBC service. AWS has applied initial mitigations and are reporting early signs of recovery. We are engaged with AWS as recovery continues. We will provide further updates as more information becomes available and once full service is restored. Thank you for your patience and understanding.

  4. monitoring Oct 20, 2025, 12:14 PM UTC

    We continue to see recovery following the Amazon Web Services (AWS) reported service disruption earlier today which may have impacted your VBC services. AWS has identified a potential root cause and applied initial mitigations, and are reporting early signs of recovery across affected services. We remain engaged with AWS as recovery continues. We’ll provide further updates as more information becomes available or once full service is restored. Thank you for your continued patience and understanding.

  5. monitoring Oct 20, 2025, 01:05 PM UTC

    We continue to see recovery following the Amazon Web Services (AWS) reported service disruption earlier today which may have impacted your VBC services. AWS has identified a potential root cause and applied mitigations, and is reporting signs of recovery across affected services. We will provide further updates as more information becomes available and once full service is restored. Thank you for your continued patience and understanding.

  6. monitoring Oct 20, 2025, 01:13 PM UTC

    We are continuing to monitor for any further issues.

  7. monitoring Oct 20, 2025, 02:06 PM UTC

    We continue to see recovery following the Amazon Web Services (AWS) reported service disruption earlier today which may have impacted your VBC services. AWS has identified a potential root cause and applied mitigations, and is reporting signs of recovery across affected services. We will provide further updates as more information becomes available and once full service is restored. Thank you for your continued patience and understanding.

  8. monitoring Oct 20, 2025, 03:08 PM UTC

    We continue to see recovery following the Amazon Web Services (AWS) reported service disruption earlier today which may have impacted your VBC services. AWS has identified a potential root cause and applied mitigations, and is reporting signs of recovery across affected services. We will provide further updates as more information becomes available and once full service is restored. Thank you for your continued patience and understanding.

  9. monitoring Oct 20, 2025, 04:05 PM UTC

    We continue to see recovery following the Amazon Web Services (AWS) reported service disruption earlier today which may have impacted your VBC services. AWS has identified a potential root cause and applied mitigations, and is reporting signs of recovery across affected services. We will provide further updates as more information becomes available and once full service is restored. Thank you for your continued patience and understanding.

  10. monitoring Oct 20, 2025, 05:05 PM UTC

    We continue to see recovery following the Amazon Web Services (AWS) reported service disruption earlier today which may have impacted your VBC services. AWS has identified a potential root cause and applied mitigations, and is reporting signs of recovery across affected services. We will provide further updates as more information becomes available and once full service is restored. Thank you for your continued patience and understanding.

  11. monitoring Oct 20, 2025, 05:15 PM UTC

    We continue to see recovery following the Amazon Web Services (AWS) reported service disruption earlier today which may have impacted your VBC services. AWS has identified a potential root cause and applied mitigations, and is reporting signs of recovery across affected services. We will provide further updates as more information becomes available and once full service is restored. Thank you for your continued patience and understanding.

  12. monitoring Oct 20, 2025, 09:05 PM UTC

    We continue to see recovery following the Amazon Web Services (AWS) reported service disruption earlier today which may have impacted your VBC services. AWS has identified a potential root cause and applied mitigations, and is reporting signs of recovery across affected services. We will provide further updates as more information becomes available and once full service is restored. Thank you for your continued patience and understanding.

  13. monitoring Oct 20, 2025, 11:08 PM UTC

    We continue to see recovery following the Amazon Web Services (AWS) reported service disruption earlier today which may have impacted your VBC services. AWS has identified a potential root cause and applied mitigations, and is reporting signs of recovery across affected services. We will provide further updates as more information becomes available and once AWS confirms full service is restored. Thank you for your continued patience and understanding.

  14. resolved Oct 21, 2025, 12:09 AM UTC

    Vonage services have been fully restored following today’s service disruption reported by AWS. Full resolution of the incident has been confirmed by AWS effective 6:53 pm ET. We thank you for your patience and understanding as we worked with AWS to restore services as quickly as possible.