Gini Outage History

Gini is up right now

Gini had 3 outages in the last 2 years totaling 7h 57m of downtime — averaging 0.1 incidents per month.

There were 3 Gini outages since December 23, 2024 totaling 7h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.gini.net

Critical June 29, 2026

Partial Service Outage

Detected by Pingoru
Jun 29, 2026, 12:32 PM UTC
Resolved
Jun 29, 2026, 07:27 PM UTC
Duration
6h 54m
Affected: Native DocumentsPay APIScanned DocumentsUser-Center APIText Documents
Timeline · 5 updates
  1. investigating Jun 29, 2026, 12:32 PM UTC

    We are currently facing an outage in parts of our system. We are currently investigating this issue.

  2. monitoring Jun 29, 2026, 01:18 PM UTC

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

  3. investigating Jun 29, 2026, 02:39 PM UTC

    We are currently investigating this issue.

  4. monitoring Jun 29, 2026, 03:01 PM UTC

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

  5. resolved Jun 29, 2026, 07:27 PM UTC

    The fix is working, our APIs are stable

Read the full incident report →

Critical October 9, 2025

Service Degradation

Detected by Pingoru
Oct 09, 2025, 12:54 PM UTC
Resolved
Oct 09, 2025, 01:50 PM UTC
Duration
55m
Timeline · 2 updates
  1. investigating Oct 09, 2025, 12:54 PM UTC

    We are currently facing a degradation in parts of our services. We are currently investigating this issue.

  2. resolved Oct 09, 2025, 01:50 PM UTC

    We've had a failure on the component providing redundancy to our user database, causing all services to be briefly unavailable.

Read the full incident report →

Major August 18, 2025

Access to all APIs impaired

Detected by Pingoru
Aug 18, 2025, 02:00 PM UTC
Resolved
Aug 18, 2025, 02:07 PM UTC
Duration
7m
Timeline · 2 updates
  1. investigating Aug 18, 2025, 02:00 PM UTC

    We are seeing connection issues to our main datacenter, this is being investigate by our teams right now.

  2. resolved Aug 18, 2025, 02:07 PM UTC

    This incident has been resolved.

Read the full incident report →