Quote:
Originally Posted by stomachmonkey
Not sure what the question is.
Do you believe the issue is with one of the 2 connections?
Is it consistently the same connection or bounce between the 2?
Sounds like a lookup issue. What DNS do you have set?
If the issue really is one of the connections running trace routes will get you more info than an http request.
|
This is the third complaint we've had in 6-8 months. The complaint is always only a single website, and is generally an issue only over one of the links.
The problem isn't DNS. DNS resolves quickly.
Unfortunately ping and/or traceroute isn't indicating any sort of problem.
The website in question this time, doesn't allow icmp, so a traceroute only gets so far, but that's not that unusual these days.
ge-3-1-0.425.ar2.MIN1.gblx.net (67.17.168.165) 8 msec 8 msec 9 msec
pos7-0-0-10G.ar2.CHI2.gblx.net (67.17.105.110) 25 msec 17 msec 17 msec
te-3-3.car3.chicago1.level3.net (4.68.110.193) 25 msec 17 msec 25 msec
ae-31-55.ebr1.Chicago1.Level3.net (4.68.101.158) 25 msec 16 msec 25 msec
ae-6-6.ebr1.chicago2.level3.net (4.69.140.190) 16 msec 17 msec
*
ae-3-3.ebr2.denver1.level3.net (4.69.132.61) 42 msec 50 msec *
- ae-21-54.car1.Denver1.Level3.net (4.68.107.102) 42 msec
- ae-22-54.car2.Denver1.Level3.net (4.68.107.103) 51 msec
- ae-21-54.car1.Denver1.Level3.net (4.68.107.102) 50 msec
ae-1-13.edge1.Denver1.Level3.net (4.68.106.154) 42 msec 50 msec
ae-2-23.edge1.Denver1.Level3.net (4.68.106.158) 42 msec
Quote:
|
For server response times a simple ping is easier.
|
Except pings aren't allowed by the website...
Traceroutes or HTTP GETs reply from most sites in a normal time, or from this site over a different connection in a normal time. I've got a packet capture from our firewall that shows my send the "get" at 15 seconds and the response come back at 75 seconds. 60 seconds isn't normal.