After 2 days of constant Http 504 errors for two specific sites, that everyone else there is not having a problem!
I took my same connected computer (hibernated) to another other WiFi location and confirmed I only have a problem with T-mobile Gateway Servers Lagging over 3000ms causing Http 504 Gateway Error, Here is the proof!
Somebody or something is data shaping/throttling/blocking certain IP ranges!
My bet is that T-Mobile is, now how do I prove it!
How else can I prove what is the real problem?
I'm using trace route (tracert) Sam Spade's traceroute for identifying where the delay problem is.
Here is the results from my local the Library, which works Perfect with instant return pages:
[quote]08/17/13 12:45:07 Slow traceroute HentaiVerse.org
Trace hentaiverse.org (5.79.76.155) ...
* * * failed
* * * failed
* * * failed
* * * failed
* * * failed
* * * failed
* * * failed
* * * failed
* * * failed
* * * failed
5.79.76.155 RTT: 175ms TTL: 49 (applejack.is.best.pony probable bogus rDNS: No DNS)[/quote]
[quote]08/17/13 12:33:19 Spade Log
08/17/13 12:33:40 Fast traceroute e-hentai.org
Trace e-hentai.org (95.211.201.44) ...
1 No Response * * *
2 No Response * * *
3 No Response * * *
4 No Response * * *
5 No Response * * *
6 No Response * * *
7 No Response * * *
8 No Response * * *
9 No Response * * *
10 No Response * * *
11 No Response * * *
12 95.211.201.44 124ms 128ms 127ms TTL: 52 (fluttershy.is.best.pony probable bogus rDNS: No DNS)[/quote]
THE ABOVE WORK FINE 12 HOPS WITHOUT ANY DELAYS ~128ms, like I'm next door.
Ok I'm back home and the http 504 error is back, HV is constantly blocked, but e-hentai.org is intermittent.
Look at the terrible route t-moblie sends me thru: almost 4000ms delay to the first hop; their Gateway!
Here is the trace log from my home (t-mobile) ISP.
[quote]08/17/13 19:00:40 Fast traceroute hentaiverse.org
Trace hentaiverse.org (5.79.76.155) ...
1 10.10.10.1 35ms 3ms 4ms TTL: 0 (No rDNS)
2 10.170.218.48 3921ms 1123ms 53ms TTL: 0 (No rDNS)
3 10.170.218.137 3835ms 1024ms 69ms TTL: 0 (No rDNS)
4 10.170.218.166 3754ms 931ms 52ms TTL: 0 (No rDNS)
5 10.170.218.165 3655ms 833ms 48ms TTL: 0 (No rDNS)
6 10.170.218.5 3569ms 732ms 51ms TTL: 0 (No rDNS)
7 10.170.218.11 3469ms 631ms 47ms TTL: 0 (No rDNS)
8 10.177.18.29 3375ms 537ms 57ms TTL: 0 (No rDNS)
9 10.177.18.46 3273ms 430ms 61ms TTL: 0 (No rDNS)
10 4.28.68.29 3188ms 338ms 57ms TTL: 0 (xe-9-0-0.edge4.Chicago2.Level3.net ok)
11 4.69.158.130 3185ms 340ms 156ms TTL: 0 (No rDNS)
12 4.69.140.189 3093ms 237ms 176ms TTL: 0 (ae-6-6.ebr1.Chicago1.Level3.net ok)
13 4.69.132.66 2990ms 153ms 155ms TTL: 0 (ae-2-2.ebr2.NewYork2.Level3.net ok)
14 4.69.135.253 2908ms 156ms 175ms TTL: 0 (ae-1-100.ebr1.NewYork2.Level3.net ok)
15 4.69.141.17 2807ms 150ms 154ms TTL: 0 (ae-4-4.ebr1.NewYork1.Level3.net ok)
16 4.69.137.69 2715ms 158ms 181ms TTL: 0 (ae-42-42.ebr2.London1.Level3.net ok)
17 4.69.143.81 2615ms 166ms 155ms TTL: 0 (ae-48-48.ebr2.Amsterdam1.Level3.net ok)
18 4.69.153.214 2514ms 153ms 180ms TTL: 0 (ae-59-224.csw2.Amsterdam1.Level3.net ok)
19 4.69.162.201 2411ms 157ms 152ms TTL: 0 (No rDNS)
20 212.72.43.74 2313ms 160ms 171ms TTL: 0 (FIBERRING-B.edge4.Amsterdam1.Level3.net ok)
21 5.79.79.233 2212ms 167ms 149ms TTL: 0 (No rDNS)
22 5.79.76.155 2116ms 159ms 177ms TTL: 42 (applejack.is.best.pony fraudulent rDNS)[/quote]
[quote]08/17/13 19:16:01 Fast traceroute e-hentai.org
Trace e-hentai.org (95.211.201.44) ...
1 10.10.10.1 30ms 2ms 3ms TTL: 0 (No rDNS)
2 10.170.218.48 4076ms 1280ms 50ms TTL: 0 (No rDNS)
3 10.170.218.137 3992ms 1182ms 52ms TTL: 0 (No rDNS)
4 10.170.218.166 3915ms 1081ms 48ms TTL: 0 (No rDNS)
5 10.170.218.165 3817ms 980ms 68ms TTL: 0 (No rDNS)
6 10.170.218.5 3722ms 880ms 56ms TTL: 0 (No rDNS)
7 10.170.218.11 3623ms 785ms 59ms TTL: 0 (No rDNS)
8 10.177.18.29 3529ms 687ms 54ms TTL: 0 (No rDNS)
9 10.177.18.46 3431ms 586ms 49ms TTL: 0 (No rDNS)
10 4.28.68.29 3330ms 486ms 78ms TTL: 0 (xe-9-0-0.edge4.Chicago2.Level3.net ok)
11 4.69.158.130 3341ms 487ms 168ms TTL: 0 (No rDNS)
12 4.69.140.189 3238ms 385ms 156ms TTL: 0 (ae-6-6.ebr1.Chicago1.Level3.net ok)
13 4.69.132.66 3140ms 295ms 152ms TTL: 0 (ae-2-2.ebr2.NewYork2.Level3.net ok)
14 4.69.135.253 3047ms 193ms 155ms TTL: 0 (ae-1-100.ebr1.NewYork2.Level3.net ok)
15 4.69.201.41 2945ms 147ms 150ms TTL: 0 (ae-44-44.ebr1.Stockholm2.Level3.net ok)
16 4.69.137.69 2862ms 152ms 154ms TTL: 0 (ae-42-42.ebr2.London1.Level3.net ok)
17 4.69.143.69 2759ms 146ms 152ms TTL: 0 (ae-45-45.ebr2.Amsterdam1.Level3.net ok)
18 4.69.153.214 2661ms 151ms 153ms TTL: 0 (ae-59-224.csw2.Amsterdam1.Level3.net ok)
19 4.69.139.169 2568ms 144ms 148ms TTL: 0 (ae-2-52.edge3.Amsterdam1.Level3.net ok)
20 213.244.164.2 2469ms 147ms 152ms TTL: 0 (BR2.Amsterdam1.surf.net fraudulent rDNS)
21 95.211.201.44 2368ms 144ms 147ms TTL: 41 (fluttershy.is.best.pony fraudulent rDNS) [/quote]
Looks like T-Mobile is sending me the long way thru the uncle sam woods(shapers) to grandma's house!
How do I get T-Mobile to fix their Gateway! or more proof if they need it?
Message was edited by: Glenn D
