Server side ping spike?


#1

C:\Users\win>tracert 52.66.29.29

Tracing route to ec2-52-66-29-29.ap-south-1.compute.amazonaws.com [52.66.29.29]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 9 ms 8 ms abts-mp-static-199.100.168.122.airtelbroadband.in [122.168.100.199]
3 8 ms 7 ms 7 ms 125.21.0.109
4 41 ms 41 ms 40 ms 182.79.224.126
5 40 ms 43 ms 40 ms 182.79.234.245
6 41 ms 41 ms 41 ms 52.95.218.181
7 66 ms 64 ms 64 ms 52.93.19.102
8 60 ms 60 ms 60 ms 52.93.19.111
9 60 ms 60 ms 60 ms 54.239.43.170
10 67 ms 65 ms 66 ms 52.95.67.32
11 60 ms 60 ms 60 ms 52.95.67.27
12 70 ms 71 ms 71 ms 52.95.67.48
13 62 ms 62 ms 61 ms 52.95.67.65
14 61 ms 60 ms 60 ms 52.95.67.210
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 60 ms 60 ms 61 ms ec2-52-66-29-29.ap-south-1.compute.amazonaws.com [52.66.29.29]

6th hop is when i enter server range and in 7th it spikes


#2

bump…


#3

@VuNaMi is this something we can report to AWS?


#4

Bump :frowning:


#5

Hello? Seems like no one’s interested :confused:


#6

We are looking for an alternate DC in Mumbai which should have better routing for some people. There will be an announcement once that is live.


#7

Getting high ping now


#8

Tracing route to ec2-52-66-29-29.ap-south-1.compute.amazonaws.com [52.66.29.29]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms domain.name.dlink.com [192.168.0.1]
2 <1 ms 1 ms 1 ms 5.5.5.80
3 1 ms <1 ms <1 ms host-12301.fivenetwork.com [183.87.12.201]
4 31 ms 31 ms 30 ms 59.145.88.221
5 61 ms 89 ms 60 ms 182.79.198.68
6 66 ms 66 ms 66 ms 52.95.218.181
7 108 ms 108 ms 113 ms 52.93.19.86
8 107 ms 103 ms 100 ms 52.93.19.95
9 90 ms 90 ms 62 ms 54.239.43.170
10 69 ms 72 ms 67 ms 52.95.67.76
11 65 ms 64 ms 65 ms 52.95.67.67
12 68 ms 65 ms 70 ms 52.95.67.132
13 69 ms 68 ms 68 ms 52.95.67.153
14 60 ms 59 ms 59 ms 52.95.67.214

WHEN IS THIS GOING TO GET FIXED ?


#9

@JLT You had confirmed on Wed, Aug 30, 2017 at 5:52 PM that your routing has now been fixed.

Note that we do not have any SLA on routing as it is dependent on factors out of our control.


#10

Yes i did confirm, but it was for a very brief period, it started again in like 10 days but i was kind of on a hiatus from cs so i didnt report it again but now when i want to pug it out i cant because ping sucks for reasons that are not in control of my ISP.


#11

No shit given to subscriber’s “Legit” issues, weird that a gaming company of which a huge market is based on proper connectivity says its not in included in "SLA"
Yeah nice, if everyone has these issues then would i see the same reply ? hell no, please dont make your one of the initial subs to hate the platform for a “fixable” issue, hope you give a damn.


#12

And you mentioning that any DC would not fix the issue saying its not included in SLA is jsut absurd.


#13

Hi,

As you remember, I have approached AWS multiple times about the routing. For this, this is such a minor problem that they just beat around the bush and not take responsibility.

In the long term, we are looking to source our bandwidth from a few other providers which should improve the situation.

However, I am willing to reopen the case with AWS again if you can send me the routing data (again) to my email.

Regards,
VuNaMi