Some of our clients are still having issues accessing Gemini. We have a solution: We offer different routing to reach Google on servers s1, s2, and s3 (each one of these offers a unique path). s4, s5 and s801 are a separate group which also offers a different path but it is the same for all 3 (s4, s5, s801). Please try s1, s2, s3 and one of ... Ler Mais »
Today we have rolled out another big fix for Gemini.
Google is cracking down on VPN providers. We've been working around the clock to find ways to restore Gemini for our clients. We have just rolled out a major update to our network which should address all Gemini-related issues. This update applies to all plans/continents.
If your IPLC service stopped working, please see this article for a solution:
https://justmysocks.net/members/knowledgebase.php?action=displayarticle&id=16
We have developed a workaround aimed at the recent update to the Google location detection.
A fix has been deployed which should resolve this issue.
We have completed a series of upgrades at our Amsterdam location.
s5 servers on LA plan should have a lot better performance, especially during peak hours.
Today we are migrating the HK IPLC circuit to support China Telecom and China Unicom direct connection.
Originally, this change was planned to be performed without causing any service interruption. However, during the implementation, we have encountered a disruption.
UPDATE: New IPLC circuit is online.
We have successfully deployed a number of network upgrades and countermeasures to our servers. We are observing a significant reduction in interference, as well as increased network performance. If you are using an old v2ray client (released before 2022), we recommend updating it to avoid detection. On our side, we have added a specific ... Ler Mais »
We have been informed of a fiber cut which is affecting IPLC services in Hong Kong. ETR is pending.
Update: We will reroute the affected segment. An engineer has been diapatched.
Update: Fiber cut has been fixed. IPLC service is fully operational now.
Our partner in Amsterdam has completed the migration and we have restored the location of s5 nodes.
Our upstream provider in Amsterdam is migrating to a different datacenter, which resulted in a prolonged outage today. We have temporarily migrated s5 servers to Los Angeles and will migrate them back to Amsterdam as soon as the datacenter is back online.
