Massive Lag Spikes/Disconnects

[Koma]

We have alternative IP addresses, but the third test we ran still routed through AS6453 as you noticed. Unfortunately, there's no way for me to obtain more IPs that what we've been assigned and checked so far. While the other server is also in Dallas, it may not be at the same datacenter.

[Resolve]

No offense meant on this succeeding question:

So, uh, given that, should I just quit?

[Koma]

Wasn't saying to quit, just that we have nothing to do with the ISP making that rerouting decision therefore we (Amistr) cannot do much to fix it. The fix would have to be reached by getting your ISP to correct it as you mentioned they were looking into.

Otherwise, we'll have to make another move as the current location is being routed by PLDT to use a craptastic route to the current server. This is still a possibility, but there's no telling what the inverse effects are on other players too as with any server move.

[Resolve]

it appears that the prob may not be on the TATA cable.when the tech support guy used ping on my ip add, there were times when it failed to get anything, so my DSL may be having an intermittent connection. theyre still checkin on it.



Im an atheist but please Pray for me.

[Kiana]

Good Luck Resolve, Im sure you'll get it all worked out.

[Resolve]

Well, this is a sample of what I normally get:

C:\> tracert pldt.com */its my isp's page

then i get 58.71.0.74 as my remote host.

then i do:

ping 58.71.0.74 -t

then i get:

Code: Select all

Reply from 58.71.0.74: bytes=32 time=67ms TTL=253
Reply from 58.71.0.74: bytes=32 time=64ms TTL=253
Reply from 58.71.0.74: bytes=32 time=64ms TTL=253
Reply from 58.71.0.74: bytes=32 time=65ms TTL=253
Reply from 58.71.0.74: bytes=32 time=66ms TTL=253
Reply from 58.71.0.74: bytes=32 time=66ms TTL=253
Reply from 58.71.0.74: bytes=32 time=64ms TTL=253
Reply from 112.xxx.xxx.x: Destination host unreachable.
Reply from 112.xxx.xxx.x: Destination host unreachable.
Reply from 58.71.0.74: bytes=32 time=131ms TTL=253
Reply from 58.71.0.74: bytes=32 time=62ms TTL=253
Reply from 58.71.0.74: bytes=32 time=63ms TTL=253
Reply from 58.71.0.74: bytes=32 time=63ms TTL=253
Reply from 58.71.0.74: bytes=32 time=64ms TTL=253
Reply from 58.71.0.74: bytes=32 time=65ms TTL=253
Reply from 58.71.0.74: bytes=32 time=67ms TTL=253
Reply from 58.71.0.74: bytes=32 time=65ms TTL=253
Reply from 58.71.0.74: bytes=32 time=65ms TTL=253
Reply from 58.71.0.74: bytes=32 time=64ms TTL=253
Reply from 58.71.0.74: bytes=32 time=62ms TTL=253
Reply from 58.71.0.74: bytes=32 time=65ms TTL=253
Reply from 58.71.0.74: bytes=32 time=65ms TTL=253
Reply from 58.71.0.74: bytes=32 time=66ms TTL=253
Reply from 112.xxx.xxx.x: Destination host unreachable.
Reply from 112.xxx.xxx.x: Destination host unreachable.
Reply from 112.xxx.xxx.x: Destination host unreachable.
Reply from 58.71.0.74: bytes=32 time=65ms TTL=253
Reply from 58.71.0.74: bytes=32 time=63ms TTL=253
Reply from 58.71.0.74: bytes=32 time=65ms TTL=253
Reply from 58.71.0.74: bytes=32 time=66ms TTL=253
Reply from 58.71.0.74: bytes=32 time=65ms TTL=253
Reply from 58.71.0.74: bytes=32 time=63ms TTL=253
Reply from 58.71.0.74: bytes=32 time=66ms TTL=253
Reply from 58.71.0.74: bytes=32 time=69ms TTL=253
Reply from 58.71.0.74: bytes=32 time=64ms TTL=253
Reply from 58.71.0.74: bytes=32 time=63ms TTL=253
Reply from 58.71.0.74: bytes=32 time=67ms TTL=253
Reply from 58.71.0.74: bytes=32 time=66ms TTL=253
Reply from 112.xxx.xxx.x: Destination host unreachable.
Reply from 58.71.0.74: bytes=32 time=2216ms TTL=253
Reply from 58.71.0.74: bytes=32 time=64ms TTL=253
Reply from 58.71.0.74: bytes=32 time=65ms TTL=253
Reply from 58.71.0.74: bytes=32 time=65ms TTL=253
Reply from 58.71.0.74: bytes=32 time=66ms TTL=253
Reply from 58.71.0.74: bytes=32 time=65ms TTL=253
Reply from 58.71.0.74: bytes=32 time=66ms TTL=253

the thing is, this only happens when RO is on, otherwise i dont get those unreachable messages.

I think i have enough reason to take off a malfunctioning LAN card as a cause because the problem happens only when I am playing AmistrRO.

I have a theory that most people in my area of the world, i.e. SE Asia players experience massive lagging with the current host, except that my case is more amplified.

I think it really all boils down to the fact that the current data center sucks for the world minus NA, and that although the poll which showed dallas as the middle ground may be accurate, the host that was chosen, which was located in dallas, goes through a different cable compared to Speedtest.net's Dallas Test site.

[Koma]

That connecting point to the 58.71.*.* seems to be where your errors are coming from. Judging from the tracerts you've sent me in the past, that 112.*.*.* address is your first hop too so it makes sense.

1 56 ms 57 ms 57 ms 112.*.*.* [112.*.*.*] <-- where your ping fails to continue to its target
2 58 ms 56 ms 57 ms 119.*.*.*
3 57 ms 57 ms 56 ms 58.*.*.* <--- your ping target

When you connect to any other places, this problem never occurs? Remember, we found out that that 58.*.*.* point is the last connection you make in Asia before it connects to North America. I'm curious if you have those unreachable messages when doing a large transfer overseas too -- or on another server as you've experienced as well.

If we go back in the data comparing the RO servers that worked without issues and the servers that did have issues, there's a direct correlation with that 58.*.*.* IP being present and the start of those AS6453 connections.

The root problem is still the AS6453 link.

EDIT: There is still one possibility that may happen next week. The datacenter is doing switch upgrades on Monday @ 00:00-06:00. I've yet to make an official announcement about this, but the server may experience intermittent connections around that point. In this past week, there was a recent server attack which caused lag for a few players for an hour, but other than that, we haven't heard of many connectivity issues since the last move.

[Resolve]

i think its the AS link really. Because when i use the same thing [ping -t] is always on on my PC, and I surf like, youtube or icefilms.info, this unreachable thing never happens. Yes there are request time outs still, but no unreachable stuff.

[Koma]

Trace your route to those sites. Every connection is different and routed as necessarily chosen by an ISP, so most likely PLDT isn't routing you through that line still to other destinations. Did they ever get back to you about that temporary rerouting?

[Resolve]

Trace your route to those sites. Every connection is different and routed as necessarily chosen by an ISP, so most likely PLDT isn't routing you through that line still to other destinations. Did they ever get back to you about that temporary rerouting?

Well, I have emailed them today about it. I have replaced my LAN card and it still is so messed up. Chances are when all this is over, I'll be more knowledgeable with this thing than those creeps with professional licenses.