Routing issues

[Doko-illidan]

Over the last few days latency to most shards from Buenos Aires, Argentina using the ISP “Personal” , formerly known as “Fibertel” has increased noticeably.
The problem seems to be somerwhere in a link between Level 3 and blizzard as per hop 9 to 10 massive latency increase (this was previously only about 30-50ms). For an end point latency of 160-200 most of the time.
Ignore the asterix indicating packet loss/timeout as there is none, argentinian ISPS have been dropping ICMP packets since before most of the people reading this forum were born.
The shards hosted on googleusercontent, are routing great and net 160-170ms which is about as good as you can get from down here in Buenos Aires.

Tracing route to 24.105.62.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     9 ms     9 ms     8 ms  ae13.baires3.bai.seabone.net [195.22.220.56]
  8   140 ms   141 ms   142 ms  et5-1-2.miami15.mia.seabone.net [89.221.41.175]
  9   140 ms     *      141 ms  blizzard.miami15.mia.seabone.net [89.221.41.3]
 10   323 ms     *      321 ms  ae1-br01-eqmi2.as57976.net [137.221.76.33]
 11   318 ms     *      320 ms  xe-0-0-0-1-br01-eqat2.as57976.net [137.221.65.50]
 12     *        *        *     Request timed out.
 13   318 ms     *      320 ms  et-0-0-1-pe02-eqch2.as57976.net [137.221.69.53]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

[Jetsum-echo-isles (Jetsum)]

The only thing you can do is contact your ISP as Blizzard has no say in how your ISP does its peering partners and the route they decide to take to get to Blizzard’s servers.

[Bilbonson-quelthalas]

Same issue with fibertel 320ms constant this week. Some friends with this isp have it working fine, cant tell where the problem is

[Elocin-mugthol]

Looks like Seabone in Miami is the issue, but that’s still outside Blizzard’s network. They only name the node for convenience when setting up routing tables (the routing peer’s tables, not Blizzard’s).

@Doko-illidan

  9   140 ms     *      141 ms  blizzard.miami15.mia.seabone.net [89.221.41.3]
 10   323 ms     *      321 ms  ae1-br01-eqmi2.as57976.net [137.221.76.33]

You can see the time it takes for Seabone to communicate with Level 3 above is quite slow.

[Doko-illidan]

Still not fixed. These people on the spanish support site are having the same issues.

Problemas de MS desde el 01/05

I realize this is not a problem inside blizzard’s network per say, however it is basically preventing your customers from playing the game as anything over 220-250ms is a miserable experience / unplayable.
This is not something that my ISP’s costumer support will fix even if I bugged them daily for the next 2 years. Unless a major website is unreachable / unusable they won’t lift a finger.
New PoE season coming out so il just play that for a bit, maybe the faulty equipment / qos settings sort themselves out in the meantime, but just want to be clear contacting our ISPs is about as impactful as adding a single drop of water on the pacific ocean.

[Elocin-mugthol]

@Doko-illidan

I realize this is not a problem inside blizzard’s network per say, however it is basically preventing your customers from playing the game as anything over 220-250ms is a miserable experience / unplayable.

Just to be clear, I’m a fellow player like you. It’s not a problem with the ISP, it’s a routing peer they pay to route their network traffic (Seabone). Your ISP is Seabone’s customer, not you or Blizzard. It wouldn’t make sense for Blizzard to contact the ISP since they don’t do business with them. But since your ISP’s choice of routing peer is affecting you, it does make sense for you to raise this concern with the company you’re paying.