My brother mentioned that as well so it's probably happening but an entirely different issue. The first IP between TW and Omantel was affected which subsequently messed with every single server that was available through the Omantel route - that no longer happens. This is some other problem...
TW latency issue stemmed from Omantel and happened between October and December. Haven't noticed it for a couple of months and I use that server every night almost
Thanks man. Direct TW user so was wondering how it looked like for PTCL guys because I had a feeling it would look good. Currently this IP address is irrelevant and useless, but I'm assuming AWS will be using this ISP in Bahrain for their servers. Think it's operational in March.
Interestingly...
I don't understand why you want to get an optimised route for a website? Either way it's always dynamic and I'm not expert so I have no idea way. Changes day to day so there must be something to it.
As for the peer, it's most likely the Singapore internet exchange you are looking at. Doesn't...
There's an optimised traceroute using pie on one of the recent srormfiber thread pages. Send that and yours and it should get fixed. Alternatively, follow the troubleshooting steps on i3d.net. They are very helpful and might even get through to PTCL on your behalf. That's what they did for me...
Division rivals and weekend league are on dedicated servers in the UAE. They have been since September 17. That's where you are connecting to and I get 20~ ms to the server on TW. Always have and great performance. IP address is 185.179.202.65. Send a MTR report to i3d.net if you think you are...
Yeah he's reluctant so far because he needs the HD box to watch football. But with the new fifa coming out and them also on i3d.net servers it might be time for him to go back on Tata sky for football and get TW because you know how unreliable routing is. Randomly there's a day when they decide...
Yeah I shifted to TW from fiberlink in April. Just another world in terms of consistency of routing and reliability. I haven't had a disconnection yet apart from the micro disconnection you get to get a new IP once a day.
Latency is also reliable during peak hours except the last two weeks I...
Destination untraceable isn't relevant. It's there to avoid being ddos'd.
I'm not sure. I don't have ptcl but I'm going to assume it goes to shit during peak times especially because of the number of hops being used to get to the destination. The poster who originally mentioned this maybe can...
It doesn't matter where it's taking you judging by those results because the routes are both first going to Europe and then to Singapore/HK which perfectly explains why you can't stream on ptcl.
Notice how my route goes directly to the twitch servers after TW's last hop which tells me that TW...
I don't have any problems with streaming on twitch full quality during peak hours or otherwise. Transworld
And, yes we go straight to singapore
C:\Users\dell>tracert live.twitch.tv
Tracing route to live-sin.twitch.tv [45.113.129.123]
over a maximum of 30 hops:
1 2 ms 5 ms 3...
Was getting 22 ms on LAN with TW
- - - Updated - - -
Good to see it works through pie now bro. Looks like they can go through Omantel now as long as the necessary IP prefix is advertised.
Here's how it looks like on transworld:
Tracing route to hosted-by.i3d.net [185.179.202.196]
over a...
The announcing theory is only relevant for TW because Omantel, a TW upstream, have a direct connection with i3d.net servers. For PTCL and their routing you may or may not get those 90-100 ms pings but they aren't intentional and can't be controlled by PTCL.
All ISPs relying on another ISP for bandwidth will always eventually degrade in quality. I bet TW do it on purpose. What can these smaller ISPs even do? It's a monopoly. Especially as the other option is PTCL