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

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

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:

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?

https://github.com/anuraghazra/github-readme-stats/issues/1471#issuecomment-979306704 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 https://github.com/anuraghazra/github-readme-stats/issues/2130#issuecomment-1270624232_

[anuraghazra]

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.

[anuraghazra]

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.