Sites not working

[Rik]

Thanks, Rik. I've no idea what a resolver is, apart from something horribly techie that's going to go whooshing over my head (well, not literally), so I guess I'll just make a cuppa and find one of those papery things to amuse myself with while I wait it out. Books, I think they're called 

The resolver is the DNS nameserver, the bit that translates the www.xxx into an IP address. However, it now appears that it's an external problem to IDNet, with one of the peers dropping intermittently. When that happens, all the IP addresses have to be re-routed, which takes time and cause the slow access or lack of access. Being intermittent, of course, it's proving a bit more difficult to find and bypass.

[psp83]

Thanks, Rik. I've no idea what a resolver is, apart from something horribly techie that's going to go whooshing over my head (well, not literally)

Well that all depends how far you live from IDnet's HQ and how pee'd off Simon / Tim gets and can throw the damn thing! 

[zappaDPJ]

I currently have a couple of RSS feeds not responding including one from the BBC. Everything else seems to be working though.

[Reya]

The resolver is the DNS nameserver, the bit that translates the www.xxx into an IP address. However, it now appears that it's an external problem to IDNet, with one of the peers dropping intermittently. When that happens, all the IP addresses have to be re-routed, which takes time and cause the slow access or lack of access. Being intermittent, of course, it's proving a bit more difficult to find and bypass.

Thank you! Makes sense now

Well that all depends how far you live from IDnet's HQ and how pee'd off Simon / Tim gets and can throw the damn thing! 

I suppose sandbags and a blankie fort won't protect me? (I'm going! I'm going! )

[Glenn]

 

[Rik]

[jezuk1]

I almost logged into WoW, and then was DC'd, but some progress  

[Desaan]

Wondered what was going on, I thought it was the thunderstorm that has been going on for a few hours - hope it gets sorted soon I'm getting earache, "The internet has stopped working!"


*Fixcus Internetus!*

[.Griff.]

It shouldn't. Having checked the suspect resolver, it now looks like it's an intermittent external routing problem.

That sounds more like the problem. Latency has been on the increase since lunchtime I notice which I guess would be a result of routing issues.

[Rik]

Sounds probable. It's been a fun-filled few days hasn't it. 

[Conrad]

OMFG....  Just had a peep at the network status page.  We are going to have a SIX hour outage tomorrow night!??  NOOOoooooooo.  

Oi!  BT!  

[Glenn]

You can see the packet loss increase on my graph

[.Griff.]

You can see the packet loss increase on my graph

Same -

[Rik]

OMFG....  Just had a peep at the network status page.  We are going to have a SIX hour outage tomorrow night!??  NOOOoooooooo. 

Oi!  BT!   

'Fraid so, though whether it will affect everyone or last that long is moot. BT tend to paint a 'worst case scenario' with this kind of work.

[Ray]

Similar here with mine, not quite as bad as yours, Glenn, Ping graph

[jameshurrell]

Same here for packet loss:

[Glenn]

The packet loss looks the same across all the graphs.

[Ardua]

Like others, I have waited patiently over the past few days for commonly used sites to load. Geocaching.com is the latest one to 'hang'. I confess that I do not know what a traceroute shows but here are the details. Any thoughts?   


Traceroute has started...

traceroute to www.geocaching.com (66.150.167.189), 64 hops max, 52 byte packets
1  www.routerlogin.com (192.168.0.1)  2.324 ms  1.521 ms  1.613 ms
2  telehouse-gw4-lo2.idnet.net (212.69.63.99)  33.596 ms  33.917 ms  32.971 ms
3  telehouse-gw5-lo1.idnet.net (212.69.63.245)  33.982 ms  32.850 ms  32.677 ms
4  gi8-27.mpd01.lon02.atlas.cogentco.com (149.6.148.205)  35.579 ms  33.592 ms  33.250 ms
5  te1-2.ccr02.lon02.atlas.cogentco.com (130.117.50.117)  40.034 ms
    te1-2.ccr01.lon02.atlas.cogentco.com (130.117.50.138)  33.624 ms
    te1-2.ccr02.lon02.atlas.cogentco.com (130.117.50.117)  35.240 ms
6  te0-1-0-5.ccr21.ymq02.atlas.cogentco.com (38.109.18.125)  112.438 ms
    154.54.42.46 (154.54.42.46)  119.203 ms
    154.54.42.49 (154.54.42.49)  109.936 ms
7  te0-0-0-6.mpd21.ord01.atlas.cogentco.com (38.20.46.9)  147.041 ms
    te0-2-0-6.ccr21.ord01.atlas.cogentco.com (154.54.30.238)  135.648 ms
    te0-2-0-6.mpd21.ord01.atlas.cogentco.com (154.54.30.234)  137.447 ms
8  multi-use.cogentco.com (154.54.25.81)  150.689 ms
    te0-0-0-3.mpd21.mci01.atlas.cogentco.com (154.54.2.233)  149.224 ms
    te0-0-0-3.ccr21.mci01.atlas.cogentco.com (154.54.2.217)  147.063 ms
9  te4-4.mpd01.den01.atlas.cogentco.com (154.54.24.81)  162.970 ms  159.297 ms
    te4-4.mpd02.den01.atlas.cogentco.com (154.54.7.130)  162.514 ms
10  te4-2.ccr01.slc01.atlas.cogentco.com (154.54.0.42)  166.737 ms
    te3-2.ccr01.slc01.atlas.cogentco.com (154.54.3.14)  178.726 ms
    te4-2.ccr01.slc01.atlas.cogentco.com (154.54.0.42)  171.786 ms
11  te7-3.ccr01.smf01.atlas.cogentco.com (66.28.4.194)  181.596 ms
    te4-2.ccr01.smf01.atlas.cogentco.com (154.54.1.101)  183.539 ms
    te7-3.ccr01.smf01.atlas.cogentco.com (66.28.4.194)  182.417 ms
12  te4-3.ccr01.sea01.atlas.cogentco.com (154.54.40.106)  197.373 ms  196.867 ms  196.574 ms
13  te4-2.ccr01.sea03.atlas.cogentco.com (154.54.41.146)  198.659 ms  199.115 ms  197.782 ms
14  regus-business-center.demarc.cogentco.com (38.104.124.82)  197.101 ms  196.255 ms  197.762 ms
15  border8.t8-1-bbnet2.sef.pnap.net (63.251.160.82)  199.400 ms  197.167 ms  200.563 ms
16  * *

Ping has started...

PING www.geocaching.com (66.150.167.189): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8

--- www.geocaching.com ping statistics ---
10 packets transmitted, 0 packets received, 100.0% packet loss

[Bill]

They're all looking similar to the second one I gave here... the routers are sending some of us on the scenic route

[Rik]

And it's not even Scotland.

[Ardua]

And .... the solution is?

[kinmel]

And .... the solution is?

far away 

[Bill]

And .... the solution is?

I think it has to be- wait until IDNet get it fixed.

FWIW, Geocaching.com works fine for me

[Rik]

There are no updates atm, they are working as quickly as possible to resolve the issue.

[psp83]

There are no updates atm, they are working as quickly as possible to resolve the issue.

Looks like some overtime needed tonight