Eligible Outage History

Eligible is up right now

Eligible had 2 outages in the last 2 years totaling 56m of downtime — averaging 0.1 incidents per month.

There were 2 Eligible outages since June 3, 2025 totaling 56m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.eligible.com

Notice October 20, 2025

Service Disruption Resolved - Post-Incident Update

Detected by Pingoru
Oct 20, 2025, 09:51 AM UTC
Resolved
Oct 20, 2025, 09:58 AM UTC
Duration
7m
Affected: Eligible APIEligible SandboxEligible.com
Timeline · 2 updates
  1. monitoring Oct 20, 2025, 09:51 AM UTC

    Between 12:11 AM and 2:30 AM PDT this morning, our services experienced a major disruption due to an infrastructure provider outage in the US-East region. The issue affected authentication, API requests, and data processing capabilities. Our services are beginning to recover. Most functionality has been restored, though some users may still experience intermittent issues or slower performance as systems process backlogs. Our Incident Response team continues to monitor the situation closely.

  2. resolved Oct 20, 2025, 09:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 3, 2025

Increased API Error Rates

Detected by Pingoru
Jun 03, 2025, 07:47 PM UTC
Resolved
Jun 03, 2025, 08:36 PM UTC
Duration
49m
Affected: Eligible API
Timeline · 3 updates
  1. investigating Jun 03, 2025, 07:47 PM UTC

    Incident Status Update Status: Investigating Impact: API Service Disruption Started: 6/3 3:44PM EST We are currently investigating reports of issues affecting our API service. Users may experience intermittent failures, increased response times, or service unavailability when making API requests. Current Actions: Engineering and DevSecOp Admin teams have been notified and are actively investigating Monitoring systems are being reviewed to identify the root cause We are working to restore full service as quickly as possible

  2. monitoring Jun 03, 2025, 08:15 PM UTC

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

  3. resolved Jun 03, 2025, 08:36 PM UTC

    This incident has been resolved.

Read the full incident report →