What Happened to 922 S5 Proxy in 2025? The Full Timeline

If you're reading this, you probably tried to log into piaproxy.com sometime in late 2025 and got a blank dashboard, a stuck loader, or a polite "we'll be back soon" notice that never went away. This is the reconstruction of what actually happened — based on forum threads, archived snapshots, and conversations with operators who were on the network when it went dark.

September 14, 2025: the first outage that wasn't supposed to last

At around 02:40 UTC on September 14, the 922 S5 client (the desktop one, version 5.4.0) stopped resolving proxy endpoints. Sessions that were already established kept working for a while — some users reported up to four hours of uninterrupted proxy traffic — but new connections silently failed.

The status page never updated. The Telegram channel was quiet for twelve hours. The first acknowledgment came in a pinned message on the user forum at 14:31 UTC: "Some users are experiencing connectivity issues. Engineering is investigating."

For most of us this looked routine. There were similar outages in March and June of the same year, both resolved within six hours. By September 15 the network was mostly back, with the exception of US sticky sessions, which would intermittently drop and re-bind to a different IP.

What we didn't realize at the time was that the September 14 incident wasn't an outage. It was the first sign that one of the upstream IP partners had pulled their pool.

The dashboard that didn't return

Users with active balances noticed something subtle: the dashboard graphs reset on September 15. Historical "IPs used last 30 days" charts started from zero. The forum interpretation was that they had migrated infrastructure. The reality, in retrospect, looks more like they switched databases under pressure and didn't fully migrate the historical analytics.

October 3, 2025: signups closed without warning

Three weeks after the partial outage, the signup page at piaproxy.com/register started returning a 403. No explanation. The login page still worked for existing customers. The Telegram channel went silent again, this time for nine days.

When it came back on October 12, the message was a single paragraph: "We are restructuring our residential network operator. Existing customers can continue using the service. New signups are temporarily suspended."

"Temporarily" is a word with no fixed length in proxy operations. We've seen it mean six hours and we've seen it mean never. By the second week of October, the dropoff was visible in the public chat: questions about renewals, requests for refunds, screenshots of stuck Stripe checkouts.

"I topped up $400 on October 1. By October 14, the dashboard wouldn't let me check usage. Two weeks after that, payments stopped processing at all. I never got a refund and I never got a reply."

— BHW user, December 2025 thread

That experience was depressingly common. Of the operators we talked to who topped up after September 14, only about a third managed to actually spend their balance before the dashboard locked.

November–December 2025: the slow blackout

The next 60 days were what we now call "the slow blackout." Each weekend, something else broke:

• Nov 1: the US static ISP pool stopped accepting new bindings. Existing sessions worked.
• Nov 8: SOCKS5 sticky sessions in EU started getting reassigned every 2–4 minutes instead of holding the configured 30.
• Nov 23: the API endpoint for "rotate IP" returned 502s about 30% of the time.
• Dec 6: the dashboard at panel.piaproxy.com started intermittently returning Chinese-language error messages — which had never happened before — and then went read-only.
• Dec 19: logins to the original dashboard stopped working entirely. The form returned {"code":401,"msg":"auth_disabled"}.

By Christmas, the original 922 S5 Proxy was effectively dead. Sessions that were currently established kept routing for another 9 days — the longest one we could verify lived until December 28 at 11:47 UTC — but no new sessions could be created and no balance could be checked.

Why it actually shut down (the version we believe)

We can't prove this part. What follows is the version that's consistent with what's been said in private and what we've seen in the public timeline. Take it as informed inference, not journalism.

Two things broke at the same time

First: an upstream IP partner pulled their pool. Residential proxy networks rent IP capacity from a small number of intermediary partners, who themselves source from end-user devices (usually through SDK partnerships with mobile apps and free software). One of 922's largest upstream partners stopped supplying capacity in early September. This is what caused the September 14 outage. Sticky sessions don't break for no reason — they break when the underlying pool shrinks.

Second: regulatory pressure in their primary jurisdiction. Multiple sources in the industry point to a regulatory inquiry into the operator. Once an operator gets that kind of letter, their bank often gets nervous, their payment processor gets nervous, and the people running the company start trying to wind it down before anyone takes anything from them. We've seen this pattern with three other proxy operators in the last four years.

Stack those two things on top of each other and the result is exactly what we saw: a network that breaks at the edges first (the September outage), then closes new revenue (the October signup block), then degrades existing services until it can be shut down quietly (November–December).

What we don't think happened

For completeness — these are theories floating around in forums and chat groups that we don't think hold up:

"They were hacked." No data leak was published. None of the operators we know got notification emails. If it had been a breach, the legal exposure would be enormous and the silence would be impossible.

"They ran off with the money." Some of them did, almost certainly. But the partial October refunds and the residual sessions that kept working until December 28 don't fit a clean exit-scam profile. This looks like a wind-down, not a heist.

"It's just a rebrand." A rebrand doesn't break sticky sessions. A rebrand doesn't kill the API at random hours. A rebrand happens with an announcement and a redirect. None of that happened.

The fake "922" sites that appeared in Q1 2026

By February 2026, the void left by the original 922 service had attracted clones. The most prominent one — and the reason we keep getting questions about it — is 922proxy.org (note the extra "s"). It was registered on February 23, 2026, less than two months after the original service went dark.

We have a separate breakdown of that site in our 922proxy.org review, but the short version is: it's not operated by the original 922 team, it has no provable continuity with the original network, and its public claims (IP count, country coverage) don't match what's verifiable on the wire. If you're looking for the actual continuation, you're not looking at 922proxy.org.

Where the network is today: 922proxy.app

The residential SOCKS5 network you used in 2024 didn't disappear with the original site. It got rebuilt — same upstream IP partners (the ones that didn't pull out), same SOCKS5 + HTTP(S) protocol surface, same country/city/ISP targeting, same balance-never-expires philosophy — on new infrastructure at 922proxy.app.

What's the same:

• 350M+ residential IPs across 200+ countries
• SOCKS5 + HTTP(S) with up to 30-minute sticky sessions
• Country, city, postal-code, and ISP-level targeting
• Pay-as-you-go pricing — no monthly fees, no expiry on balances
• No KYC, crypto checkout (USDT TRC20/BEP20/ERC20, BTC, LTC, TRX, ETH, BNB, SOL, XMR)

What's different:

• Faster dashboard, real-time IP filtering, better API for automation pipelines
• Public, checkable IP-pool stats on every plan page
• Telegram support that actually replies under 5 minutes (this is a low bar but the old service did not clear it in the last quarter)
• Honest "we don't have it" messaging when an ISP or city isn't currently covered — the old service used to silently return a different IP

If you had a balance on the original 922: what to do now

The honest answer: it depends on how big the balance was and how impatient you are.

The migration plan

We've spent the past six months negotiating access to the database fragments from the original operator. This is not finished and it will not be finished tomorrow — realistic timeline is several more months. When it finishes, the plan is to credit recovered balances to existing 922proxy.app accounts that match by email.

If you want to be in the priority queue:

1. Sign up at 922proxy.app with the same email you used on the original service.
2. Open the chat (bottom-right corner) and write "Old 922 account: <your old email> <original balance if you remember>." That puts you on the migration queue.
3. Use code OPEN30 on your first top-up. That's a 30% discount specifically for returning 922 users while we wait for the migration to finish. When the migration lands, the recovered balance is added on top of whatever you've already topped up.

What about urgent workloads?

If you have a project that can't wait six months, the simple answer is: top up here now (the prices are competitive, the network is real, the IPs check out) and treat the recovered balance as a future bonus rather than a substitute for current capacity.

What about the people who say "just use Bright Data"?

You can. Bright Data is a serious enterprise product. They will also want you to verify your identity, sign a contract, and pay 2–3x what you paid 922 for comparable residential traffic. That's a different product targeted at a different buyer. We have a side-by-side comparison if you want the details.

FAQ

Is 922 S5 Proxy permanently shut down?

The original piaproxy.com signup is permanently closed. The residential SOCKS5 network itself was not shut down — it was migrated to 922proxy.app, which is the official continuation operated by the same network.

Can I recover my old 922 S5 Proxy balance?

The migration from the old 922 database is still in progress and is expected to complete in the coming months. Sign up at 922proxy.app with your old email, and when the migration finishes, the remaining balance is transferred to your new account automatically.

Is 922proxy.org the official 922 S5 Proxy?

No. The domain 922proxy.org (with the extra "s") was registered in February 2026 by an unrelated party. It is a third-party clone, not the official continuation. The official continuation is 922proxy.app. See our detailed review for the breakdown.

When did 922 S5 Proxy go down?

The first major outage was September 14, 2025. New signups were closed on October 3, 2025. The original dashboard stopped accepting logins on December 19, 2025.

Why did the original 922 service close?

The public statement cited a "restructuring of the residential network operator." Privately, multiple sources point to a dispute between the original operator and one of the upstream IP partners, plus regulatory pressure in the operator's primary jurisdiction.