Profile rendering 502/503 timeout due to high contribution volume (~14k)

[dogi]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Profile

Body

Description

Loading my default profile URL consistently throws HTTP 502 (Bad Gateway) and 503 (Service Unavailable) errors from the backend. This appears to be a server-side rendering timeout caused by a massive contribution payload (nearly 14,000 contributions in the rolling 12-month window).

Reproduction Steps

Navigate to the default GitHub profile URL: https://github.com/dogi
Observe the page failing to load with the message "Something went wrong, please refresh the page to try again." and throwing 502/503 errors in the browser developer console.
Navigate to a date-filtered URL that restricts the contribution payload size, such as: https://github.com/dogi?tab=overview&from=2026-07-01&to=2026-07-17
Observe that the profile page loads successfully when the payload is reduced (down to ~8,000 contributions for 2026).

Fault Type - Permanent - Occurring repeatably
Blocking? - no -ish
Last working date - 16 July

Logs

Developer Console Output:

❌ Failed to load resource: the server responded with a status of 503 ()
URL: https://collector.github.com/github/collect
❌ Failed to load resource: the server responded with a status of 503 ()
URL: https://collector.github.com/github/collect
❌ Failed to load resource: the server responded with a status of 502 ()
URL: https://github.com/dogi?action=show&...

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[xusnitdinov]

Really clean writeup, the date-filtered URL comparison basically nails the root cause: the overview render is timing out while trying to build the full contribution payload for the rolling 12-month window, and once you shrink that window it renders fine. So this looks like a server-side rendering timeout that scales with contribution count, not something wrong on your end.

One thing worth flagging: this discussions board is mostly community + product feedback, so backend timeouts tied to a specific account like this usually need GitHub Support to actually look at the render path and logs. I'd open a ticket at https://support.github.com/ and link this discussion plus the two screenshots. The "works with a smaller date range, 502/503 with the full range" detail is exactly the kind of repro they can act on.

In the meantime the date-filtered URL you found is a decent stopgap for anyone hitting your profile who needs it to load.

Out of curiosity, is it consistently 502/503 every time, or intermittent under load? That distinction (hard timeout vs occasional) is useful to include in the ticket too.

[dogi]

@xusnitdinov it looks to me it is a hard timeout ...

[dogi]

also to https://support.github.com/ I even created 2 ... both of them got immediately autoclosed ...
the first one I opened in the wrong category (repository) so I understand
but the second one in https://support.github.com/contact/bug-report which is the right spot got also closed the moment I opened it -> that put me totally off
both autoclose messages pointed me to create a message here in github discussions
so here we are

[xusnitdinov]

Thanks for confirming, @dogi. Hard timeout every load is a useful data point for whoever eventually looks at this.

Also wow, that support loop is rough. If both tickets got autoclosed and pointed you back to Discussions, then this thread is basically the only path left for now. At least the repro is solid: full overview 502/503, smaller from/to window loads fine, and @ljodea is seeing the same thing around 22k contributions. So it is not a one-off account glitch.

Hopefully a GitHub staffer picks this up from the Product Feedback catalog note above. Until then the date-filtered URL is still the best workaround for people who need the profile to load.

[ljodea]

having the same issue with ~22k+ contributions over the past 12 months

[dogi]

github.com (aka dashboard) also breaks when logged in ...

[dogi]

looks like it got fixed
thank you github <3

PS: @ljodea you should try ... 804 points on one day is impressive