Gini Outage History

Gini is up right now

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

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

Source: https://status.gini.net

Notice July 17, 2026

Partial Service Outage

Detected by Pingoru
Jul 17, 2026, 09:00 AM UTC
Resolved
Jul 17, 2026, 10:20 AM UTC
Duration
1h 20m
Affected: Native DocumentsPay APIScanned DocumentsUser-Center APIText Documents
Timeline · 2 updates
  1. investigating Jul 17, 2026, 09:00 AM UTC

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

  2. resolved Jul 17, 2026, 10:20 AM UTC

    Between 11:00 CET and 11:15 CET, the service experienced degraded availability due to an internal database process that caused resource contention and impacted production services. The underlying cause has been identified and the service has been fully restored. We have identified the necessary corrective measures and are implementing changes to prevent this type of issue from affecting production services in the future.

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 →