Gigalixir Outage History

Gigalixir is up right now

Gigalixir had 7 outages in the last 2 years totaling 46m of downtime — averaging 0.3 incidents per month.

There were 7 Gigalixir outages since November 7, 2024 totaling 46m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.gigalixir.com

Major September 1, 2026

GCP US-Central1 Region AZ Appears Offline

Detected by Pingoru
Sep 01, 2026, 03:25 PM UTC
Resolved
Sep 01, 2026, 04:11 PM UTC
Duration
46m
Affected: US-Central1 (Google Cloud)
Timeline · 5 updates
  1. investigating Sep 01, 2026, 03:25 PM UTC

    The us-central1-b availability zone appears to be offline for GCP. Some of our standard tier database in us-central1 region are unreachable at the moment. We are currently investigating this incident and awaiting GCP action.

  2. monitoring Sep 01, 2026, 03:56 PM UTC

    We are seeing the zone recovery and most databases should be reachable again. we are still monitoring and will post when all is healthy.

  3. monitoring Sep 01, 2026, 03:56 PM UTC

    Note from GCP: _Google Cloud multi-product customers are experiencing elevated packet loss and errors to/from us-central1-b._ _Most recent update – 17 minutes ago September 1, 2026 at 10:38:32 AM UTC-5_ _Google Cloud multi-product customers are experiencing elevated packet loss and errors to/from us-central1-b. We are experiencing an issue with Hybrid Connectivity Tuesday, 2026-09-01 07:44 US/Pacific. Our engineering team continues to investigate the issue. We will provide more information by Tuesday, 2026-09-01 09:15 US/Pacific with current details._

  4. monitoring Sep 01, 2026, 04:06 PM UTC

    The AZ is recovering, we are seeing most back online now. If you still are experiencing issues, write us immediately at [[email protected]](mailto:[email protected]) so we can investigate.

  5. resolved Sep 01, 2026, 04:11 PM UTC

    This incident has been resolved, noted both on our end and by GCP below. All databases appears to be functioning. Any continuing issues, please email us immediately at [email protected]. GCP Note regarding the outage: September 1, 2026 at 11:09:16 AM UTC-5 Multiple products in us-central1-b are experiencing network service degradation. We are experiencing a networking issue starting Tuesday, 2026-09-01 07:41 US/Pacific. The issue is affecting a portion of the us-central1-b zone. The remaining zones in the region are unaffected. Our network engineering team has put in mitigations and we are seeing services starting to recover. We will provide more information by Tuesday, 2026-09-01 09:30 US/Pacific with current details.

Read the full incident report →

Minor February 9, 2026

GitHub Incident with Issues, Actions and Git Operations

Detected by Pingoru
Feb 09, 2026, 07:12 PM UTC
Resolved
Feb 09, 2026, 07:12 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 09, 2026, 07:12 PM UTC

    Type: Incident Duration: 1 hour and 37 minutes Affected Components: US-Central1 (Google Cloud), Europe-West1 (Google Cloud), US-East-1 (AWS), US-West-2 (AWS) Feb 9, 19:12:06 GMT+0 - Investigating - We are currently investigating the repercussions of GitHub's issues for git operations. This will possibly affect some Gigalixir operations if you're pushing to production new builds. Feb 9, 19:36:58 GMT+0 - Identified - We are continuing to monitor GitHub's status for their expected timeline to fix their incident. Feb 9, 20:26:56 GMT+0 - Monitoring - We continue to monitor, please reach out to [[email protected]](mailto:[email protected]) if you are affected and need assistance. Feb 9, 20:49:31 GMT+0 - Resolved - This incident has been resolved. We'll continue to monitor, please reach out if you have questions. Feb 9, 21:03:09 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor March 30, 2025

Unusually High Flow of Traffic

Detected by Pingoru
Mar 30, 2025, 04:15 PM UTC
Resolved
Mar 30, 2025, 04:15 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Mar 30, 2025, 04:15 PM UTC

    Type: Incident Duration: 1 day, 10 hours and 53 minutes Affected Components: US-West-2 (AWS) Mar 30, 16:49:52 GMT+0 - Resolved - We will continue to monitor the situation, but everything is operating as expected, so we will mark this resolved. Mar 30, 16:15:00 GMT+0 - Monitoring - We noticed an issue for roughly 25 minutes due to processing an unusual flow of traffic through this region. We have taken steps to mitigate the impacts on the system and are addressing the root cause. We will continue to monitor the situation, but everything is operating as expected.

Read the full incident report →

Minor November 7, 2024

NPM Builds Not Completeing

Detected by Pingoru
Nov 07, 2024, 04:31 PM UTC
Resolved
Nov 07, 2024, 04:31 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Nov 07, 2024, 04:31 PM UTC

    Type: Incident Duration: 1 day, 14 hours and 58 minutes Affected Components: US-Central1 (Google Cloud), Europe-West1 (Google Cloud), US-East-1 (AWS), US-West-2 (AWS) Nov 7, 16:31:47 GMT+0 - Investigating - We've seen a few customers with issues related to NPM builds not deploying successfully. It appears that NPM has changed their packaging system, causing the build failures. We should have a solution deployed shortly. Nov 7, 17:10:44 GMT+0 - Resolved - As we believed, there was a change in the packaging system, causing build failures. We have applied a fix for the nodejs resolution issues during the build process. Please contact support if you are still experiencing issues with deploying.

Read the full incident report →