Khabarovsk node is dead again

Technical Support
1

Khabarovsk node seems to be dead again. I know it is difficult to keep it alive but will it come back?

2

not again :smiling_face_with_tear:

3

Hi Eniff, thank you for your feedback. Yes, the Khabarovsk node is currently down, and unfortunately, we aren’t sure when it will be back.

The server itself is still running, but due to severe censorship by the Russian government, SSH access is blocked and it cannot communicate with our central servers. Because of this, we are seriously considering removing the node entirely.

We apologize for the inconvenience and appreciate your understanding.

1 Like
4

Hi weongyo!

Please don’t remove it!
It is the only node that gives me playable latency.
I can imagine how hard it might be with the hostile attitude you receive from governments, but this node is invaluable.

5

What Eniff said, please don’t remove it, it’s my saving grace :face_holding_back_tears: :folded_hands:
Also the node is back as of this reply, question is for how long.
edit. it lasted for 5 minutes :')

6

RU Europe (Khabarovsk - Misaka) should be back right now. Please test it when you get a chance.

1 Like
7

it is back as of now, yes. Hopefully it doesn’t die again

8

Thanks for confirming that RU Europe (Khabarovsk - Misaka) is working again! We understand how important this node is for your latency, and we’re sorry for the repeated interruptions. If it drops again, please reply here with the time and time zone, and let us know whether the node disappears from the list or remains listed but cannot connect.

2 Likes
9

Hello weongyo, I am new here, so there might be an issue with my settings, but it seems that RU Europe (Khabarovsk - Misaka) is not working again. The current time is 21:35 JST. The node is still listed, but it shows 100% packet loss. I would appreciate it if you could check whether the node can be fixed, or advise me on how to change my settings if the problem is on my side.

10

@0pt1m12m Hello! Thanks for reporting. The 100% packet loss is likely due to the ongoing censorship blocks on the RU Europe (Khabarovsk - Misaka) node, not your settings.

Could you test the node by following How to check the basic functionality and let me know if you get a proper result?

We’ll keep investigating. Thanks for your patience!

1 Like
11

Hello! I tried following the steps in your post, but it seems like it’s not working. When I try to access https://myip.mudfish.net, the connection times out instead of showing the confirmation message.

12

@0pt1m12m Thanks for testing. Sorry it still fails. Please repeat the basic test with a Tokyo node: enable Full VPN, save and restart Mudfish, then visit https://myip.mudfish.net. Turn Full VPN off afterward.

If Tokyo works, this points to the Khabarovsk node or its route. Please share the result. If Tokyo also fails, send warnings/errors from Status → Process, hiding personal details.

13

Hi! Yeah, the Tokyo node works, but I was hoping to use the Khabarovsk node to get lower ping in Squad. :disappointed_face:

14

Thanks for testing, and sorry for the disruption. Tokyo working points to an issue with the Khabarovsk node or its route. We have no confirmed recovery time yet.

For now, please use a working node. To help find a lower-ping route for Squad, please share the server name and region from the server browser, plus your in-game ping on that same server with Mudfish off and via Tokyo. Please turn Full VPN off after testing.

15

For me it’s working through Khabarovsk. They banned more destinations but some are still working.

16

Thanks for the update, Eniff! Glad to hear the Khabarovsk node is working for you again. Please keep using this working route for now.

From what I can tell, it seems the Russian ISP or government policies are blocking specific IP ranges while allowing others. This likely explains why the node works for some users but remains inaccessible for others.

Let us know if you experience any further issues!

17

Thanks for the response. Since I’m connecting from Tokyo, I understand that using a Tokyo relay does not necessarily guarantee a better route.

However, I’ve encountered several issues while testing Mudfish with Squad:

1. Ping and routing

  • Without Mudfish, my connection to the Russian Squad server (195.18.27.172) works normally, with a ping of approximately 250–270 ms.
  • Through several Tokyo nodes, my ping remains around 270 ms, with no meaningful improvement.
  • I tried different connection modes, including TCP and UDP, but switching modes did not resolve the issue.
  • For comparison, ExitLag reduces my ping to approximately 124–150 ms.

2. Squad queue disconnections
When Mudfish is enabled, I get disconnected from the Squad queue with a Disconnected from queue error. The queue works normally when Mudfish is disabled. I encountered this issue with Tokyo nodes and also tested Full VPN, but it did not resolve the problem.

3. Khabarovsk node issues

  • The Khabarovsk–Misaka node showed 100% packet loss during my tests.
  • Accessing myip.mudfish.net through this node resulted in a timeout.
  • I understand that there is currently no confirmed recovery time for this node.

4. Mudfish item configuration
The default Squad item did not appear to capture the game’s traffic correctly, and the realtime traffic remained at zero. I eventually identified the actual game process (SquadGame-Win64-Shipping.exe ) and manually created a custom Mudfish item. After that, Mudfish started capturing the game’s traffic.

Could you help me investigate why Mudfish’s Tokyo routes do not provide a lower ping comparable to ExitLag, and why Squad disconnects from the queue when Mudfish is enabled? Are there any alternative nodes or routing configurations I should try from Japan?

I’ll retest the server with Mudfish disabled and through a Tokyo node, with Full VPN turned off, and share the exact ping values.

Thanks for your help!

18

@0pt1m12m Thanks for testing, and sorry for the trouble. Tokyo nodes may still take a longer route than ExitLag.

With Full VPN off, try Advanced mode in your custom item’s settings and compare full-route RTTs via the magnifier. Avoid Khabarovsk while it times out. Restart Mudfish and Squad after changes.

Since Full VPN also fails, missing item routes alone may not explain the queue error. Please reproduce it, then send a Problem Report with node names, time/time zone, custom-item settings and your ping comparisons.

19

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.