503s on GitLab.com

September 24, 2026 23:02 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:04 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:27 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We will update with more details shortly. September 24, 2026 23:39 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly. September 24, 2026 23:44 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.

September 24, 2026 23:02 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:04 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:27 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We will update with more details shortly. September 24, 2026 23:39 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly. September 24, 2026 23:44 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:01 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly.

September 24, 2026 23:02 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:04 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:27 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We will update with more details shortly. September 24, 2026 23:39 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly. September 24, 2026 23:44 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:01 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:19 UTC Identified - Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly.

September 24, 2026 23:02 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:04 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:27 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We will update with more details shortly. September 24, 2026 23:39 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly. September 24, 2026 23:44 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:01 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:19 UTC Identified - Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly. September 25, 2026 00:31 UTC Identified - Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly.

September 24, 2026 23:02 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:04 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:27 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We will update with more details shortly. September 24, 2026 23:39 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly. September 24, 2026 23:44 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:01 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:19 UTC Identified - Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly. September 25, 2026 00:31 UTC Identified - Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly. September 25, 2026 00:41 UTC Identified - Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon. September 25, 2026 01:02 UTC Identified - Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon.

September 24, 2026 23:02 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:04 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:27 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We will update with more details shortly. September 24, 2026 23:39 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly. September 24, 2026 23:44 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:01 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:19 UTC Identified - Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly. September 25, 2026 00:31 UTC Identified - Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly. September 25, 2026 00:41 UTC Identified - Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon. September 25, 2026 01:02 UTC Identified - Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon. September 25, 2026 01:43 UTC Identified - GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts.

September 24, 2026 23:02 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:04 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:27 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We will update with more details shortly. September 24, 2026 23:39 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly. September 24, 2026 23:44 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:01 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:19 UTC Identified - Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly. September 25, 2026 00:31 UTC Identified - Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly. September 25, 2026 00:41 UTC Identified - Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon. September 25, 2026 01:02 UTC Identified - Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon. September 25, 2026 01:43 UTC Identified - GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts. September 25, 2026 02:03 UTC Monitoring - GitLab services are now operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.

September 24, 2026 23:02 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:04 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:27 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We will update with more details shortly. September 24, 2026 23:39 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly. September 24, 2026 23:44 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:01 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:19 UTC Identified - Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly. September 25, 2026 00:31 UTC Identified - Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly. September 25, 2026 00:41 UTC Identified - Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon. September 25, 2026 01:02 UTC Identified - Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon. September 25, 2026 01:43 UTC Identified - GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts. September 25, 2026 02:03 UTC Monitoring - GitLab services are now operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window. September 25, 2026 02:34 UTC Monitoring - GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.

September 24, 2026 23:02 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:04 UTC Investigating - We are recieving reports of 503 errors on GitLab.com. This is under active investigation. We will update with more details shortly. September 24, 2026 23:27 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We will update with more details shortly. September 24, 2026 23:39 UTC Identified - We've identified the cause of 503 errors on GitLab.com and are working on mitigating the issue. We're aware that the API is also affected. We will update with more details shortly. September 24, 2026 23:44 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:01 UTC Identified - We are seeing some recovery based on our mitigation efforts, which are ongoing. We will update with more details shortly. September 25, 2026 00:19 UTC Identified - Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly. September 25, 2026 00:31 UTC Identified - Error rate is decreasing after active mitigation efforts. We're still actively working on addressing the root cause. We will update with more details shortly. September 25, 2026 00:41 UTC Identified - Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon. September 25, 2026 01:02 UTC Identified - Error rates are decreasing, but some customers may still see errors. We are continuing to address the remaining impact and will update again soon. September 25, 2026 01:43 UTC Identified - GitLab remains stable and error rates have decreased. We are still actively engaging in recovery efforts. September 25, 2026 02:03 UTC Monitoring - GitLab services are now operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window. September 25, 2026 02:34 UTC Monitoring - GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window. September 25, 2026 03:36 UTC Monitoring - GitLab services are operational and we're continuing to monitor the situation. We are assessing any outstanding impacts during the disruption window.

503s on GitLab.com resolved