I'm by no means an networking expert, but I wanted to give you a news update about the Telekom launcher timeout issue.
There was an intense discussion going on in the German Telekom forum with actual Telekom employees, where people pushed the ISP to do *something*:
https://telekomhilft.telekom.de/conversations/festnetz-internet/routing-problem-nach-japan-zu-square-enix-login-servern-über-ntt-transit-in-japan-paketloss-bei-ntt-japan/69738e3d132cd4765ce39c58?commentId=697760bcf8cc8d2960cdfd4c&replyId=697771f4f8cc8d2960d403bc
There is also a discussion going on in the Square Enix Forum itself:
https://forum.square-enix.com/ffxiv/threads/525983-Kein-Login-im-Launcher/page8
So, to the update:
Telekom says- "We can confirm that the problem is caused by an NTT customer who is overloading their peering connections to us.
Our peering management team is aware of the issue, and we are also in contact with NTT to find a solution.
Unfortunately, we cannot provide a timeframe for resolution, as we are primarily dependent on NTT in this matter."
As a good friend condensed it for me:
"Overload due to rerouting. NTT has to activate AS Path Prepending so that its traffic from DTAG US to DTAG Frankfurt flows via NTT Frankfurt."
As far as I understand this, Telekom and NTT are in active talks to fix the problem. At least we somehow got Telekom to acknowledge that there IS a problem.
submitted by /u/schwamperl
[link] [comments]
Continue reading...
There was an intense discussion going on in the German Telekom forum with actual Telekom employees, where people pushed the ISP to do *something*:
https://telekomhilft.telekom.de/conversations/festnetz-internet/routing-problem-nach-japan-zu-square-enix-login-servern-über-ntt-transit-in-japan-paketloss-bei-ntt-japan/69738e3d132cd4765ce39c58?commentId=697760bcf8cc8d2960cdfd4c&replyId=697771f4f8cc8d2960d403bc
There is also a discussion going on in the Square Enix Forum itself:
https://forum.square-enix.com/ffxiv/threads/525983-Kein-Login-im-Launcher/page8
So, to the update:
Telekom says- "We can confirm that the problem is caused by an NTT customer who is overloading their peering connections to us.
Our peering management team is aware of the issue, and we are also in contact with NTT to find a solution.
Unfortunately, we cannot provide a timeframe for resolution, as we are primarily dependent on NTT in this matter."
As a good friend condensed it for me:
"Overload due to rerouting. NTT has to activate AS Path Prepending so that its traffic from DTAG US to DTAG Frankfurt flows via NTT Frankfurt."
As far as I understand this, Telekom and NTT are in active talks to fix the problem. At least we somehow got Telekom to acknowledge that there IS a problem.
submitted by /u/schwamperl
[link] [comments]
Continue reading...