Voucherify Outage History

Voucherify is up right now

Voucherify had 6 outages in the last 2 years totaling 57h 41m of downtime — averaging 0.2 incidents per month.

There were 6 Voucherify outages since September 3, 2025 totaling 57h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.voucherify.io

Notice May 8, 2026

us1 - AWS operational issue in N.Virginia - Increased Error Rate and Latency

Detected by Pingoru
May 08, 2026, 01:18 AM UTC
Resolved
May 09, 2026, 09:09 AM UTC
Duration
1d 7h
Affected: US1 - APIUS1 - Dashboard
Timeline · 4 updates
  1. investigating May 08, 2026, 01:18 AM UTC

    We observe increased error rate and API response times at voucherify caused by an operational issue of our cloud provider in N. Virginia. We are currently investigating the issue.

  2. monitoring May 08, 2026, 02:51 AM UTC

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

  3. monitoring May 08, 2026, 03:21 AM UTC

    We continue to monitor for any further issues. So far the impact on us1 cluster was very limited: increased API response latency for 50 minutes (mostly p95 and p99 longtail), between 2026-05-07 23:36 and 2026-05-08 00:48 UTC

  4. resolved May 09, 2026, 09:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 10, 2026

dsa1 - Partial outage

Detected by Pingoru
Feb 10, 2026, 10:27 AM UTC
Resolved
Feb 10, 2026, 01:33 PM UTC
Duration
3h 5m
Timeline · 2 updates
  1. monitoring Feb 10, 2026, 10:27 AM UTC

    dsa1 environment: We've observed a period of elevated errors from both the Voucherify API and Dashboard between 09:38 UTC and 09:46. The situation is now stabilized, we are monitoring the services related to this environment.

  2. resolved Feb 10, 2026, 01:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 10, 2026

deu4 - Partial outage

Detected by Pingoru
Feb 10, 2026, 10:23 AM UTC
Resolved
Feb 10, 2026, 01:33 PM UTC
Duration
3h 9m
Timeline · 2 updates
  1. monitoring Feb 10, 2026, 10:23 AM UTC

    deu4 environment: We've observed a period of elevated errors from both the Voucherify API and Dashboard between 09:36 UTC and 09:40. The situation is now stabilized, we are monitoring the services related to this environment.

  2. resolved Feb 10, 2026, 01:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 20, 2025

us1 - elevated error rate due to AWS large-scale outage in us-east-1

Detected by Pingoru
Oct 20, 2025, 07:27 PM UTC
Resolved
Oct 21, 2025, 07:20 AM UTC
Duration
11h 53m
Affected: US1 - APIUS1 - Dashboard
Timeline · 2 updates
  1. monitoring Oct 20, 2025, 07:27 PM UTC

    See https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_BA540_514A652BE1A

  2. resolved Oct 21, 2025, 07:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 9, 2025

Delayed processing of customers data (stale data or no new customers visible in Dashboard)

Detected by Pingoru
Sep 09, 2025, 03:02 PM UTC
Resolved
Sep 09, 2025, 07:36 PM UTC
Duration
4h 33m
Affected: EU1 - APIEU1 - Dashboard
Timeline · 4 updates
  1. identified Sep 09, 2025, 03:02 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Sep 09, 2025, 03:04 PM UTC

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

  3. monitoring Sep 09, 2025, 05:29 PM UTC

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

  4. resolved Sep 09, 2025, 07:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 3, 2025

Delayed distributions based on customer segments (incl. webhooks / email / sms delivery)

Detected by Pingoru
Sep 03, 2025, 02:25 PM UTC
Resolved
Sep 03, 2025, 05:34 PM UTC
Duration
3h 8m
Affected: EU1 - APIAS1 - APIUS1 - API
Timeline · 3 updates
  1. identified Sep 03, 2025, 02:25 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Sep 03, 2025, 04:08 PM UTC

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

  3. resolved Sep 03, 2025, 05:34 PM UTC

    This incident has been resolved.

Read the full incident report →