DNS/Routing/Something problem?

Hello,

Is anyone else having "problems" this evening? I'm finding that sometimes I can't access a website... but after a few moments, then I can.
Typically the outage is so brief that by the time I've logged into my router to check it can't resolve an address, the problem has fixed itself. But I did manage to confirm it once... so I don't think its my computer!

Ping times all seem fine.

The router log doesn't actually show any issues; the connection is holding up. I did warm-boot the router and it didn't want to authenticate (or whatever) immediately:

Sun, 2002-09-08 12:00:20 - Administrator login successful - IP:192.168.0.40
Sun, 2002-09-08 12:00:22 - Initialize LCP.
Sun, 2002-09-08 12:00:22 - LCP is allowed to come up.
Sun, 2002-09-08 12:00:31 - Administrator login successful - IP:192.168.0.40
Sun, 2002-09-08 12:01:05 - LCP down.
Sun, 2002-09-08 12:01:22 - Initialize LCP.
Sun, 2002-09-08 12:01:23 - LCP is allowed to come up.
Sun, 2002-09-08 12:01:28 - CHAP authentication success
Sun, 2002-09-08 12:01:35 - Send out NTP request to time-g.netgear.com
Wed, 2006-10-04 19:03:07 - Receive NTP Reply from time-g.netgear.com

Most likely if I just leave it, it will all be working by tomorrow, but I find it unnerving when I don't see anyone else complaining!!

Cheers,

Peter.

Your not the only one, im getting the same and so is a mate on idnet aswell. Irritating.

Yes, same here. It's the hop after sl-bb21-lon-3-0.sprintlink.net that's the problem - when sites are working the IP is 213.206.131.22 ; it doesn't resolve to anything, but the hop after that is on level3.

Yup, I'm seeing it as well. As you say, nothing obviously wrong, but but a site won't load for a few minutes. No obvious pattern...

At least I'm not alone... which does make me feel better!

Despite what I said before about pings being ok, some tracert 's look to me a little poor compared to normal:

Tracing route to reference.com [66.161.12.84]

over a maximum of 30 hops:



  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]

  2    23 ms    22 ms    20 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]

  3    21 ms    22 ms    24 ms  telehouse-gw-bb.idnet.net [212.69.63.9]

  4    22 ms    23 ms     *     g-s-1.lon1.arbinet.net [213.232.64.51]

  5     *        *        *     Request timed out.

  6    91 ms    90 ms    93 ms  sl-bb20-nyc-2-0.sprintlink.net [144.232.9.163]

  7    91 ms    92 ms    89 ms  sl-bb26-nyc-6-0.sprintlink.net [144.232.13.9]

  8    90 ms    97 ms    99 ms  144.232.8.194

  9   164 ms     *      166 ms  tbr1033301.n54ny.ip.att.net [12.123.0.98]

 10   160 ms   163 ms   162 ms  tbr1-cl14.cgcil.ip.att.net [12.122.10.2]

 11     *      164 ms   162 ms  tbr2-cl22.cgcil.ip.att.net [12.122.9.134]

 12   160 ms   167 ms   162 ms  tbr2-cl7.sl9mo.ip.att.net [12.122.10.46]

 13   164 ms   162 ms   164 ms  tbr2-cl21.la2ca.ip.att.net [12.122.10.14]

 14   163 ms   158 ms     *     12.127.3.205

 15   159 ms   159 ms   159 ms  12.122.79.106

 16   161 ms   161 ms   164 ms  bb1-p6-0.crrvca.sbcglobal.net [151.164.41.34]

 17   168 ms   165 ms     *     core2-p9-0.crrvca.sbcglobal.net [151.164.40.253]

 18   161 ms   163 ms   162 ms  bb2-p5-1.irvnca.sbcglobal.net [151.164.42.74]

 19   169 ms     *      166 ms  ded1-g7-0-0.irvnca.sbcglobal.net [151.164.42.35]

 20   163 ms   167 ms   162 ms  bb2-z-g1-0-0.irv.sbcidc.com [66.161.96.25]

 21     *      167 ms   166 ms  core2-z-g2-1.irv.sbcidc.com [216.65.209.18]

 22   167 ms   168 ms     *     acs2-a-g2-1.irv.sbcidc.com [216.65.208.110]

 23   167 ms     *      164 ms  66.161.12.84



Trace complete.





Tracing route to www.slashdot.org [66.35.250.151]

over a maximum of 30 hops:



  1     1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]

  2    27 ms    27 ms    32 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]

  3    44 ms    46 ms    46 ms  telehouse-gw-bb.idnet.net [212.69.63.9]

  4    29 ms    42 ms    47 ms  g-s-1.lon1.arbinet.net [213.232.64.51]

  5    29 ms    32 ms     *     sl-bb22-lon-9-0.sprintlink.net [213.206.128.104]

  6    37 ms    40 ms    28 ms  bcr1-so-5-0-0.Londonlnx.savvis.net [206.24.169.41]

  7    30 ms    31 ms     *     bcs1-so-1-1-0.Londonlnx.savvis.net [204.70.193.114]

  8    33 ms   101 ms    30 ms  bcs1-as0-0.Londonlnx.savvis.net [204.70.193.201]

  9   113 ms   107 ms     *     bcs1-so-6-0-0.NewYork.savvis.net [204.70.192.37]

 10   121 ms   122 ms   117 ms  bcs2-so-4-0-0.Washington.savvis.net [204.70.192.1]

 11   146 ms   122 ms     *     dcr2-so-7-1-0.Atlanta.savvis.net [204.70.192.61]

 12   170 ms   139 ms   169 ms  dcr1-so-7-2-0.losangeles.savvis.net [204.70.192.245]

 13   188 ms   141 ms   185 ms  dcr2-so-2-0-0.SanFranciscosfo.savvis.net [204.70.192.90]

 14   172 ms   167 ms   179 ms  bhr1-pos-0-0.SantaClarasc8.savvis.net [208.172.156.198]

 15   186 ms   187 ms   183 ms  csr1-ve243.santaclarasc8.savvis.net [66.35.194.50]

 16   189 ms   186 ms   183 ms  dcr2-so-5-0-0.SanFranciscosfo.savvis.net [204.70.192.150]

 17   174 ms     *      176 ms  bhr1-pos-0-0.SantaClarasc8.savvis.net [208.172.156.198]

 18     *        *      183 ms  csr1-ve243.santaclarasc8.savvis.net [66.35.194.50]

 19     *        *        *     Request timed out.

 20     *        *        *     Request timed out.

 21     *     ^C

so maybe it's a problem upstream somewhere?

Hi All

We have noticed instability across the London XchangePoint network so we have shutdown our connection to there for the time being.

Regards
Simon

Thanks Simon!!

Hi ive noticed it too im in central London and i noticed on the news page here that BT are doing work here but they said between 12 and 6am though dont know if that would have anything to do with it.