[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](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)

Each PAT have 5000 points, and based on the complexity of the GraphQL query & [resource limitations](https://docs.github.com/en/graphql/overview/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_