Loosing access to a website at various periods

Scream

Scream

Scream

Soldato
Joined
18 Oct 2002
Posts
4,656
Location
The Darkside
A guy I know is having problems accessing a website with it going great and then the next minute it can become so slow that it ends up failing to load. Other websites work without problems except this website.

It works without problems on my systems but gives lots of problems on his systems. Its only started to give bother this past week or so.

Its hardly anything to do with his ISP would it? (BT Broadband)

Any help would be great as the guy is quite demanding on having it fixed quickly. :mad:
 
A traceroute both when it's working and isn't would probably help.
Doubt it's anything to do with his ISP, but anything's possible without more detail.
 
Tracing route to hp-intl-uk.ebay.com [66.135.208.97]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 31 ms 26 ms 29 ms 217.32.0.122
3 33 ms 27 ms 29 ms 217.32.0.161
4 26 ms 28 ms 28 ms 217.41.174.21
5 24 ms 29 ms 27 ms 217.41.174.118
6 26 ms 27 ms 27 ms 217.41.218.54
7 20 ms 29 ms 30 ms 217.47.186.113
8 24 ms 22 ms 29 ms core2-pos12-1.edinburgh.ukcore.bt.net [217.32.16
9.213]
9 41 ms 27 ms 28 ms core2-pos15-2.birmingham.ukcore.bt.net [194.74.1
6.237]
10 33 ms 39 ms 32 ms core2-pch4.reading.ukcore.bt.net [62.6.204.138]

11 37 ms 31 ms 38 ms 62.6.204.157
12 45 ms 35 ms 42 ms transit2-pos4-0.ealing.ukcore.bt.net [194.72.17.
86]
13 42 ms 37 ms 42 ms t2c2-p8-0.uk-eal.eu.bt.net [166.49.168.33]
14 112 ms 109 ms 113 ms t2c2-p4-0.us-ash.eu.bt.net [166.49.164.62]
15 108 ms 117 ms 111 ms dcp-brdr-02.inet.qwest.net [205.171.1.37]
16 110 ms 110 ms 111 ms dcx-core-02.inet.qwest.net [205.171.251.37]
17 111 ms 108 ms 113 ms dca-core-01.inet.qwest.net [205.171.209.113]
18 * * * Request timed out.
19 177 ms 173 ms 172 ms svc-cntr-01.inet.qwest.net [205.171.14.2]
20 179 ms 175 ms 184 ms msfc-15.jsv.qwest.net [66.77.107.34]
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 * 63.146.113.4 reports: Destination net unreachable.

Trace complete.


The site is ebay and as he is a business seller, he needs daily access which he is having problems with.

I've asked him to try his old USB modem encase his bloody Belkin router is somehow doesn't like ebay.
 
Assuming the traceroute above is while it's not working, if it was DNS servers, it wouldn't be able to find the IP to trace to in the first place.
 
Well, I'm told it wasn't working when that traceroute was taken.

If its not the DNS servers, what else could be culprit?
 
Check MTU for one, though that trace isn't particularly useful - looks like ebay are filtering ICMP:

2 ge0-202-0.bdr2.thdo.lnc.net (62.197.50.138) 0.742 ms 1.010 ms 0.478 ms
3 level3-gw1.thdo.lnc.net (62.197.50.213) 1.685 ms 1.185 ms 1.573 ms
4 ae-0-54.bbr2.London1.Level3.net (4.68.116.98) 1.250 ms ae-0-52.bbr2.London1.Level3.net (4.68.116.34) 0.904 ms ae-0-56.bbr2.London1.Level3.net (4.68.116.162) 1.720 ms
5 so-3-0-0.mp1.SanFrancisco1.Level3.net (209.247.8.89) 143.295 ms 143.397 ms 143.061 ms
6 so-2-0-0.mpls1.Sacramento1.Level3.net (209.247.8.78) 145.318 ms 145.368 ms 145.343 ms
7 so-10-0.hsa1.Sacramento1.Level3.net (4.68.113.58) 145.296 ms 145.367 ms 144.846 ms
8 * * *
9 * * *
Click to expand...
 
Last edited:
Find a site which doesn't work, but also doesn't filter ICMP.

When it doesn't work, trying running telnet 66.135.208.97 80, and see if you get an answer (should be something along the lines of "Trying 66.135.208.97...Connected to hp-intl-uk.ebay.com.").
 
You must log in or register to reply here.
Back
Top Bottom