Rubbish connection today

[zappaDPJ]

I'm having problems connecting here as well. It's been fine all day, now it's timing out on me.

[Gary]

I'm having problems connecting here as well. It's been fine all day, now it's timing out on me.

No problems here Zap apart from a few sites used for signatures that I have now adblocked, they would not load properly. Netgear site is not loading for me.

[esh]

Periodically a whole host of websites do not respond / time out and then the next refresh are fine. This is still going on as I write this post though it is not so frequent to be 'crippling'.

[Gary]

Periodically a whole host of websites do not respond / time out and then the next refresh are fine. This is still going on as I write this post though it is not so frequent to be 'crippling'.

That sums it up perfectly.

[Rik]

If we can give lists of affected sites, it gives IDNet a better chance of working out what's happening.

[Steve]

I have really struggled to get through to those two since last night.

http://www.mx5oc.co.uk/forum/forums/
http://www.mx-5.com/

But it is intermittent.

[Gary]

I have really struggled to get through to those two since last night.

http://www.mx5oc.co.uk/forum/forums/
http://www.mx-5.com/

But it is intermittent.

I cant get through to them either Steve at this time. Its the forum one that will not load now

[Steve]

I switched just now to IDNet DNS and they resolved, then tried again with IDNet DNS and it's no go again,it just doesn't make sense.

[Rik]

Same here, Steve. IDNet DNS.

[Steve]

http://www.downforeveryoneorjustme.com/http://www.mx5oc.co.uk/forum/forums/  confirms it's up.

[Gary]

I dare not change DNS again I think things are getting to confused as it is   I'm on IDNets DNS which works much better since last night than Norton DNS which was working perfectly until this started.

[Rik]

Yup. I've tried Open DNS, Norton & IDNet during the day, with similar results, things work one minute, fail the next, usually with server reset messages. Image-heavy sites seem to be the worst afflicted.

[Gary]

http://www.downforeveryoneorjustme.com/http://www.mx5oc.co.uk/forum/forums/  confirms it's up.

I can get through to it now, still having issues with Deviant arts multiple sub domian thingys Edit: now its fine Arghhhhhhhhhhhhhhh!

[Rik]

I can't.

[Rik]

And now I can.

[Steve]

For site that's supposed to be up

Ping http://www.mx5oc.co.uk/forum/forums/
Ping has started...

PING http://www.mx5oc.co.uk/forum/forums/ (67.215.65.132): 56 data bytes
64 bytes from 67.215.65.132: icmp_seq=0 ttl=55 time=27.665 ms
64 bytes from 67.215.65.132: icmp_seq=1 ttl=55 time=29.870 ms
64 bytes from 67.215.65.132: icmp_seq=2 ttl=55 time=36.423 ms
64 bytes from 67.215.65.132: icmp_seq=3 ttl=55 time=29.004 ms
64 bytes from 67.215.65.132: icmp_seq=4 ttl=55 time=28.738 ms
64 bytes from 67.215.65.132: icmp_seq=5 ttl=55 time=38.608 ms
64 bytes from 67.215.65.132: icmp_seq=6 ttl=55 time=40.984 ms
64 bytes from 67.215.65.132: icmp_seq=7 ttl=55 time=29.629 ms
64 bytes from 67.215.65.132: icmp_seq=8 ttl=55 time=38.489 ms
64 bytes from 67.215.65.132: icmp_seq=9 ttl=55 time=29.395 ms

--- http://www.mx5oc.co.uk/forum/forums/ ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 27.665/32.880/40.984/4.834 ms



Via OpenDNS
traceroute to http://www.mx5oc.co.uk/forum/forums/ (67.215.65.132), 64 hops max, 52 byte packets
1  192.168.0.1 (192.168.0.1)  2.533 ms  1.726 ms  1.073 ms
2  telehouse-gw4-lo2.idnet.net (212.69.63.99)  24.315 ms  73.330 ms  19.916 ms
3  telehouse-gw5-e4-400.idnet.net (212.69.63.245)  20.589 ms  21.168 ms  20.258 ms
4  gi8-27.mpd01.lon02.atlas.cogentco.com (149.6.148.205)  19.807 ms  20.228 ms  20.756 ms
5  verio.lon02.atlas.cogentco.com (130.117.14.174)  115.548 ms  196.973 ms  213.751 ms
6  ae-1.r23.londen03.uk.bb.gin.ntt.net (129.250.5.237)  23.037 ms  19.939 ms  19.811 ms
7  as-3.r22.amstnl02.nl.bb.gin.ntt.net (129.250.4.19)  38.922 ms  27.967 ms  27.895 ms
8  po-1.r01.amstnl02.nl.bb.gin.ntt.net (129.250.4.71)  36.170 ms  27.592 ms  36.895 ms
9  opendns-0.r01.amstnl02.nl.bb.gin.ntt.net (81.20.64.82)  35.693 ms  28.635 ms  27.591 ms
10 *

Via IDNet DNS

Traceroute has started...

traceroute: unknown host http://www.mx5oc.co.uk/forum/forums/

Both fail although one does get further than the other.

[Gary]

And now I can.

And now I cant again  

[Glenn]

I can get on to the website, but not the forum, Steve.

[Rik]

 

[Gary]

If someone could ping the same site with Norton DNS and it stops at what looks like an Amsterdam server could that be the issue?

[armadillo]

Periodically a whole host of websites do not respond / time out and then the next refresh are fine. This is still going on as I write this post though it is not so frequent to be 'crippling'.

I am getting exactly that too today. I have tried changing DNS from IDNET to Norton, and switching the order of primary and secondary. No difference.

I don't think it's a DNS issue though. While Firefox is trying to load the page, I get "Waiting for [url]" in the status line and then eventually the page times out or the connection is reset.

DNS errors, on the other hand, tend to give "Looking up [url]" in the status line.

These suggest that the DNS is resolved but times out after it has been resolved.

As esh says, refreshing the page provides instant successful loading. Sometimes, several refreshes are needed.

[Rik]

If someone could ping the same site with Norton DNS and it stops at what looks like an Amsterdam server could that be the issue?

Are you volunteering?

[pctech]

Hi folks

I'll try running some tests tonight when I get home about 9, if someone could PM me a list of sites I'm happy to report back for comparison with a non-IDNet connection so that you can determine whether its Akamai?

[Gary]

I am getting exactly that too today. I have tried changing DNS from IDNET to Norton, and switching the order of primary and secondary. No difference.

I don't think it's a DNS issue though. While Firefox is trying to load the page, I get "Waiting for [url]" in the status line and then eventually the page times out or the connection is reset.

DNS errors, on the other hand, tend to give "Looking up [url]" in the status line.

These suggest that the DNS is resolved but times out after it has been resolved.

As esh says, refreshing the page provides instant successful loading. Sometimes, several refreshes are needed.

Very true, this morning I could not get through to apple but literally hitting the link three times in a row did it, I could not get much at all through Nortons DNS in the end so went back to idnets which right now is the best of the bunch.

[Glenn]

http://www.shareprice.co.uk is slow to resolve.