Eversend Outage History

Eversend is up right now

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

There were 3 Eversend outages since July 5, 2026 totaling 180h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://eversend.statuspage.io

Notice September 3, 2026

MTN XAF Withdrawals — Service Instability

Detected by Pingoru
Sep 03, 2026, 06:20 AM UTC
Resolved
Sep 10, 2026, 09:01 AM UTC
Duration
7d 2h
Timeline · 2 updates
  1. investigating Sep 03, 2026, 06:20 AM UTC

    We are currently experiencing instability with MTN withdrawals in XAF. Some withdrawal transactions may fail, remain pending, or take longer than usual to process. Our team is actively investigating the issue with our provider and working to restore stable service as quickly as possible. We apologize for the inconvenience and appreciate your patience while we work on a resolution.

  2. identified Sep 08, 2026, 07:24 AM UTC

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

Read the full incident report →

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 →