Gigalixir incident

GitHub Incident with Issues, Actions and Git Operations

Minor Resolved View vendor source →
Started
Feb 09, 2026, 07:12 PM UTC
Resolved
Feb 09, 2026, 07:12 PM UTC
Duration
Detected by Pingoru
Feb 09, 2026, 07:12 PM UTC

Update timeline

  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.

Looking to track Gigalixir downtime and outages?

Pingoru polls Gigalixir's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Gigalixir reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Gigalixir alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Gigalixir for free

5 free monitors · No credit card required