Hi @seripap @andy-maier. Apologies, we have not had time to get back to this community issue for further investigation.

Generally speaking in response to your issues:

They are not related to any site-wide incident or general issue that we are aware of, which explains the lack of an incident on our status page. Our best guess is that something about your specific requests is triggering a long-running back-end query that is resulting in the timeout.
Your reports have prompted us to perform a general investigation of slow back-end queries that seem to be the cause of these timeout issues for some customers, so the hope is we'll be able to reduce their occurrence asap.
We could now use further examples of specific requests of Repo and Build pages that are returning 504/502, as we are investigating those to understand what the contributing factors are and address them.

Specifically, for each of your individual cases:

@seripap, We have enough specific requests for you right now. I intended to get back to you earlier with an update that I did identify one of your original requests that showed a slow-running back-end query contributing to your 15s page load, which under other circumstances could easily have resulted in a timeout for you. I have not been able to perform an analysis to determine what the contributing factors might be in your case, but that is my next step when I'm able.
@andy-maier, any more detail you can provide on specific requests for Repo or Build pages that resulted in a Gateway Timeout would be helpful. The URL and the timing of the request are the most helpful details as we are searching for them in logs.
- That said, two key points:
  - The specific issue with requests for individual Source File Reports, like this one you mentioned, we are addressing as a different matter, under Gateway timeout (504) when viewing coverage changes of file #1757. We see that as more of an ongoing issue, which, given the different context---of the separate request to GitHub, the size of the source file, and other matters---is harder to predict and has a different resolution path.
  - But if you have specific requests for Repo Pages or Build Pages that are returning Gateway Timeouts, those would be the ideal requests to report here and we'd love to know the URLs and timing of any requests that return a 502/504. 🙏

Also, a P.S. @andy-maier:

I have been able to obtain a full report for this page (your original example) today without issue. Can you verify whether you can see it now as well? This, BTW, is the nature of the Source Files Page requests. They are sometimes intermittent, and, on a different day, resolve just fine. We think that, among the other factors, rolling maintenance at Cloudflare that adds hops to your main geographic access point may be a temporary factor that exacerbates the timeout issues for these pages.

Gateway timeouts #1799

Description