Voyado incident

Engage - Vipps integration issues

Major Resolved View vendor source →

Voyado experienced a major incident on February 5, 2026 affecting Other, lasting 3h 12m. The incident has been resolved; the full update timeline is below.

Started
Feb 05, 2026, 10:56 AM UTC
Resolved
Feb 05, 2026, 02:09 PM UTC
Duration
3h 12m
Detected by Pingoru
Feb 05, 2026, 10:56 AM UTC

Affected components

Other

Update timeline

  1. investigating Feb 05, 2026, 10:56 AM UTC

    We are currently seeing issues in our integration with Vipps. Investigation ongoing.

  2. resolved Feb 05, 2026, 02:09 PM UTC

    The issue has been resolved.

  3. postmortem Feb 23, 2026, 01:51 PM UTC

    ## Summary On the afternoon of February 5th, we experienced a disruption affecting the delivery of app push notifications for customers using the Vipps integration. The issue was caused by an expired security certificate in a third-party integration service. The problem was identified and resolved the same day, and all delayed events were sent shortly after recovery. ## Customer impact Some customers experienced **delayed app push notifications**. No notifications were lost, and no other functionality within the Voyado platform was affected. The impact was considered minor and non-critical. ## Root cause The issue was caused by an **expired security certificate** used by a third-party integration service that handles communication between Voyado Engage and Vipps. Once the certificate expired, event delivery was temporarily blocked. ## Mitigation After identifying the expired certificate, a new certificate was issued and applied with support from our IT team. Once the integration was restored, **all queued events were successfully sent**. Vipps was informed after resolution. ## Next steps To reduce the risk of similar incidents in the future, we are: * Improving monitoring and alerting for the integration to detect issues earlier * Establishing clearer ownership and reminders for certificate renewals well ahead of expiration We apologize for the inconvenience this delay may have caused and appreciate your understanding.