I'm trying to get to app.e2ma.net, and it doesn't work from the verizon network, but works fine from other networks.
Trace route from Verizon:
1: lo0-100.bstnma-vfttp-324.verizon-gni.net 2.550ms
1: lo0-100.bstnma-vfttp-324.verizon-gni.net 3.662ms
2: b3324.bstnma-lcr-22.verizon-gni.net 8.637ms
3: no reply
4: no reply
5: 0.et-10-3-0.gw7.dfw13.alter.net 49.401ms asymm 6
6: sungard-gw.customer.alter.net 53.423ms
7: dal2cr2-te-0-0-0-1.sgns.net 57.216ms asymm 10
8: smy1cr1-te-0-1-0-2.sgns.net 60.705ms asymm 9
9: alp1cr1-te-0-0-1-0.sgns.net 62.317ms asymm 8
10: 66.179.229.122 59.868ms asymm 7
11: 64.238.200.98 84.621ms asymm 8
12: 130.250.160.105 85.173ms asymm 7
13: no reply
14: no reply
15: no reply
Trace route from amazon server:
1?: [LOCALHOST] pmtu 9001
1: 10.0.0.1 0.168ms pmtu 1500
1: no reply
2: no reply
3: no reply
4: no reply
5: no reply
6: 100.65.10.33 0.565ms
7: 205.251.244.224 1.492ms asymm 8
8: 52.93.24.153 1.350ms asymm 7
9: 54.239.111.20 246.642ms asymm 13
10: no reply
11: no reply
12: 54.239.43.201 31.972ms asymm 15
13: 176.32.125.154 48.756ms asymm 20
14: 176.32.125.190 46.231ms asymm 19
15: 176.32.124.212 38.095ms asymm 17
16: 0.TenGigE0-3-0-9.GW6.DFW13.ALTER.NET 31.698ms asymm 19
17: 0.et-11-3-0.GW7.DFW13.ALTER.NET 39.266ms asymm 18
18: smy1cr1-te-0-1-0-2.sgns.net 40.495ms asymm 19
19: dal2cr2-te-0-0-0-1.sgns.net 40.834ms
20: smy1cr1-te-0-1-0-2.sgns.net 40.552ms asymm 19
21: 64.238.200.98 70.172ms asymm 22
22: 64.238.200.98 78.341ms
23: 130.250.160.105 69.456ms asymm 19
24: no reply
25: no reply
They both seem to hit 130.250.160.105, yet pings from verzon don't work, and pings from the amazon network do.
Do I just hope the owner upstream of 130.250.160.105 discover the problem and fixes it? Is there any way to get this resolved?