Overleaf outage history

We are investigating reports of Google SSO login issues for some users.

Some users are seeing success by waiting for several minutes before retrying login with Google SSO. Other login methods are unaffected. We are continuing to investigate.

We are continuing to investigate. Some users are seeing successful logins when retrying after several minutes. Also, if possible, try using a password or resetting your password to access your account: [https://www.overleaf.com/user/password/reset](https://www.overleaf.com/user/password/reset "https://www.overleaf.com/user/password/reset")

We are continuing to investigate. We believe we have isolated the problem to users who use "Log In with Google". Some users are seeing successful logins when retrying after several minutes. Also, if possible, try using a password or resetting your password to access your account: [https://www.overleaf.com/user/password/reset](https://www.overleaf.com/user/password/reset "https://www.overleaf.com/user/password/reset")

We are continuing to investigate. We have isolated the problem to users who use "Log In with Google". Some users are seeing successful logins when retrying after several minutes. Also, if possible, try using a password or resetting your password to access your account: [https://www.overleaf.com/user/password/reset](https://www.overleaf.com/user/password/reset "https://www.overleaf.com/user/password/reset")

We are continuing to investigate. We have isolated the problem to users who use "Log In with Google". Other SSO providers are not affected, and neither is email & password based login. Some users are seeing successful logins when retrying after several minutes. Also, if possible, try using a password or resetting your password to access your account: [https://www.overleaf.com/user/password/reset](https://www.overleaf.com/user/password/reset "https://www.overleaf.com/user/password/reset")

We have identified a possible issue with some users' experience of "Log in with Google" SSO functionality. We have implemented a workaround and are investigating further in conjunction with Google. In the meantime a small number of users may experience some extra confirmation steps when logging in with their Google account. Please contact our Support team if you are still unable to log in with Google.

We have identified a possible issue with some users' experience of "Log in with Google" Single Sign-On (SSO) functionality. We have implemented a temporary fix that may benefit some users, and are continuing to investigate further in conjunction with Google. A small number of users may experience some extra confirmation steps when logging in with their Google account. If you still experience issues, you may be able to use a password, or reset your password to access your account:  . Please contact our Support team if you have any questions.

Some users will get an error response when requesting suggestions via the Writefull models

We are working to improve availability of suggestion models. Other site functions are not affected.

The situation is improving. We are continuing to monitor.

The issue with suggestions has been resolved. We are continuing to monitor the service.

We are currently experiencing issues with in-editor AI features, including TeXGPT or Insert math from text or image, and are investigating.

The issue is resolved, all AI features are working normally again.

Conversions/Submissions are down. This affects LatexQC, journal submissions, gallery publishing

Conversions/Submissions were down between 6-10.45am UTC. The issue should be resolved, and the team is continuing to monitor the system.

Incident is now resolved

Our Github integration is currently facing issues. We are investigating, but the issue is likely due to the ongoing service degradations at Github. See https://www.githubstatus.com for more information.

We confirm that the unreliable behaviour of the Github sync integration is due to the ongoing Github outage. Due to the currently unreliable behaviour of Github's API, we recommend not trying to link/unlink repositories or performing any Github related operations via Overleaf until the incident is resolved.

Github outage is now resolved. Github sync integration is operating normally.

We are aware of issues with access to our AI features and are currently investigating.

The issue has been identified and a fix is being implemented.

A fix has been implemented, we're monitoring the results.

We are continuing to monitor for any further issues.

This incident has been resolved.

Some users may currently encounter issues while trying to accept invitations to join projects. Our teams are currently investigating.

Project invitations are now working again. Incident is now resolved.

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

We are still investigating the issue.

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

The incident is now resolved.

We are currently investigating a technical issue that is blocking the synchronization of projects between Dropbox and Overleaf.

We have identified the root cause and are working on restoring the synchronization.

Synchronization of projects from Dropbox to Overleaf is working again.

Incident is now resolved.

We are aware of issues accessing Overleaf, including difficulty logging in, and we are currently investigating.

A fix has been implemented and we are monitoring the status of the site.

This issue is now resolved. Thanks for your patience.

We are currently experiencing an issue. Changes in Dropbox don't get reflected in Overleaf

Dropbox synchronizations are working again.

This incident has been resolved.

A technical incident is affecting multiple systems. Users may not be able to log in. Our engineers are currently investigating the issue.

A technical incident is affecting multiple systems. Our engineers have identified the issue. There may be some users unable to log in.

The incident is now resolved. We apologise for any inconvenience.

Some submissions to publishers are failing to upload. The team is investigating.

A fix has been implemented are we are monitoring the results.

This incident has been resolved. All failed submissions should now have been processed, but please contact our support team if you have any questions.

We are aware of issues with access to our AI features and are currently investigating.

AI features are now functioning properly. We apologise for any inconvenience.

Overleaf is experiencing issues with one of our service providers. We apologize for any inconvenience and have identified the source of the issue.

GitHub sync is now functional. We're monitoring to ensure the issue does not reappear.

This incident has been resolved. We apologise for any inconvenience.

Git Bridge was unavailable between 1715 UTC and 1750 UTC. We have updated the service and are monitoring its performance. We apologise for any inconvenience.

Git Bridge was unavailable this morning. We have updated the service and are monitoring its performance.

The issue has been fixed. We apologise for any inconvenience.

Due to an incident at one of our providers, Overleaf is currently unable to receive or respond to customer support inquiries via email or our contact page.

Service has been restored by our providers, and we are now able to receive and respond to support inquiries via email or our contact page.

We are investigating an issue preventing the Writefull AI features from loading.

A fix has been implemented and we are continuing to monitor.

The issue has been fixed. We apologize for any inconvenience caused.

Users are reporting that projects using certain packages, including svg and minted, are unable to compile.

We have deployed a fix and are seeing the compilations recover. If you are still seeing errors, try the "Recompile from scratch" option in the dropdown next to the "Recompile" button.

The compilation metrics have returned to normal levels, and users are reporting that the fix has worked. If you are still seeing errors, try the "Recompile from scratch" option in the dropdown next to the "Recompile" button.