Vi Trust Outage History

Vi Trust is up right now

Vi Trust had 2 outages in the last 2 years totaling 18h 5m of downtime, averaging 0.1 incidents per month.

There were 2 Vi Trust outages since October 20, 2025 totaling 18h 5m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: trust.virtualincentives.com

Notice November 18, 2025

Cloudflare Global Outage

Detected by Pingoru
Nov 18, 2025, 11:45 AM UTC
Resolved
Nov 18, 2025, 03:21 PM UTC
Duration
3h 35m
Affected: Batch APIGlobal eGiftcard APIRecipient PlatformRest APIVisa and MastercardVI Now Client PortalWebhooks
Timeline · 4 updates
  1. identified Nov 18, 2025, 02:11 PM UTC

    We’re experiencing service disruptions due to an ongoing Cloudflare outage. Our team is monitoring the situation and will provide updates as Cloudflare restores normal operations

  2. identified Nov 18, 2025, 02:14 PM UTC

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

  3. monitoring Nov 18, 2025, 02:43 PM UTC

    A fix has been implemented and we believe the incident is now resolved. We are continuing to monitor for errors to ensure all services are back to normal.

  4. resolved Nov 18, 2025, 03:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 20, 2025

AWS Global Outage

Detected by Pingoru
Oct 20, 2025, 07:11 AM UTC
Resolved
Oct 20, 2025, 09:41 PM UTC
Duration
14h 29m
Affected: Batch APIGlobal eGiftcard APIRecipient PlatformRest APIVisa and MastercardVI Now Client PortalWebhooks
Timeline · 4 updates
  1. identified Oct 20, 2025, 05:01 PM UTC

    We’re experiencing service disruptions due to an ongoing AWS outage. Our team is monitoring the situation and will provide updates as AWS restores normal operations.

  2. identified Oct 20, 2025, 05:04 PM UTC

    AWS continues to experience issues affecting some of our services. We’re seeing partial recovery but are still monitoring performance closely. We’ll share another update as soon as AWS confirms full resolution.

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

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 20, 2025, 09:41 PM UTC

    This incident has been resolved.

Read the full incident report →