We've resolved the issue affecting GitBridge and the service is back to normal. We're sorry for any disruption this caused.
As part of recovering the service, we restored the Git integration from a backup taken shortly before the disruption began. Commit history up to that point was preserved, however changes made through the Git integration in the short window between that backup and the start of the incident could not be recovered. No project data was lost. Your documents, files, and project history within Overleaf itself were not affected.
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
Posted Jul 02, 2026 - 12:13 UTC
Update
We are still investigating the issue.
Posted Jul 02, 2026 - 08:03 UTC
Investigating
The Git integration functionality is currently down. Investigation is on going.
Posted Jul 01, 2026 - 13:47 UTC
This incident affected: overleaf.com (Git Access (git.overleaf.com)).