same issue

same here. its getting very annoying

引用自 MinerSun0803：

Hi, let me explain what's happening. When I'm connected to my home network, I always encounter the following issue whenever I try to view my inventory or queue for the Steam Market:

"Sorry! An error was encountered while processing your request: You've made too many requests recently. Please wait and try your request again later."

I don't know why this keeps happening. It started after I bought Don't Starve Together (I've already returned the game), but the problem persists. I'm the only one in my household who uses Steam, and my PC doesn't have any VPN, mining software, or suspicious code that could be causing this.

Interestingly, when I connect through a different network—like my mobile data—this issue doesn't occur. So I'm wondering if anyone knows a solution to this problem.

You hit an API quota limit. This quota limit is IPv4 based. If restarting your router doesn't help, you'll have to wait it out.

IPv4 addresses are not unique anymore. As there are more humans (8 billion) than IPv4 addresses (4.2 billion), ISPs have chosen to route users together on an identical IPv4 address. This technique is known as CGNAT.[en.wikipedia.org]

For Valve's inventory and community market API this bundled together group of users using CGNAT or Dual Stack Lite looks like a single user.

If you waited several days to weeks, your only recourse is getting a public IPv4 address. It doesn't matter whether this one is static or dynamic. Ask your ISP on how to obtain one.

If you are behind Dual Stack Lite (shared IPv4 address, dedicated IPv6 prefix), temporarily disable IPv4 on your system after you made sure IPv6 support is enabled in your router to force Steam to use IPv6. Undo this step after you finished using the market or inventory (you will have to redo it every time you use either). Do not use this as a permanent solution because not every service on the internet did implement IPv6 support yet.

If you already have a public also known as dedicated IPv4 address, you should stop spamming inventory actions.