Can we have a fix on snjsca04

[Menriq]

At this point, I'm having to give up my spot in the static because of this issue right during primetime. It would be nice if someone were to raise the issue, but it doesn't seem like it's either a priority or we are a small minority that the cost benefit isn't worth fixing.

[Flarestar]

Same. This starts at 10 PM Eastern and continues until roughly 1 AM every night - like literally we were mid-pull tonight and at 10 PM on the dot everyone started iceskating on my screen.

This is clearly a traffic shaping behavior NTT is engaging in on that node during west coast primetime. Square, you guys have gotta get in touch with them to get it resolved.

[Liralara]

Bump. Same issue again tonight. Started around 9pm CST. Same node within NTT's network in San Jose.
The support ticket I have they stated that they have numerous reports of this and they are working on it. Take that as you will.

[Freki42]

Same. This starts at 10 PM Eastern and continues until roughly 1 AM every night - like literally we were mid-pull tonight and at 10 PM on the dot everyone started iceskating on my screen.

This is clearly a traffic shaping behavior NTT is engaging in on that node during west coast primetime. Square, you guys have gotta get in touch with them to get it resolved.

have you been told by SE they are not looking into the issue? I know it has affected a good many people here on the forums, but only a few of the tracert's and other track information doesn't show just those NTT nodes having an issue, heck the one that is posted about here is in NJ and owned by an elevator company. I don't know what to tell you.

[NevaehQuest]

every freaking night 7pm -11pm

[Zinzu]

have you been told by SE they are not looking into the issue? I know it has affected a good many people here on the forums, but only a few of the tracert's and other track information doesn't show just those NTT nodes having an issue, heck the one that is posted about here is in NJ and owned by an elevator company. I don't know what to tell you.

Please double check your post.

The whois data you posted is for 192.250.5.17. This node that we're referencing is 129.250.5.17

https://www.whois.com/whois/129.250.5.17

This is an NTT node.

[Freki42]

Please double check your post.

The whois data you posted is for 192.250.5.17. This node that we're referencing is 129.250.5.17

https://www.whois.com/whois/129.250.5.17

This is an NTT node.

you are correct i apparently transposed the 2 and the 9. and you are correct it is NTT, but still SE has no hold over them. they can talk and it has been commented that they are in talks with them. this node however as shown is in CO. this makes it even more interesting as I am an East coast player and it would stand to reason that I would be affected by this, however I am not. I am genuinely curious as to why I am not affected (no I am not using a VPN, but connected directly to verizon fios. good catch of my mistake. My apologies.

[NevaehQuest]

thanks you guys are doing gods work, please keep it up~!

[Leviathan1usa]

Freki42, if they pay NTT as their host then yes they would have a hold over them to get it fixed and they have done this before as NTT is the host for their servers, not just some random intermediate IP host. Your thought process as far as it stands to reason that you would be affected by it would not be exactly accurate. The reason for this is your routing table for Verizon is more than likely routed differently from those that are experiencing the issue. Not every internet provider routes the same way through to that server so that would probably be why you are seeing a different affect from others.

[Zerea]

My stuff is still borked. Every night from 9:45 PM ET to 12:15 AM. Same issue as everybody else here is reporting.

220ms all throughout prog was a ton of fun.