⚠️ OKAC Shutdown Risk Alert—July 1, 2026
As of July 1, 2026, users had repeatedly reported route failures, inaccessible websites, and interrupted customer-support and management responses at OKAC. Because OKAC shares an operator with Naiyun, whose shutdown has been confirmed, this site currently classifies OKAC as a provider shutdown risk.
Shutdown risk alert: Existing users should immediately stop renewing or adding account credit. Preserve screenshots of payment records, support tickets, conversations, and subscription status first.
Risk-monitoring board
Many proxy services have recently become unreachable after data centers removed their servers. Consult the 2025–2026 Proxy-Service Shutdown and Risk List for additional records.
Latest OKAC shutdown-risk update (July 1, 2026)
Websites reported during the incident included www.okanc.com, https://www.okads.top/, and https://aff.okads.cc/; users reported that none of them could be accessed normally. From mid-May through late June, the group continued to receive reports of nodes showing errors, unstable connections, and connections that appeared successful but were unusable.
An important connection is that OKAC, Naiyun, CAC, and Yinyun share the same operator. Naiyun's shutdown has been confirmed. OKAC's problems should therefore not be evaluated as an isolated website failure; the availability and communication status of CAC and Yinyun during the same period also matter.
Evidence limitations
The assessment below is compiled from available user reports and screenshots. Some details still require verification.
Until the platform provides a verifiable announcement and restores stable service, treat it as high risk.
Analysis of OKAC's shutdown risk
Caution
OKAC has developed a combination of prolonged route failures, website-access problems, and interrupted management responses.
Stop renewing or purchasing immediately to avoid further losses.
OKAC websites: Users reported that www.okanc.com, https://www.okads.top/, and https://aff.okads.cc/ were all inaccessible.
- Website status: None of the reported domains—
www.okanc.com,https://www.okads.top/, orhttps://aff.okads.cc/—could be accessed normally during the incident. Whether a temporary replacement domain exists remains unverified. - Support status: Records show some conversations about restoring orders after mid-May, but replies later slowed significantly and then stopped. The exact time when support became fully unreachable remains unverified.
- Management status: No new, substantive recovery notice or follow-up explanation was seen after June 14.
- User reports: From mid-May through late June, users repeatedly reported nodes showing errors, unstable connections, and connections that succeeded but remained unusable.
- Operator connection: OKAC, Naiyun, CAC, and Yinyun share the same operator. Naiyun's confirmed shutdown increases the risk of correlated service and financial problems among the related projects.
May 11–13, 2026: recurring A-route and broader multi-route failures
On May 11, Telegram-group users reported that the A route had failed and only the B route remained usable. Management replied that day that the problem had been fixed. On May 13, however, the group again received reports of failures on the A route and on multiple routes, indicating that service had not been restored reliably.


May 17, 2026: data loss, order-restoration discussions, and website problems
On May 17, management issued a notice about “data loss” and said that users could contact support to have orders restored. Users reported website-access problems during the same period. For a paid proxy service, data loss combined with an inaccessible website is itself a serious operational risk.


Late May to mid-June 2026: repeated node errors and unusable connections
From late May through mid-June, users continued to report nodes showing errors, failed connections, increased latency, and connections that appeared successful but could not carry traffic. The disruption had already lasted longer than ordinary short-term maintenance.




June 12–14, 2026: management acknowledged interruption risk, then stopped providing meaningful updates
On June 12, management posted that “special circumstances” could interrupt service for three to five days and said a compensation plan would follow. No new, substantive recovery notice or explanation was seen after June 14, and communication noticeably weakened.


Mid-to-late June 2026: weaker ticket responses and concentrated reports of a complete outage
In mid-to-late June, users continued to report overlapping website and node failures, while ticket and communication responses weakened. By June 22, the group had concentrated reports of a complete outage and no effective response.



Conclusion
The available timeline and screenshots show the following high-risk characteristics:
- The A route failed repeatedly, while problems spread across multiple routes.
- Management acknowledged data loss and warned of a possible service interruption.
- The websites were inaccessible, and the existence of any temporary replacement domain remains unverified.
- OKAC shares an operator with Naiyun, whose shutdown has been confirmed, as well as with CAC and Yinyun; their risks should be evaluated together.
- In mid-to-late June, users reported a complete outage and ineffective communication.
- No visible, substantive recovery explanation was provided after June 14.
This site currently classifies OKAC as a provider shutdown risk.
There is not yet an explicit official closure notice or other evidence of an irreversible exit, so this page does not classify OKAC as a confirmed shutdown. The risk level may be raised if new evidence shows prolonged loss of contact, continued website unavailability, or funds that cannot be recovered.
Loss-mitigation advice for existing users
- Stop renewing and adding account credit immediately.
- Back up and export subscription URLs, plan details, payment records, support tickets, and chat records.
- If support or the ticket system still accepts requests, submit a written refund or explanation request and take screenshots of every step.
- Move promptly to an alternative service whose current operating status can be independently checked, so that a single-provider outage does not disrupt all access.
Submit a provider shutdown or risk alert
Other proxy-service options
Warning
Every proxy service carries a shutdown risk. Keep several pay-as-you-go backups and use monthly billing for your primary service to limit potential losses.