503s on GitLab.com

Timeline

1. 25 Sep · 04:37 UTC ⚪ Investigating rss

   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

2. 25 Sep · 03:36 UTC ⚪ Investigating rss

   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

3. 25 Sep · 02:34 UTC ⚪ Investigating rss

   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

4. 25 Sep · 02:03 UTC ⚪ Investigating rss

   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

5. 25 Sep · 01:43 UTC ⚪ Investigating rss

   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

6. 25 Sep · 01:02 UTC ⚪ Investigating rss

   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.

7. 25 Sep · 00:41 UTC ⚪ Investigating rss

   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.

8. 25 Sep · 00:31 UTC ⚪ Investigating rss

   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.

9. 25 Sep · 00:19 UTC ⚪ Investigating rss

   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.

10. 25 Sep · 00:01 UTC ⚪ Investigating rss

    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.

11. 24 Sep · 23:44 UTC ⚪ Investigating rss

    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.

12. 24 Sep · 23:39 UTC ⚪ Investigating rss

    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.

13. 24 Sep · 23:27 UTC ⚪ Investigating rss

    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.

14. 24 Sep · 23:04 UTC ⚪ Investigating rss

    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.

15. 24 Sep · 23:02 UTC ⚪ Investigating rss

    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.