Access Restricted - Possible Static Resource Rate Limiting Issue

[lubiebie]

Select Topic Area

General

GitHub Feature Area

Other

Body

I am experiencing an "Access Restricted - You have triggered a rate limit" issue when trying to access raw.githubusercontent.com and user-images.githubusercontent.com static resources.

Here are the details of my situation:

I have been using GitHub as an image hosting solution by setting up a personal repository. I integrated it with PicGo for automatic image uploading and used Obsidian to embed and view those images in my notes.
Recently, I suddenly found that I could no longer preview any images hosted on GitHub. The issue occurs both inside Obsidian and directly when browsing the repository through GitHub's web interface.
I can still access github.com normally and upload new images to my repository without problems.
However, static resource URLs (e.g., raw.githubusercontent.com links) cannot be loaded and show the "Access Restricted" rate limit error.
I have already cleared the local DNS cache, flushed browser cookies, changed my network IP (using both a mobile hotspot and VPN), and used incognito mode to eliminate possible local issues. The problem persists across different IP addresses and sessions.
My question is:

Is my IP address or account currently restricted?
Is there an approximate timeframe for automatic lifting of this rate limit? I have been waiting for one day and nothing has changed.

Are there any further actions I can take to resolve this issue?
Thank you very much for your help!!!!!!!

[UjuiUjuMandan]

• Access Restricted - Possible Static Resource Rate Limiting Issue #157851

[ArshAliAzam]

Thanks for the detailed explanation — you're clearly doing all the right things to troubleshoot. Based on your description, you're encountering a rate limit imposed by GitHub's CDN (e.g., raw.githubusercontent.com, user-images.githubusercontent.com), not GitHub.com itself. Here's how to address it:

🔍 1. Root Cause: Rate Limiting on CDN Access
GitHub CDN endpoints like raw.githubusercontent.com and user-images.githubusercontent.com are more aggressively rate-limited than GitHub's main domain. These limits are often IP-based, not account-based, and they can be triggered by tools like PicGo or Obsidian polling too frequently.

✅ 2. What You’ve Tried (and Did Right)
You’ve done a thorough job already:

Flushing DNS & cookies ✅

Trying VPNs & alternate IPs ✅

Using incognito/private sessions ✅

Verifying image uploads still succeed ✅

But since uploads still work and only static CDN access fails, this strongly suggests an IP-based temporary restriction.

⏳ 3. How Long Do These Limits Last?
GitHub doesn't publish exact timeframes, but:

Soft rate limits (like for CDN access) usually reset within 1–3 days.

If you’re still blocked after 72 hours, something stronger may be in effect, or your IP range could be flagged more permanently.

🛠 4. Additional Steps You Can Try
Here are some focused actions you can take:

A. Switch DNS Providers
Sometimes DNS resolution via certain providers (e.g., local ISP DNS or overloaded public DNS) can trigger issues:

Try using Cloudflare DNS (1.1.1.1) or Google DNS (8.8.8.8)

B. Use a Residential VPN or Proxy
Many CDN protections block:

Data center IPs

VPNs

Hosting providers (AWS, etc.)

Try a VPN provider with rotating residential IPs, like:

Windscribe (with residential routing enabled)

Proxies like Bright Data or Smartproxy (for developers)

C. Check with GitHub Support
You can open a ticket with GitHub here:
👉 https://support.github.com/contact

Include:

Your IP address

The exact URLs that are failing

A mention that you use PicGo/Obsidian for image delivery

They can clarify if the block is automated or manual.

🧼 5. Future-Proofing
To avoid future rate-limiting:

Use a GitHub Pages site to serve images (via a .md or .html wrapper) rather than hotlinking raw CDN links.

Limit PicGo's retry/upload frequency or use a timed delay between uploads.

Consider moving to a purpose-built image host (e.g., Cloudinary, Imgur API, or self-hosted S3 bucket).

[shinybrightstar]

Hi @lubiebie,

The GitHub Community on Discussions is a space for all GitHub users to come and discuss ideas and projects. Your post was closed and locked because it violates our Community Code of Conduct, such as posting the same comment in multiple places. We encourage you to use our search bar before posting to find if a similar discussion exists so we don't overwhelm the community with duplicate discussions, and we ask that you no longer cross-post.

For additional guidance, please review our Community on Discussions Code of Conduct and GitHub’s Terms of Service.

Thanks for understanding!