gitarena - Notice history

All systems operational

100% - uptime

Frontend - Operational

100% - uptime
May 2026 · 100.0%Jun · 99.99%Jul · 100.0%

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Backend - Operational

100% - uptime
May 2026 · 99.87%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2026
Jun 2026
Jul 2026

API - Operational

100% - uptime
May 2026 · 99.97%Jun · 99.89%Jul · 100.0%

Previous page

Next page

May 2026
Jun 2026
Jul 2026
100% - uptime

Git over SSH - Operational

100% - uptime
May 2026 · 99.89%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Git over HTTP - Operational

100% - uptime
May 2026 · 99.88%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2026
Jun 2026
Jul 2026

Notice history

Jul 2026

No notices reported this month

Jun 2026

Elevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)
  • Resolved
    Resolved

    This incident has been resolved.

  • Monitoring
    Monitoring

    All traffic has been restored to the FRA1 Vercel Region.

  • Update
    Update

    The issue has been fixed. We are starting to re-route traffic from the CDG1 Vercel Region back to the FRA1 Vercel Region. We will provide another status update after this has finished.

  • Update
    Update

    The impact is currently mitigated. We are continuing to re-route traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.

  • Identified
    Identified

    We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.

  • Investigating
    Investigating

    We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue.

Frontend is back up
  • Resolved
    Resolved
    Frontend is back up. This incident was automatically resolved by Instatus monitoring.
  • Investigating
    Investigating
    Frontend is down at the moment. This incident was automatically created by Instatus monitoring.
Backend Proxy is back up
  • Resolved
    Resolved
    API is back up. This incident was automatically resolved by Instatus monitoring.
  • Investigating
    Investigating
    API is down at the moment. This incident was automatically created by Instatus monitoring.
Scheduled maintenance on database
  • Completed
    June 05, 2026 at 10:00 PM
    Completed
    June 05, 2026 at 10:00 PM
    Maintenance has completed successfully
  • In progress
    June 05, 2026 at 6:00 PM
    In progress
    June 05, 2026 at 6:00 PM
    Maintenance is now in progress
  • Planned
    June 05, 2026 at 6:00 PM
    Planned
    June 05, 2026 at 6:00 PM

    During that time a short interruption of service may occur due to changing DNS pointers to our fallback database.

May 2026

Git over HTTP is back up
  • Resolved
    Resolved
    Git over HTTP is back up. This incident was automatically resolved by Instatus monitoring.
  • Investigating
    Investigating
    Git over HTTP is down at the moment. This incident was automatically created by Instatus monitoring.
Backend is back up
  • Resolved
    Resolved
    Backend is back up. This incident was automatically resolved by Instatus monitoring.
  • Investigating
    Investigating
    Backend is down at the moment. This incident was automatically created by Instatus monitoring.
Git over SSH is back up
  • Resolved
    Resolved
    Git over SSH is back up. This incident was automatically resolved by Instatus monitoring.
  • Investigating
    Investigating
    Git over SSH is down at the moment. This incident was automatically created by Instatus monitoring.
Git over HTTP is back up
  • Resolved
    Resolved
    Git over HTTP is back up. This incident was automatically resolved by Instatus monitoring.
  • Investigating
    Investigating
    Git over HTTP is down at the moment. This incident was automatically created by Instatus monitoring.
Backend Proxy is back up
  • Resolved
    Resolved
    API is back up. This incident was automatically resolved by Instatus monitoring.
  • Investigating
    Investigating
    API is down at the moment. This incident was automatically created by Instatus monitoring.

May 2026 to Jul 2026

Next