Sites not working

[sof2er]

Same here (FTTC) some sites won't load at all.

[Gary]

And PC-Pals. On the phone...

working on the phone 

[Rik]

One of the resolvers is playing up - being worked on as I type.

[Gary]

One of the resolvers is playing up - being worked on as I type.

You said it was a quite day to early, Rik 

[jameshurrell]

Yep had two bouts of this wierdness - just before lunch my VPN to the office dropped out, but MSN and Skype stayed up. I use OpenDNS routinely but couldn't get to their website at all. Thought it was them so after some faffing around switched to IDnet DNS servers - this resolved it. So, OpenDNS was the culprit i thought - but nothing on their forums or status. However, the same thing has just happened. I've once again switched to IDNet DNS and some sites work (this one) and some don't... VPN to office has dropped again but SKype/MSN are up. Obviously the first time around the problem had been sorted by the time I switched to IDNet DNS...

I use the IDnet RSS feed, but there's nothing in there.

[Rik]

You said it was a quite day to early, Rik 

[Bill]

The number of users online is looking healthy again

[Gary]

Thats because its like browsing through Treacle 

[Rik]

Every cloud, Bill.

[kinmel]

I am having a lot of DNS problems today too.

However, I am using OpenDNS  and through Idnet on my netbook, Pings  to 208.67.220.220 (openDNS servers ) fail and tracerts time out after the first hop 212.66.63.99.

Doing the same thing on the same netbook through my neighbours Talktalk connection, there is no problem at all.

[Rik]

That's odd. Have you told support, Alan?

[jameshurrell]

I use OpenDNS too Alan, but have only seen issues twice today. When the problem at IDNet has occurred (just before lunch and just before 4pm) it affects my ability to connect to the OpenDNS DNS servers, rendering the connection completely useless. Switching to IDNet DNS opens up a bit more, but still 50% of sites (at a rough guess) don't work.

Edit: Like Alan, a tracert to one of the OpenDNS IP addresses times out after second hop 212.66.63.99.

[Gary]

Lost Myspace and Mobog again Cant sign in on the Playstaiton either now

[vitriol]

Browsing has been a pit slow this afternoon, but I see that one of the resolvers is playing up - thanks Rik for the info. 

[Rik]

NP. It should be returning to normal now.

[.Griff.]

One of the resolvers is playing up - being worked on as I type.

How/Why would that affect those of us using OpenDNS or Google DNS?

[Glenn]

The traffic has to go through IDNet, before it reaches the outside world. I would think the resolver needs to know where to send the packets once you click on the links,

[Rik]

It shouldn't. Having checked the suspect resolver, it now looks like it's an intermittent external routing problem. This causes routes to be re-broadcast at frequent intervals, causing the problem. IDNet are working to identify the external route so they can bypass it.

[Reya]

I'm getting packet loss, high pings and timeouts all over the place. Bah! LiveJournal, Wordpress, Second Life, Twitter, Gmail. Flickr. The whole internets is playing hide and seek

Pings and tracerts from just two of those:

C:\Users\Reya>ping www.wordpress.com

Pinging lb.wordpress.com [74.200.244.59] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 74.200.244.59:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Reya>tracert www.wordpress.com

Tracing route to lb.wordpress.com [74.200.244.59]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    49 ms    33 ms    33 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
(etc etc, over all 30 hops.)

C:\Users\Reya>ping livejournal.com

Pinging livejournal.com [208.93.0.128] with 32 bytes of data:
Request timed out.
Reply from 208.93.0.128: bytes=32 time=180ms TTL=239
Request timed out.
Reply from 208.93.0.128: bytes=32 time=181ms TTL=239

Ping statistics for 208.93.0.128:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 180ms, Maximum = 181ms, Average = 180ms

C:\Users\Reya>tracert livejournal.com

Tracing route to livejournal.com [208.93.0.128]
over a maximum of 30 hops:

  1     2 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    30 ms    32 ms    30 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    28 ms    28 ms    28 ms  telehouse-gw5-lo1.idnet.net [212.69.63.245]
  4    31 ms    31 ms    29 ms  gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148
.205]
  5   167 ms   203 ms   199 ms  te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50
.117]
  6   114 ms   108 ms   107 ms  te0-5-0-1.ccr22.jfk02.atlas.cogentco.com [154.54
.30.134]
  7   119 ms   121 ms   112 ms  te0-2-0-7.ccr22.dca01.atlas.cogentco.com [154.54
.41.9]
  8   111 ms   110 ms   115 ms  te0-0-0-5.ccr22.iad02.atlas.cogentco.com [154.54
.30.126]
  9   112 ms   133 ms   114 ms  qwest.iad01.atlas.cogentco.com [154.54.10.26]
10   180 ms   175 ms   189 ms  bil-core-02.inet.qwest.net [205.171.8.154]
11   189 ms   184 ms   187 ms  bil-edge-02.inet.qwest.net [205.171.154.22]
12   181 ms   181 ms   180 ms  65.121.112.210
13   182 ms     *        *     livejournal.com [208.93.0.128]
14   194 ms   183 ms   182 ms  livejournal.com [208.93.0.128]

Trace complete.

[Rik]

See above.

[kinmel]

How/Why would that affect those of us using OpenDNS or Google DNS?

It cannot be the resolver, I am typing in IP addresses and failing.

I can't even contact Support by telephone, 0800 701 2000 gets an answerphone and 01462 476 555 is unobtainable.  

The Idnet site is unreachable through Idnet and Talktalk

[tomharrison]

Same issues here with both OpenDNS and IDNet's servers. Network status page just updated:

Network Status

2010-09-07 16:37: There have been a couple of network routing issues this afternoon that we are working to resolve.

[Rik]

Phones are in meltdown, Alan, they're a man short and those who would normally step in to help are trying to fix the problem.

I can reach the site fine, but the problem is intermittent...

[Reya]

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 

[Gary]

I'm going to go kill some Helgans and take out my frustration on the PS3