Overleaf incident

Git integration is restored

Critical Ongoing View vendor source →

Overleaf is currently experiencing a critical incident affecting Git Access (git.overleaf.com), which began 23h ago. The vendor's full update timeline is below.

Started
Jul 01, 2026, 01:47 PM UTC
Resolved
Ongoing
Duration
● 22h 47m
Detected by Pingoru
Jul 01, 2026, 01:47 PM UTC

Affected components

Git Access (git.overleaf.com)

Update timeline

  1. investigating Jul 01, 2026, 01:47 PM UTC

    The Git integration functionality is currently down. Investigation is on going.

  2. investigating Jul 02, 2026, 08:03 AM UTC

    We are still investigating the issue.

  3. monitoring Jul 02, 2026, 12:13 PM UTC

    We've resolved the issue affecting GitBridge and the service is back to normal. We're sorry for any disruption this caused. If you were working with your repository during this time, you may find that your local copy and the version on our servers have diverged. The simplest way to get back on track is to perform a fresh clone of your repository, which will give you a clean, synchronised version of your project. Before you re-clone, we'd recommend keeping a copy of your current local repository in a separate location. This means that if you made any changes during the disruption, you'll have them available to review and copy into your freshly cloned version afterwards. If you'd prefer not to re-clone and are comfortable with Git, you may be able to resolve any discrepancies manually by fetching the latest state and rebasing your local commits — though if you're unsure, the fresh clone is the safer route. If you run into any persistent issues after re-cloning or attempting a manual rebase, please use our contact form to get in touch with us: https://www.overleaf.com/contact