Pagero incident

Temporary Phone Support Unavailability

Notice Resolved View vendor source →

Pagero experienced a notice incident on October 20, 2025 affecting Pagero Online, lasting 9h 32m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 03:24 PM UTC
Resolved
Oct 21, 2025, 12:57 AM UTC
Duration
9h 32m
Detected by Pingoru
Oct 20, 2025, 03:24 PM UTC

Affected components

Pagero Online

Update timeline

  1. identified Oct 20, 2025, 03:24 PM UTC

    We’re currently experiencing an issue with our phone service provider that is impacting our ability to receive incoming calls. All other support channels — including web case creation, email, and live chat — remain fully operational. Our provider is actively working to resolve the issue, and our internal teams are implementing additional measures to maintain service stability. We apologize for any inconvenience and appreciate your patience while we work toward a full resolution.

  2. identified Oct 20, 2025, 03:39 PM UTC

    We’ve identified that the issue affecting our phone services is related to a broader global AWS outage. This disruption is causing issues with inbound calls. The impacted platform continues to work toward resolution. All other support channels — including web case creation, email, and live chat — remain fully available. We’re closely monitoring the situation and will continue to provide updates as more information becomes available. Thank you for your continued patience.

  3. monitoring Oct 20, 2025, 08:30 PM UTC

    We're actively investigating an issue that affected our phone services as part of a broader global AWS outage. Inbound calls are working again, but you may still experience occasional interruptions while we finalize a fix. We're working closely with our platform provider to ensure stability and a full resolution. All other support channels, web case creation, email, and live chat, are operating normally. We're monitoring this closely and will share updates as we have them. Thank you for your patience and understanding.

  4. resolved Oct 21, 2025, 12:57 AM UTC

    This incident has been resolved.