Skip to content

[Down Time] Card throws 'maximum retries exceeded' error #1471

Open

Description

@anuraghazra

Hi everyone, I see that all personal access tokens are currently failing, thus you will see the "Maximum retries exceeded" error.

I'm looking into the issue to figure out what caused it.

Ideally, it should be fixed in an hour when the PATs get rest.

Details

Public instance information

Custom badge

Explanation


Hey everyone, sorry for the recent downtimes.

For the sake of transparency, we get a huge amount of requests per month (it's kind of mind boggling for a side project which I built just for fun). Here's the vercel dashboard statistics:

image

As you can see even with 73% of the responses being cached by vercel the amount of live requests are huge, and the bottleneck here is Personal Access Tokens

Each PAT have 5000 points, and based on the complexity of the GraphQL query & resource limitations set by GitHub, it's actually very very low considering that amount of requests.

To circumvent the issue, we currently have 7 PATs (thats 35k points) which sometimes get exhausted.
Thanks to @rickstaa we are going to add few more probably bumping it up to 10 or 12, hopefully that could help alleviate the downtimes.

Note: That these downtimes are temporary, and only lasts for 1hour, since PATs regenerate after 1 hour


So whats the idea way?

#1471 (comment)
Deploy on your own vercel instance. WHY?
It's easy to do, free & reliable.

  • It reduces loads on our vercel instance.
  • Your own PAT will give you more concrete stats including private stats
  • It ensures that there won't be any downtime on your profile stats because you are the only one who is gonna hit your URL

Originally posted by @anuraghazra in #2130 (comment)

Activity

  1. pinned this issue on Nov 24, 2021
  2. jincheng9 commented on Nov 25, 2021

    @jincheng9
  3. jincheng9 commented on Nov 25, 2021

    @jincheng9
  4. GabrielMendesdc commented on Nov 25, 2021

    @GabrielMendesdc
  5. Ari24-cb24 commented on Nov 25, 2021

    @Ari24-cb24
  6. devmohit-live commented on Nov 25, 2021

    @devmohit-live
  7. anuraghazra commented on Nov 25, 2021

    @anuraghazra
    OwnerAuthor

    Hi everyone.

    Sorry for the inconvenience.
    I will highly recommend deploying github-readme-stats on your own vercel instance to fix this issue, while I try to find a fix. Currently I'm unable to find any root cause.

    Consider deploying on your own fork. follow the guide -> https://github.com/anuraghazra/github-readme-stats#deploy-on-your-own-vercel-instance

    Youtube video tutorial: https://www.youtube.com/watch?v=n6d4KHSKqGk&feature=youtu.be&t=107

    Also after forking make sure to open vercel.json and change the maxDuration option to 10.

  8. GabrielMendesdc commented on Nov 25, 2021

    @GabrielMendesdc
  9. anuraghazra commented on Nov 25, 2021

    @anuraghazra
    OwnerAuthor

    Thanks a lot! mine is already bug fixed

    Yes, it's happening intermittently for some people, and for some it's not.

  10. elli0t43 commented on Nov 25, 2021

    @elli0t43
  11. elli0t43 commented on Nov 25, 2021

    @elli0t43
  12. anuraghazra commented on Nov 25, 2021

    @anuraghazra
    OwnerAuthor

    Added 4 new PATs, let's observe the downtime.
    For some reason the PATs are weirdly depleting super fast. not sure why.

    ALSO: Note that deploying on your own instance is ALWAYS a better option than relaying on ours

    1. It reduces loads on our vercel instance, we get almost 3-4Million requests per month which is hard to scale up.
    2. Your own PAT will give you more concrete stats including private stats
    3. It ensures that there won't be any downtime on your profile stats because you are the only one who is gonna hit your URL

    So please I enocurage everyone to deploy on their own instance,
    If you face any kind of issues while deployment I'm more than happy to help you out.

  13. Babu-Mohammed-Izhan commented on Nov 25, 2021

    @Babu-Mohammed-Izhan
  14. 189 remaining items

  15. added a commit that references this issue on Nov 30, 2025
  16. F18-Maverick commented on Dec 7, 2025

    @F18-Maverick

    Okay, thanks @pwbriggs and @qwerty541. I'll try it later!

  17. RedaArrous commented on Dec 23, 2025

    @RedaArrous

    how to deploy it?

  18. pwbriggs commented on Dec 24, 2025

    @pwbriggs

    Hey @RedaArrous! Check out the "Deploy on your own" section of this repo's readme. If something goes wrong while following those instructions, please search the issues to see if somebody's had your problem before, and if not, open a new issue with an error report. Issues with deploying your own instance are likely off-topic for this issue. Thanks!

  19. RedaArrous commented on Dec 24, 2025

    @RedaArrous

    @pwbriggs thanks for the polite response man .

  20. added a commit that references this issue on May 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ⭐ top issueTop issue.fixedIssue seems to be fixed for now.upstreamProblems caused by upstream issues.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions