Eversend Outage History

Eversend is up right now

Eversend had 3 outages in the last 2 years totaling 1159h 58m of downtime — averaging 0.1 incidents per month.

There were 3 Eversend outages since August 6, 2025 totaling 1159h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://eversend.statuspage.io

Critical July 30, 2026

Virtual Card Creation Outage

Detected by Pingoru
Jul 30, 2026, 07:32 AM UTC
Resolved
Jul 30, 2026, 12:07 PM UTC
Duration
4h 34m
Affected: Creating a new virtual card
Timeline · 2 updates
  1. identified Jul 30, 2026, 07:32 AM UTC

    We are currently experiencing a service disruption that is preventing the creation of new virtual cards.

  2. resolved Jul 30, 2026, 12:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 5, 2026

Technical Mainteneance

Detected by Pingoru
Jul 05, 2026, 08:23 AM UTC
Resolved
Jul 05, 2026, 01:24 PM UTC
Duration
5h 1m
Timeline · 2 updates
  1. identified Jul 05, 2026, 08:23 AM UTC

    We are currently performing unscheduled maintenance, and some of our services are temporarily unavailable. Our team is working to restore normal service as quickly as possible. We will provide an update as soon as services have been fully restored. We sincerely apologize for the inconvenience and appreciate your patience.

  2. identified Jul 05, 2026, 08:25 AM UTC

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

Read the full incident report →

Major August 6, 2025

GHS Mobile Money Collections Issue 🚨

Detected by Pingoru
Aug 06, 2025, 11:07 AM UTC
Resolved
Sep 23, 2025, 09:29 AM UTC
Duration
47d 22h
Affected: Adding GHS by mobile money
Timeline · 3 updates
  1. identified Aug 06, 2025, 11:07 AM UTC

    We are experiencing intermittent issues with GHS collections, where some transactions may fail to process, while others may experience prolonged delays to get processed successfully. We sincerely apologize for the inconvenience and appreciate your patience as the responsible party works diligently to resolve the issue as quickly as possible.

  2. identified Aug 26, 2025, 09:05 AM UTC

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

  3. resolved Sep 23, 2025, 09:29 AM UTC

    This incident has been resolved.

Read the full incident report →