Hi, I noticed some high latency today in competitive, so I asked others in the match if their connections were higher than normal and nobody else reported anything out of the ordinary.
I’ve made a custom game as advised, confirmed it’s connected to the Sydney server with netgraph and alt tabbed out to run WinMTR - Traceroute times out at 8 hops so I couldn’t see any issue there.
But in WinMTR at hop 13 it’s routing through 54.240.192.109 - I had a look on WHOIS IP and it’s showing as Amazon Seattle, which would explain my 140ms ping today.
Strangely enough I checked World of Warcraft and Diablo 3 and my ping to those 2 games is 19-23ms as normal, only Overwatch is affected, not sure if I should contact my ISP or if this is an issue with Blizzard internally, I’m with Internode ISP
Update, ran a traceroute to the OW servers in Sydney (PSE2) in custom games on my mobile phone on the mobile network (off home fiber) and it’s also routing via Washington before going to Sydney, Australia - Can I get an ETA on a fix?
2 Likes
OCE network bug - #10 by Matt1000-1391 we have the same issue post on this thread so they will look at it maybe mate
1 Like
I did see that thread, but I’m not getting slightly higher pings (40 to 100-120) I’m getting US-East pings and traceroutes to the PSE2 servers, 23ms -> 140ms
(Sounds like you guys are having a routing issue in SA thats giving an extra 60 or so ms, i’m literally seeing traceroutes go to the states and back with a traceroute map on my phone)
Same issue in Sydney, seem to always get PSE2 servers with 140ms ping rather than usual ~24ms.
Custom game puts me in amazon southeast
ec2-13-239-11-68 ap-southeast-2 compute amazonaws com [13.239.11.68]
1 Like
Also yesterday was fine, it’s a new problem today for me
Are you with Internode/iinet/TPG by any chance? Mine only started happening today as well. Internode’s service status page is full of service disruption issues so I’m -hoping- it’s just from that
I tried pinging on mobile data with the same issue, I might try making a custom game with my phone tethered via USB to see if it’s Internode’s network causing weird routing somehow on game creation, or both are having issues
EDIT: 50ms in custom game phone tethered via USB - It’s Internode for sure, might give em a call.
I have been having this problem all day 
i have had 150 ping when usually i have around 30. I have tried almost everything and this is the only game that is affected.
Same experience for me also. I’m an Internode customer in Sydney.
A mate who lives in the same building as me is with Aussie Broadband and his connection is fine.
This certainly appears to be an issue with a recent change to Internode’s routes or an upstream network provider they depend upon.
1 Like
This problem’s driving me nuts. Some more acknowledgement from the staff would be a bit comforting (havent heard back in a while on my post about this).
1 Like
Same problem here. High ping (150ms when I normally get 40ms). Sydney, Internode, ADSL2.
I suspect it’s an Internode issue rather than a Blizzard one - Take a look at Internode’s “Service status” - There’s like 44-45 sites with red " High impact - network-wide interruption of services likely" issues. I’ve never seen this many before.
I’ll likely call them tomorrow or Monday if not resolved requesting I not be billed for this month.
The strange thing is, I checked both World of Warcraft (under level 10 doesn’t require subscription) and Diablo 3 - Both are under 30ms latency, in the same location.
Something is screwy between Internode and Overwatch specifically.
You might be right but their service status is always spotty so it’s hard to tell. I’ve been getting constant drop outs from them too lately - but it seems to have stopped. I dont know - 2019 is shaping up to be a sh*t show for my internet connection haha
Found the server that shows routing to Amazon in the US in the WinMTR, server is 54.79.111.170 - Every other server on PSE2 I connect to is affected as well but hop 13 times out on them
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dsldevice.lan - 0 | 65 | 65 | 0 | 0 | 2 | 0 |
| lo0.bras21.bne8.on.ii.net - 0 | 65 | 65 | 3 | 3 | 7 | 3 |
| be4.cr2.bne8.on.ii.net - 0 | 65 | 65 | 3 | 3 | 5 | 3 |
| 203-219-107-25.static.tpgi.com.au - 0 | 65 | 65 | 3 | 3 | 8 | 3 |
| bri-pow-que-crt1-po10.tpgi.com.au - 0 | 65 | 65 | 14 | 25 | 191 | 14 |
| syd-sot-ken-crt3-te-1-5.tpgi.com.au - 0 | 65 | 65 | 15 | 19 | 24 | 15 |
| 203.29.134-125.tpgi.com.au - 0 | 65 | 65 | 14 | 15 | 18 | 15 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| 54.240.192.109 - 0 | 65 | 65 | 129 | 129 | 133 | 129 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Thank you for the great discussion here everyone and the information, let’s focus the discussion on the threads we are tracking, here for iiNet/Interlode specifically, and Oceanic Network issues here. Just to keep things linear! We’re monitoring and tracking the iiNet issue on our end, and looking for more information for others who are experiencing issues on the PSE servers, outside of iiNet/Interlode.