StormFiber - Weird latency shoot to Dubai (StormFiber)
Hello,
So its been 5 months and I used to be a happy StormFiber customer. Two of the main reasons was streaming and gaming.
The routing wasn't that great on Transworld towards Dubai and Singapore servers so on my request they shifted me to PIE and from 140ms it went to 28ms in Dubai for me and I was over the moon because it was one hell of a drastic change.
Pings on SEA were 72ms, better than 110ms earlier. 4 months went well, but suddenly since last month I started facing 148ms on dubai servers. SEA is only 83ms but from 28ms to 147ms it was really unplayable.
I ran tracert and shared with SF team but they had no other response as it was out of their scope and they couldnt do shit about it.
I wanna share the TRACERT with you guys, the ping is absolutely fine at all hopes beside the last hop. I have no idea why does it take that high jump.
Can anybody please explain why from 28ms on 2nd last hop to 149ms to the last hop?
My friends who are still using PTCL are getting 45ms same on PIE node.
Can anybody please help me out? I don't wanna get back to PTCL.
TIA
Hello,
So its been 5 months and I used to be a happy StormFiber customer. Two of the main reasons was streaming and gaming.
The routing wasn't that great on Transworld towards Dubai and Singapore servers so on my request they shifted me to PIE and from 140ms it went to 28ms in Dubai for me and I was over the moon because it was one hell of a drastic change.
Pings on SEA were 72ms, better than 110ms earlier. 4 months went well, but suddenly since last month I started facing 148ms on dubai servers. SEA is only 83ms but from 28ms to 147ms it was really unplayable.
I ran tracert and shared with SF team but they had no other response as it was out of their scope and they couldnt do shit about it.
I wanna share the TRACERT with you guys, the ping is absolutely fine at all hopes beside the last hop. I have no idea why does it take that high jump.
Code:
Tracing route to 185.25.183.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.100.1
2 2 ms 2 ms 2 ms 202.163.100.252
3 4 ms * 3 ms 202.163.100.13
4 2 ms 2 ms 2 ms 202.163.100.66
5 2 ms 2 ms 2 ms khi77.pie.net.pk [221.120.205.77]
6 4 ms 3 ms 3 ms rwp44.pie.net.pk [221.120.251.229]
7 3 ms 2 ms 2 ms static-khidr-ni02-sw.pie.net.pk [202.125.128.179]
8 28 ms 27 ms 27 ms khi77.pie.net.pk [202.125.132.230]
9 31 ms 30 ms 31 ms 10.44.152.146
10 28 ms 28 ms 28 ms 94.205.255.33
11 148 ms 148 ms 149 ms 185.25.183.1
My friends who are still using PTCL are getting 45ms same on PIE node.
Code:
Tracing route to dxb.valve.net [185.25.183.1]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 21 ms 21 ms 26 ms 182.176.0.51
3 17 ms 16 ms 17 ms 10.0.4.5
4 17 ms 18 ms 15 ms static-10GE-KHI494-P01-KHI494-SWA.pie.net.pk [202.125.128.174]
5 18 ms 17 ms 15 ms static-khidr-ni01-sw.pie.net.pk [202.125.128.141]
6 41 ms 42 ms 43 ms khi77.pie.net.pk [202.125.132.230]
7 44 ms 45 ms 45 ms 10.44.152.146
8 * * * Request timed out.
9 41 ms 41 ms 42 ms 185.25.183.1
Trace complete.
TIA
Last edited: