DC on DZ (Distorted Zone)

[Nimmienaticz]

I just wanna ask, why I keep DC-ing on DZ.
I'm using Fibr Connection with this Speed
Location: Manila, Philippines.



Every 2-3 runs on DZ, i get DC-ed in the first part of the DZ stage upon entering.
I don't have any 3rd party applications, downloads or updating stuffs.
I can somehow say, that my connection is really STABLE during the time I spammed DZ,
since I'm using it only on my Laptop & Phone.

Laptop Quick Spec:
Intel i3-4th Gen Quad Core
8gb RAM (6.35gb usable)
2gb VRAM
600gb+ HDD Free Space

It seems my laptop has no issues on specs, based on my quick specs.
Is it just a DN Server Problem or is it a Bug on DZ?
Did anyone experienced this? I guess it isn't only me.

[MeshPolygon]

Your ping test may get a more accurate results if you use a Singapore-based server as your ping test server. Unfortunately, you used one from Google which doesn't allow you from doing so. Please use another internet speed test like Speedtest by Ookla or any that allows selecting a Singapore server, more preferably a Starhub server because they're the service provider of Dragon Nest SEA.

You may also want download Windows version of MTR, WinMTR, for further observation of your network stability. Put the IP 203.116.185.1 (Starhub IP) in the host field, and run it indefinitely in the background while playing Dragon Nest. Stop it when you're done :3, or *stop it five minutes after you experienced a disconnection from the game. Click "Copy Text to clipboard" and post your results here, enclose it in [CODE][/CODE] to carry over the formatting.

Here's mine for example

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             HOME-Router -    0 |  299 |  299 |    0 |    0 |    3 |    0 |
|                             192.168.1.1 -    0 |  299 |  299 |    1 |    3 |   25 |    1 |
|                              100.65.0.1 -    0 |  299 |  299 |   20 |   32 |  127 |   24 |
|                   No response from host -  100 |   60 |    0 |    0 |    0 |    0 |    0 |
|         210.213.130.209.static.pldt.net -    2 |  284 |  280 |   20 |   31 |  243 |   75 |
|                   No response from host -  100 |   60 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   60 |    0 |    0 |    0 |    0 |    0 |
|             an-atl-int10.starhub.net.sg -    3 |  272 |  265 |   90 |  100 |  325 |   96 |
|                           203.116.185.1 -    1 |  295 |  294 |   88 |   97 |  319 |   89 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

---

EDIT

The acceptable packet loss for DN is 0% since it is not so tolerant on packet loss, a numerous sequence of packet loss is enough to make you DC, those 100% packet loss network nodes were just configured not to respond to pings. Ping result may also not be that accurate since some network equipment might be configured not to respond and drop fast pings or you pinged them for too long and blocked you.

You may also run a ping command indefinitely to further see what's going while playing. ping -t 203.116.185.1 (Starhub IP)would do. Control-C to stop.

This will definitely rekt your connection.

---

EDIT2

For comparative purpose, ping another known stable server, www.google.com maybe. Ping it in the background. When you DC'ed again, check for losses. If it's fine, we could say that your connection to DN servers really have issues. If it's full of packet losses, the problem might be somewhere at your end.

---

EDIT3

Sorry, forgot this one. If those two are fine(Starhub IP and the other known stable server or as long as Starhub IP is fine) and you are still experiencing disconnections, then the DN server probably has issues.

[yewray]

What ip address or website u used for cmd?

[MeshPolygon]

That was a google IP if I remember correctly.

[yewray]

The "Request time out" in CMD means dc right? but the dc problem is on our side or the server side?

[MeshPolygon]

RTOs = DCs? It depends. One or few is survivable. A large sequence, no. "By default, ping waits 4,000 milliseconds (4 seconds) for each response to be returned before displaying the "Request Timed Out" message" - Microsoft. So let's say you got 8 RTO in sequence, it's equivalent of 32 secs of network downtime, you are going to be out of sync for far too long, too long to make a recovery, enough for DN to consider the connection unreliable and just close it.

And if it's a client side or a server problem. The best you could do is ping a Starhub IP(203.116.185.1) and another known stable server, www.google.com maybe, at the same time for comparative purposes. Bring out two command prompt consoles ping the Starhub one on one consoles and the other server at another console in the background while playing. When you DC'ed again, take note of the losses. If the Starhub IP is the only one having packet losses and the other known stable server is well, your network have issues connecting to Starhub. If both of them having losses, then the problem definitely somewhere near at your end. And if both of them have good results and you are still experiencing disconnections, time to contact ED. I'm not saying that the server has problems, well probably, but there also different angles to consider. Maybe it is fine when we are just sending pings, but things could proceed differently on the actual scenario. Who knows. Someone in the middle might be tampering the packets. Our ISP is trolling us making the packets go all over the world then get it at last to ED server, hey this one really happens, ask PLDT about it :3. Or some network glitch that corrupts packet specifically for DN, etc. Until those are proven non existent, we can't say DN SEA server is crap.

[Nimmienaticz]

btw. this is my ping, it seems like i dont have any RTO after checking it multiple times.

[MeshPolygon]

Uhmm do you still experience disconnections at dz even with this kind of ping results?

[Nimmienaticz]

yes i still have. occasionally on portals (gts portal), some while in the middle of nest, and some upon entering LCE.

[MeshPolygon]

Time to start notifying them by mentioning their names here, or send them a ticket. It high time for them to investigate on this.