Lag in Warcraft 2025-03-27

Forums › Vetta and Quic › Lag in Warcraft 2025-03-27

1 | 2

yitz

2239 posts

Uber Geek
+1 received by user: 594

#3360685 4-Apr-2025 13:03

From what I can see Quic don't use any upstreams who have a direct connection into Blizzard North America so you are at the mercy of tier 1 providers and any associated capacity problems between them.

They also seem to use Cogent which is terrible... wonder if they bought that bandwidth contract off 2degrees lol

https://www.geekzone.co.nz/forums.asp?forumid=81&topicid=315179&page_no=1#3251587

Behodar

11102 posts

Uber Geek
+1 received by user: 6095

Trusted

Lifetime subscriber

#3362690 10-Apr-2025 12:59

Behodar:

I explicitly asked Blizzard whether 137.221.105.232 was the correct IP address and they didn't respond. In fact, they went further than not responding: they edited my support ticket and redacted the question out.

I eventually managed to get a response out of them, but unfortunately it was "we will not discuss the IP address of any realm".

Any suggestions on where I can go from here? Can we assume that 137.221.105.232 is correct, given that netstat shows it when connected, and it appears to be in the right sort of geographical area?

yitz

2239 posts

Uber Geek
+1 received by user: 594

#3362693 10-Apr-2025 13:11

telemetry-in.battle.net resolves to 137.221.105.232 so not quite I think.

If you want the realm server IP I guess you need to do a packet capture...

Chorusnz

436 posts

Ultimate Geek
+1 received by user: 603

Trusted

Chorus

#3362733 10-Apr-2025 15:20

Behodar:

Any suggestions on where I can go from here?

Random hail merry but have you tried a VPN? Myself and a couple of guild mates were having issues a year or two ago on (what was then Vodafone). Just to the US wow servers. Random lag spikes for no apparent reason and rest of my network was fine.

Could not figure it out. Tried ExitLag out of pure frustration. Instant fix. Seems there had been some routing issue that the VPN fixed. Used that for about 3 months until the base issue went away. Was the only way the game was remotely playable.

Not saying it is the same issue here, but worth a try? I'm sure you can get a free trial so no real risk involved.

^Richard

Behodar

11102 posts

Uber Geek
+1 received by user: 6095

Trusted

Lifetime subscriber

#3362734 10-Apr-2025 15:21

Good spotting. I might have another poke around and see whether I can find another address that looks about right, although I don't like having to do the whole "trial and error" thing!

Edit: Chorus sneaking in while I was typing :)

I haven't tried a VPN although I expect it'll work around the issue successfully, since the problem seems to be between Quic and Blizzard. It was on my "to think about" list, but I hadn't got as far as actually trying one.

Behodar

11102 posts

Uber Geek
+1 received by user: 6095

Trusted

Lifetime subscriber

#3363077 11-Apr-2025 19:34

I think I've found the right addresses now.

Pings to 64.224.31.40 and 64.224.28.105 are sitting at 290-295 ms, which meshes with what I'm seeing in-game. These addresses are registered to Blizzard.

A traceroute is fine for a while, then hits a "telecomitalia" hop and jumps up after that.

traceroute to 64.224.28.105 (64.224.28.105), 64 hops max, 40 byte packets
1 10.0.1.1 (10.0.1.1) 0.836 ms 0.476 ms 0.341 ms
2 bng1-akl2.vetta.net (103.243.102.38) 11.510 ms 10.254 ms 10.145 ms
3 core1-akl2.vetta.net (103.243.102.212) 10.663 ms 10.137 ms 10.257 ms
4 edge2-akl2.vetta.net (14.102.98.107) 11.339 ms 10.084 ms 10.334 ms
5 * * *
6 be2194.agr61.akl01.atlas.cogentco.com (154.54.88.213) 11.866 ms 11.455 ms 11.831 ms
7 be5434.ccr71.akl01.atlas.cogentco.com (154.54.44.174) 12.146 ms 11.977 ms 11.740 ms
8 be5437.ccr71.syd01.atlas.cogentco.com (154.54.162.129) 39.930 ms 39.827 ms 40.009 ms
9 be2546.ccr31.sin01.atlas.cogentco.com (154.54.1.29) 136.526 ms 138.005 ms 136.502 ms
10 telecomitalia.sin01.atlas.cogentco.com (154.54.140.2) 148.161 ms 147.681 ms 137.749 ms
11 89.221.41.177 (89.221.41.177) 298.682 ms
195.22.199.179 (195.22.199.179) 294.495 ms
89.221.41.175 (89.221.41.175) 297.677 ms
12 *

The other address does the same sort of thing.

Do other Quic users see the same?

Geekzone support

Support Geekzone with one-off or recurring donations Donate via PressPatron.

saf

221 posts

Master Geek
+1 received by user: 533

ID Verified

Trusted

Vetta Group

Subscriber

#3363099 11-Apr-2025 21:30

Those addresses help us a heap, thanks @Behodar.

The team will take a look next week for you now that we have some known IPs to work with. 🙂

My views are as unique as a unicorn riding a unicycle. They do not reflect the opinions of my employer, my cat, or the sentient coffee machine in the break room.

michaelmurfy

meow
13581 posts

Uber Geek
+1 received by user: 10914

Moderator

ID Verified

Trusted

Lifetime subscriber

#3364228 15-Apr-2025 11:00

@Behodar Just been informed to give it a shot now.

Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.

Behodar

11102 posts

Uber Geek
+1 received by user: 6095

Trusted

Lifetime subscriber

#3364267 15-Apr-2025 12:17

Yes! Resolved! Thanks to everyone who helped :)

1 | 2