Status
Not open for further replies.
Any idea why I'm seeing higher than usual latency to blizzard eu servers?

I usually get around 180ms, now it's over 240? What gives?

Seeing the same thing on PUBG as well.
 
Any idea why I'm seeing higher than usual latency to blizzard eu servers?

I usually get around 180ms, now it's over 240? What gives?

Seeing the same thing on PUBG as well.

Pinging 185.60.112.157 with 32 bytes of data:
Reply from 185.60.112.157: bytes=32 time=224ms TTL=237
Reply from 185.60.112.157: bytes=32 time=225ms TTL=237
Reply from 185.60.112.157: bytes=32 time=224ms TTL=237
Reply from 185.60.112.157: bytes=32 time=224ms TTL=237
 
Pinging 185.60.112.157 with 32 bytes of data:
Reply from 185.60.112.157: bytes=32 time=224ms TTL=237
Reply from 185.60.112.157: bytes=32 time=225ms TTL=237
Reply from 185.60.112.157: bytes=32 time=224ms TTL=237
Reply from 185.60.112.157: bytes=32 time=224ms TTL=237

What does a trace look like?
 
@PBCool Do you know what the issue and ETA is with the Netstream maintenance?
I called support and they said the connection is only being restored at midnight?
Yeah they were struggling with some migration I believe.
 
@PBCool assisted me via PM, pings back down to 170.

Pinging 185.60.112.157 with 32 bytes of data:
Reply from 185.60.112.157: bytes=32 time=171ms TTL=245
Reply from 185.60.112.157: bytes=32 time=171ms TTL=245
Reply from 185.60.112.157: bytes=32 time=170ms TTL=245
Reply from 185.60.112.157: bytes=32 time=171ms TTL=245
 
Looks like Vox's SACS link is doing well

CISP not yet there...

Did a quick test from my side, have to say, quite impressive :cool:

Tracing route to 187.120.30.6 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 18 ms 22 ms 18 ms 192.168.10.1
4 14 ms 17 ms 20 ms 192.168.11.2
5 17 ms 18 ms 17 ms 154.0.4.209
6 32 ms 31 ms 32 ms 154.0.1.62
7 35 ms 38 ms 37 ms 154.0.4.162
8 32ms 34 ms 33 ms 102.130.64.13
9 69 ms 68 ms 75 ms pe2-nc029.ang.sgn.as37468.angolacables.ao [197.149.151.198]
10 130 ms 131 ms 151 ms 170.238.232.149
11 127 ms 128 ms 134 ms pe1-nc013.br.ftz.as37468.angolacables.ao [170.238.232.81]
12 130 ms 129 ms 130 ms 170.238.235.18
13 124 ms 124 ms 124 ms 187.120.30.6

Trace complete.
 
Did a quick test from my side, have to say, quite impressive :cool:

Tracing route to 187.120.30.6 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 18 ms 22 ms 18 ms 192.168.10.1
4 14 ms 17 ms 20 ms 192.168.11.2
5 17 ms 18 ms 17 ms 154.0.4.209
6 32 ms 31 ms 32 ms 154.0.1.62
7 35 ms 38 ms 37 ms 154.0.4.162
8 32ms 34 ms 33 ms 102.130.64.13
9 69 ms 68 ms 75 ms pe2-nc029.ang.sgn.as37468.angolacables.ao [197.149.151.198]
10 130 ms 131 ms 151 ms 170.238.232.149
11 127 ms 128 ms 134 ms pe1-nc013.br.ftz.as37468.angolacables.ao [170.238.232.81]
12 130 ms 129 ms 130 ms 170.238.235.18
13 124 ms 124 ms 124 ms 187.120.30.6

Trace complete.
With the CISP DNS no idea why mine is so bad1540323780491.png
 
Did something just die?

Twitch and twitter won't load - as well as other sites.

Cape town - Open serve - tried both oneDot and CI DNS. same thing all dead.
 
Last edited:
Same here... been happening to me quite often. Rebooted my router and now international is working again.
 
Any chance of a response, still not working and have heard nothing back from you. Thanks.

I have replied to your ticket.

If there is still an issue I'd like to eliminate last mile packet loss. But let's carry on on the ticket.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X