Anyone else got a connection problem

[Luke]

Came home from school to find that no websites work EXCEPT habbox :S.
Phoned ISP and they said there was a major outage or something

Anyone else aving any problems?

[scottish]

nope mines fine, what ISP?

[marriott0.01]

Mines fine aswell, we had a small problem this morning but nothing since.

As entrance said, what ISP?

[Luke]

AOL -longer-

[marriott0.01]

I'm on AOL aswell, it could be a problem with your exchange, which means it'd only be local.

[Luke]

that's what i thought at first, because w've just had 15cm of snow in last 2 hours.


But thety said in words "we've got a major outage" so dunno what's wrong

[scottish]

don't they have a server status kinda thing, like virgin has a page which shows up to date problems in areas.
http://status-cable.virginmedia.com/vmstatus/summary.do

[Luke]

i don't know
but i can't get on the AOL site anyway
i've found ONE search engine that works..
ask.com

[marriott0.01]

AOL UK is owned by Carphonewarehouse, so probably not, as we all know carphonewarehouse don't like to tell customers anything :P

[c[__]]

I'm on AOL and our net ****** up other day and my dad phoned and they said something happend all over the UK or around them lines.

[Jamieb]

Hey i having that problem..

It happen on Saturday I rang them up on Sunday spoke to 3 people who clearly was not in the uk they told me it was a problem there and it may take a few days so i just told them im moving so think im going with o2.

[scottish]

Virgin/be* ftw

[marriott0.01]

I've always been satisfied with AOL, but then again I'm easily satisfied

[N!ck]

Try using different DNS servers. It could be an AOL DNS problem which would explain the working of only certain websites. I recommend OpenDNS - 208.67.222.222 and 208.67.220.220

[Luke]

when i put them DNS in my router config, and it couldn't connect

[scottish]

http://www.opendns.com/

[N!ck]

when i put them DNS in my router config, and it couldn't connect

Tyr putting them in through your TCP/IP settings on your NIC.

[Luke]

nope, still not workling.
Although, if i use a proxy, i can get onto other sites :S

[Tomm]

Same issue here.

Heres a example trace route to the BBC news website:

C:\Users\Tom>tracert news.bbc.co.uk
Tracing route to newswww.bbc.net.uk [212.58.226.20]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.1
2 21 ms 21 ms 22 ms host-92-8-192-1.as43234.net [92.8.192.1]
3 20 ms 21 ms 20 ms 92.31.253.68
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.

It times out shortly after getting past my router.

Oh and as for a stable connection:



Tue, 2009-02-10 10:24:29 - LCP is allowed to come up.
Tue, 2009-02-10 10:24:32 - CHAP authentication success
Tue, 2009-02-10 10:24:40 - <DDNS>Update OK: good
Tue, 2009-02-10 10:40:11 - LCP down.
Tue, 2009-02-10 10:40:14 - Initialize LCP.
Tue, 2009-02-10 10:40:14 - LCP is allowed to come up.
Tue, 2009-02-10 10:40:17 - CHAP authentication success
Tue, 2009-02-10 10:40:25 - <DDNS>Update OK: good
Tue, 2009-02-10 10:51:47 - LCP down.
Tue, 2009-02-10 10:51:49 - Initialize LCP.
Tue, 2009-02-10 10:51:49 - LCP is allowed to come up.
Tue, 2009-02-10 10:51:52 - CHAP authentication success
Tue, 2009-02-10 10:51:59 - <DDNS>Update OK: good
Tue, 2009-02-10 10:55:12 - LCP down.
Tue, 2009-02-10 10:55:14 - Initialize LCP.
Tue, 2009-02-10 10:55:14 - LCP is allowed to come up.
Tue, 2009-02-10 10:55:17 - CHAP authentication success
Tue, 2009-02-10 10:55:26 - <DDNS>Update OK: good
Tue, 2009-02-10 11:26:56 - LCP down.
Tue, 2009-02-10 11:26:59 - Initialize LCP.
Tue, 2009-02-10 11:26:59 - LCP is allowed to come up.
Tue, 2009-02-10 11:27:02 - CHAP authentication success
Tue, 2009-02-10 11:27:10 - <DDNS>Update OK: good
Tue, 2009-02-10 12:52:32 - LCP down.
Tue, 2009-02-10 12:52:34 - Initialize LCP.
Tue, 2009-02-10 12:52:34 - LCP is allowed to come up.
Tue, 2009-02-10 12:52:37 - CHAP authentication success
Tue, 2009-02-10 12:52:45 - <DDNS>Update OK: good
Tue, 2009-02-10 13:18:06 - LCP down.
Tue, 2009-02-10 13:18:09 - Initialize LCP.
Tue, 2009-02-10 13:18:09 - LCP is allowed to come up.
Tue, 2009-02-10 13:18:11 - CHAP authentication success
Tue, 2009-02-10 13:18:19 - <DDNS>Update OK: good
Tue, 2009-02-10 13:53:21 - LCP down.
Tue, 2009-02-10 13:53:23 - Initialize LCP.
Tue, 2009-02-10 13:53:24 - LCP is allowed to come up.
Tue, 2009-02-10 13:53:27 - CHAP authentication success
Tue, 2009-02-10 13:53:34 - <DDNS>Update OK: good
Tue, 2009-02-10 14:01:16 - LCP down.
Tue, 2009-02-10 14:01:18 - Initialize LCP.
Tue, 2009-02-10 14:01:18 - LCP is allowed to come up.
Tue, 2009-02-10 14:01:21 - CHAP authentication success
Tue, 2009-02-10 14:01:29 - <DDNS>Update OK: good
Tue, 2009-02-10 14:21:31 - LCP down.
Tue, 2009-02-10 14:21:33 - Initialize LCP.
Tue, 2009-02-10 14:21:34 - LCP is allowed to come up.
Tue, 2009-02-10 14:21:36 - CHAP authentication success
Tue, 2009-02-10 14:21:44 - <DDNS>Update OK: good
Tue, 2009-02-10 15:06:46 - LCP down.
Tue, 2009-02-10 15:06:48 - Initialize LCP.
Tue, 2009-02-10 15:06:48 - LCP is allowed to come up.
Tue, 2009-02-10 15:06:51 - CHAP authentication success
Tue, 2009-02-10 15:38:51 - LCP down.
Tue, 2009-02-10 15:38:53 - Initialize LCP.
Tue, 2009-02-10 15:38:53 - LCP is allowed to come up.
Tue, 2009-02-10 15:38:56 - CHAP authentication success
Tue, 2009-02-10 15:39:05 - <DDNS>Update OK: good
Tue, 2009-02-10 16:04:46 - LCP down.
Tue, 2009-02-10 16:04:48 - Initialize LCP.
Tue, 2009-02-10 16:04:48 - LCP is allowed to come up.
Tue, 2009-02-10 16:04:51 - CHAP authentication success
Tue, 2009-02-10 16:04:59 - <DDNS>Update OK: good
Tue, 2009-02-10 16:49:31 - LCP down.
Tue, 2009-02-10 16:49:33 - Initialize LCP.
Tue, 2009-02-10 16:49:33 - LCP is allowed to come up.
Tue, 2009-02-10 16:49:36 - CHAP authentication success
Tue, 2009-02-10 16:49:44 - <DDNS>Update OK: good
Tue, 2009-02-10 19:28:26 - LCP down.
Tue, 2009-02-10 19:28:28 - Initialize LCP.
Tue, 2009-02-10 19:28:28 - LCP is allowed to come up.
Tue, 2009-02-10 19:28:31 - CHAP authentication success
Tue, 2009-02-10 19:28:39 - <DDNS>Update OK: good
Tue, 2009-02-10 23:13:41 - LCP down.
Tue, 2009-02-10 23:13:43 - Initialize LCP.
Tue, 2009-02-10 23:13:43 - LCP is allowed to come up.
Tue, 2009-02-10 23:13:46 - CHAP authentication success
Tue, 2009-02-10 23:13:54 - <DDNS>Update OK: good
Tue, 2009-02-10 23:23:25 - LCP down.
Tue, 2009-02-10 23:23:28 - Initialize LCP.
Tue, 2009-02-10 23:23:28 - LCP is allowed to come up.
Tue, 2009-02-10 23:23:30 - CHAP authentication success
Tue, 2009-02-10 23:23:38 - <DDNS>Update OK: good
Tue, 2009-02-10 23:58:50 - LCP down.
Tue, 2009-02-10 23:58:52 - Initialize LCP.
Tue, 2009-02-10 23:58:53 - LCP is allowed to come up.
Tue, 2009-02-10 23:58:56 - CHAP authentication success
Tue, 2009-02-10 23:59:04 - <DDNS>Update OK: good
Wed, 2009-02-11 00:50:45 - LCP down.
Wed, 2009-02-11 00:50:48 - Initialize LCP.
Wed, 2009-02-11 00:50:48 - LCP is allowed to come up.
Wed, 2009-02-11 00:50:50 - CHAP authentication success
Wed, 2009-02-11 00:50:58 - <DDNS>Update OK: good
Wed, 2009-02-11 02:10:30 - LCP down.
Wed, 2009-02-11 02:10:32 - Initialize LCP.
Wed, 2009-02-11 02:10:33 - LCP is allowed to come up.
Wed, 2009-02-11 02:10:35 - CHAP authentication success
Wed, 2009-02-11 02:10:43 - <DDNS>Update OK: good
Wed, 2009-02-11 03:18:25 - LCP down.
Wed, 2009-02-11 03:18:27 - Initialize LCP.
Wed, 2009-02-11 03:18:27 - LCP is allowed to come up.
Wed, 2009-02-11 03:18:30 - CHAP authentication success
Wed, 2009-02-11 03:18:38 - <DDNS>Update OK: good
Wed, 2009-02-11 03:20:50 - LCP down.
Wed, 2009-02-11 03:20:52 - Initialize LCP.
Wed, 2009-02-11 03:20:52 - LCP is allowed to come up.
Wed, 2009-02-11 03:20:55 - CHAP authentication success
Wed, 2009-02-11 03:21:03 - <DDNS>Update OK: good
Wed, 2009-02-11 03:35:35 - LCP down.
Wed, 2009-02-11 03:35:37 - Initialize LCP.
Wed, 2009-02-11 03:35:37 - LCP is allowed to come up.
Wed, 2009-02-11 03:35:40 - CHAP authentication success
Wed, 2009-02-11 03:35:48 - <DDNS>Update OK: good
Wed, 2009-02-11 03:50:40 - LCP down.
Wed, 2009-02-11 03:50:42 - Initialize LCP.
Wed, 2009-02-11 03:50:42 - LCP is allowed to come up.
Wed, 2009-02-11 03:50:45 - CHAP authentication success
Wed, 2009-02-11 03:50:52 - <DDNS>Update OK: good
Wed, 2009-02-11 05:18:15 - LCP down.
Wed, 2009-02-11 05:18:17 - Initialize LCP.
Wed, 2009-02-11 05:18:17 - LCP is allowed to come up.
Wed, 2009-02-11 05:18:20 - CHAP authentication success
Wed, 2009-02-11 05:18:28 - <DDNS>Update OK: good
Wed, 2009-02-11 06:51:49 - LCP down.
Wed, 2009-02-11 06:51:51 - Initialize LCP.
Wed, 2009-02-11 06:51:52 - LCP is allowed to come up.
Wed, 2009-02-11 06:52:07 - CHAP authentication failed
Wed, 2009-02-11 06:52:07 - LCP down.
Wed, 2009-02-11 06:52:52 - Initialize LCP.
Wed, 2009-02-11 06:52:52 - LCP is allowed to come up.
Wed, 2009-02-11 06:53:13 - CHAP authentication failed
Wed, 2009-02-11 06:53:13 - LCP down.
Wed, 2009-02-11 06:53:53 - Initialize LCP.
Wed, 2009-02-11 06:53:53 - LCP is allowed to come up.
Wed, 2009-02-11 06:54:02 - CHAP authentication failed
Wed, 2009-02-11 06:54:02 - LCP down.
Wed, 2009-02-11 06:54:53 - Initialize LCP.
Wed, 2009-02-11 06:54:54 - LCP is allowed to come up.
Wed, 2009-02-11 06:55:02 - CHAP authentication failed
Wed, 2009-02-11 06:55:02 - LCP down.
Wed, 2009-02-11 06:55:54 - Initialize LCP.
Wed, 2009-02-11 06:55:54 - LCP is allowed to come up.
Wed, 2009-02-11 06:56:09 - CHAP authentication failed
Wed, 2009-02-11 06:56:09 - LCP down.
Wed, 2009-02-11 06:56:55 - Initialize LCP.
Wed, 2009-02-11 06:56:55 - LCP is allowed to come up.
Wed, 2009-02-11 06:57:56 - Initialize LCP.
Wed, 2009-02-11 06:57:56 - LCP is allowed to come up.
Wed, 2009-02-11 06:58:56 - Initialize LCP.
Wed, 2009-02-11 06:58:56 - LCP is allowed to come up.
Wed, 2009-02-11 06:59:17 - CHAP authentication failed
Wed, 2009-02-11 06:59:17 - LCP down.
Wed, 2009-02-11 06:59:57 - Initialize LCP.
Wed, 2009-02-11 06:59:57 - LCP is allowed to come up.
Wed, 2009-02-11 07:00:25 - CHAP authentication failed
Wed, 2009-02-11 07:00:25 - LCP down.
Wed, 2009-02-11 07:00:58 - Initialize LCP.
Wed, 2009-02-11 07:00:58 - LCP is allowed to come up.
Wed, 2009-02-11 07:01:26 - CHAP authentication failed
Wed, 2009-02-11 07:01:26 - LCP down.
Wed, 2009-02-11 07:01:58 - Initialize LCP.
Wed, 2009-02-11 07:01:59 - LCP is allowed to come up.
Wed, 2009-02-11 07:02:26 - CHAP authentication failed
Wed, 2009-02-11 07:02:27 - LCP down.
Wed, 2009-02-11 07:02:59 - Initialize LCP.
Wed, 2009-02-11 07:02:59 - LCP is allowed to come up.
Wed, 2009-02-11 07:03:28 - CHAP authentication failed
Wed, 2009-02-11 07:03:28 - LCP down.
Wed, 2009-02-11 07:04:00 - Initialize LCP.
Wed, 2009-02-11 07:04:00 - LCP is allowed to come up.
Wed, 2009-02-11 07:05:00 - Initialize LCP.
Wed, 2009-02-11 07:05:01 - LCP is allowed to come up.
Wed, 2009-02-11 07:05:29 - CHAP authentication failed
Wed, 2009-02-11 07:05:29 - LCP down.
Wed, 2009-02-11 07:06:01 - Initialize LCP.
Wed, 2009-02-11 07:06:01 - LCP is allowed to come up.
Wed, 2009-02-11 07:06:27 - CHAP authentication failed
Wed, 2009-02-11 07:06:27 - LCP down.
Wed, 2009-02-11 07:07:02 - Initialize LCP.
Wed, 2009-02-11 07:07:02 - LCP is allowed to come up.
Wed, 2009-02-11 07:07:30 - CHAP authentication failed
Wed, 2009-02-11 07:07:30 - LCP down.
Wed, 2009-02-11 07:08:03 - Initialize LCP.
Wed, 2009-02-11 07:08:03 - LCP is allowed to come up.
Wed, 2009-02-11 07:08:31 - CHAP authentication failed
Wed, 2009-02-11 07:08:31 - LCP down.
Wed, 2009-02-11 07:09:03 - Initialize LCP.
Wed, 2009-02-11 07:09:03 - LCP is allowed to come up.
Wed, 2009-02-11 07:10:04 - Initialize LCP.
Wed, 2009-02-11 07:10:04 - LCP is allowed to come up.
Wed, 2009-02-11 07:10:58 - CHAP authentication success
Wed, 2009-02-11 07:21:05 - Initialize LCP.
Wed, 2009-02-11 07:21:05 - LCP is allowed to come up.
Wed, 2009-02-11 07:21:33 - CHAP authentication failed
Wed, 2009-02-11 07:21:33 - LCP down.
Wed, 2009-02-11 07:22:05 - Initialize LCP.
Wed, 2009-02-11 07:22:06 - LCP is allowed to come up.
Wed, 2009-02-11 07:22:33 - CHAP authentication failed
Wed, 2009-02-11 07:22:33 - LCP down.
Wed, 2009-02-11 07:23:06 - Initialize LCP.
Wed, 2009-02-11 07:23:06 - LCP is allowed to come up.
Wed, 2009-02-11 07:23:35 - CHAP authentication failed
Wed, 2009-02-11 07:23:35 - LCP down.
Wed, 2009-02-11 07:24:07 - Initialize LCP.
Wed, 2009-02-11 07:24:07 - LCP is allowed to come up.
Wed, 2009-02-11 07:24:34 - CHAP authentication failed
Wed, 2009-02-11 07:24:34 - LCP down.
Wed, 2009-02-11 07:25:07 - Initialize LCP.
Wed, 2009-02-11 07:25:08 - LCP is allowed to come up.
Wed, 2009-02-11 07:25:16 - CHAP authentication failed
Wed, 2009-02-11 07:25:16 - LCP down.
Wed, 2009-02-11 07:26:08 - Initialize LCP.
Wed, 2009-02-11 07:26:08 - LCP is allowed to come up.
Wed, 2009-02-11 07:27:09 - Initialize LCP.
Wed, 2009-02-11 07:27:09 - LCP is allowed to come up.
Wed, 2009-02-11 07:28:10 - Initialize LCP.
Wed, 2009-02-11 07:28:10 - LCP is allowed to come up.
Wed, 2009-02-11 07:28:37 - CHAP authentication success
Wed, 2009-02-11 07:28:53 - LCP down.
Wed, 2009-02-11 07:28:54 - <DDNS>HTTP cannot connected
Wed, 2009-02-11 07:28:55 - Initialize LCP.
Wed, 2009-02-11 07:28:56 - LCP is allowed to come up.
Wed, 2009-02-11 07:29:21 - CHAP authentication success
Wed, 2009-02-11 08:26:38 - Send out NTP request to 128.250.36.3
Wed, 2009-02-11 08:27:58 - Send out NTP request to 132.163.4.102
Wed, 2009-02-11 08:30:08 - Send out NTP request to 128.250.36.3
Wed, 2009-02-11 08:33:58 - Send out NTP request to 132.163.4.102
Wed, 2009-02-11 08:41:08 - Send out NTP request to 128.250.36.3
Wed, 2009-02-11 08:54:58 - Send out NTP request to 132.163.4.102
Wed, 2009-02-11 09:07:40 - LCP down.
Wed, 2009-02-11 09:07:42 - Initialize LCP.
Wed, 2009-02-11 09:07:42 - LCP is allowed to come up.
Wed, 2009-02-11 09:07:45 - CHAP authentication success
Wed, 2009-02-11 09:07:53 - <DDNS>Update OK: good
Wed, 2009-02-11 09:22:08 - Send out NTP request to 128.250.36.3
Wed, 2009-02-11 10:13:05 - LCP down.
Wed, 2009-02-11 10:13:07 - Initialize LCP.
Wed, 2009-02-11 10:13:07 - LCP is allowed to come up.
Wed, 2009-02-11 10:13:10 - CHAP authentication success
Wed, 2009-02-11 10:13:18 - <DDNS>Update OK: good
Wed, 2009-02-11 10:15:58 - Send out NTP request to 132.163.4.102
Wed, 2009-02-11 10:16:40 - LCP down.
Wed, 2009-02-11 10:16:42 - Initialize LCP.
Wed, 2009-02-11 10:16:42 - LCP is allowed to come up.
Wed, 2009-02-11 10:16:45 - CHAP authentication success
Wed, 2009-02-11 10:16:53 - <DDNS>Update OK: good
Wed, 2009-02-11 11:22:05 - LCP down.
Wed, 2009-02-11 11:22:07 - Initialize LCP.
Wed, 2009-02-11 11:22:07 - LCP is allowed to come up.
Wed, 2009-02-11 11:22:09 - CHAP authentication success
Wed, 2009-02-11 11:22:17 - <DDNS>Update OK: good
Wed, 2009-02-11 12:03:08 - Send out NTP request to 128.250.36.3
Wed, 2009-02-11 15:36:58 - Send out NTP request to 132.163.4.102
Wed, 2009-02-11 22:44:08 - Send out NTP request to 128.250.36.3
Thu, 2009-02-12 03:01:55 - Initialize LCP.
Thu, 2009-02-12 03:01:55 - LCP is allowed to come up.
Thu, 2009-02-12 03:02:08 - CHAP authentication failed
Thu, 2009-02-12 03:02:08 - LCP down.
Thu, 2009-02-12 03:02:55 - Initialize LCP.
Thu, 2009-02-12 03:02:56 - LCP is allowed to come up.
Thu, 2009-02-12 03:03:39 - CHAP authentication failed
Thu, 2009-02-12 03:03:39 - LCP down.
Thu, 2009-02-12 03:03:56 - Initialize LCP.
Thu, 2009-02-12 03:03:56 - LCP is allowed to come up.
Thu, 2009-02-12 03:04:53 - CHAP authentication success
Thu, 2009-02-12 03:04:58 - LCP down.
Thu, 2009-02-12 03:05:00 - Initialize LCP.
Thu, 2009-02-12 03:05:00 - LCP is allowed to come up.
Thu, 2009-02-12 03:05:07 - <DDNS>HTTP cannot connected
Thu, 2009-02-12 03:05:08 - CHAP authentication failed
Thu, 2009-02-12 03:05:08 - LCP down.
Thu, 2009-02-12 03:06:01 - Initialize LCP.
Thu, 2009-02-12 03:06:01 - LCP is allowed to come up.
Thu, 2009-02-12 03:06:29 - CHAP authentication failed
Thu, 2009-02-12 03:06:29 - LCP down.
Thu, 2009-02-12 03:07:02 - Initialize LCP.
Thu, 2009-02-12 03:07:02 - LCP is allowed to come up.
Thu, 2009-02-12 03:07:19 - CHAP authentication failed
Thu, 2009-02-12 03:07:19 - LCP down.
Thu, 2009-02-12 03:08:02 - Initialize LCP.
Thu, 2009-02-12 03:08:02 - LCP is allowed to come up.
Thu, 2009-02-12 03:08:33 - CHAP authentication failed
Thu, 2009-02-12 03:08:33 - LCP down.
Thu, 2009-02-12 03:09:03 - Initialize LCP.
Thu, 2009-02-12 03:09:03 - LCP is allowed to come up.
Thu, 2009-02-12 03:09:38 - CHAP authentication success
Thu, 2009-02-12 03:09:46 - <DDNS>Update OK: good
Thu, 2009-02-12 03:13:25 - Initialize LCP.
Thu, 2009-02-12 03:13:26 - LCP is allowed to come up.
Thu, 2009-02-12 03:13:53 - CHAP authentication failed
Thu, 2009-02-12 03:13:53 - LCP down.
Thu, 2009-02-12 03:14:26 - Initialize LCP.
Thu, 2009-02-12 03:14:26 - LCP is allowed to come up.
Thu, 2009-02-12 03:14:54 - CHAP authentication failed
Thu, 2009-02-12 03:14:54 - LCP down.
Thu, 2009-02-12 03:15:27 - Initialize LCP.
Thu, 2009-02-12 03:15:27 - LCP is allowed to come up.
Thu, 2009-02-12 03:16:28 - Initialize LCP.
Thu, 2009-02-12 03:16:28 - LCP is allowed to come up.
Thu, 2009-02-12 03:16:55 - CHAP authentication failed
Thu, 2009-02-12 03:16:55 - LCP down.
Thu, 2009-02-12 03:17:28 - Initialize LCP.
Thu, 2009-02-12 03:17:28 - LCP is allowed to come up.
Thu, 2009-02-12 03:17:56 - CHAP authentication failed
Thu, 2009-02-12 03:17:56 - LCP down.
Thu, 2009-02-12 03:18:29 - Initialize LCP.
Thu, 2009-02-12 03:18:29 - LCP is allowed to come up.
Thu, 2009-02-12 03:18:58 - CHAP authentication failed
Thu, 2009-02-12 03:18:58 - LCP down.
Thu, 2009-02-12 03:19:30 - Initialize LCP.
Thu, 2009-02-12 03:19:30 - LCP is allowed to come up.
Thu, 2009-02-12 03:19:33 - CHAP authentication failed
Thu, 2009-02-12 03:19:33 - LCP down.
Thu, 2009-02-12 03:20:30 - Initialize LCP.
Thu, 2009-02-12 03:20:31 - LCP is allowed to come up.
Thu, 2009-02-12 03:20:59 - CHAP authentication failed
Thu, 2009-02-12 03:20:59 - LCP down.
Thu, 2009-02-12 03:21:31 - Initialize LCP.
Thu, 2009-02-12 03:21:31 - LCP is allowed to come up.
Thu, 2009-02-12 03:21:45 - CHAP authentication success
Thu, 2009-02-12 03:24:59 - <DDNS>HTTP cannot connected
Thu, 2009-02-12 07:57:32 - LCP down.
Thu, 2009-02-12 07:57:34 - Initialize LCP.
Thu, 2009-02-12 07:57:34 - LCP is allowed to come up.
Thu, 2009-02-12 07:57:37 - CHAP authentication success
Thu, 2009-02-12 08:00:51 - <DDNS>HTTP cannot connected
Thu, 2009-02-12 08:03:20 - LCP down.
Thu, 2009-02-12 08:03:22 - Initialize LCP.
Thu, 2009-02-12 08:03:22 - LCP is allowed to come up.
Thu, 2009-02-12 08:03:25 - CHAP authentication success
Thu, 2009-02-12 08:03:32 - <DDNS>Update OK: good


Hardly...

[Kyle!]

I'm on Be* and been getting a similar problem today, even on OpenDNS.

[Agnostic Bear]

Lol oh dear, looks like BT isn't coping so well :P

traceroute to google.co.uk (216.239.59.104), 64 hops max, 40 byte packets
1 10.167.160.1 (10.167.160.1) 6.306 ms 4.663 ms 5.935 ms
2 pete-t2cam1-b-ge911.network.virginmedia.net (80.3.130.169) 5.957 ms 6.055 ms 5.905 ms
3 pete-t3core-1b-ge-112-0.network.virginmedia.net (195.182.182.101) 5.932 ms 5.817 ms 5.939 ms
4 pop-bb-b-so-520-0.network.virginmedia.net (212.43.162.249) 11.926 ms 16.762 ms 11.895 ms
5 pop-bb-a-ae0-0.network.virginmedia.net (213.105.174.229) 12.913 ms 11.805 ms 11.904 ms
6 man-bb-b-as1-0.network.virginmedia.net (212.43.162.86) 16.876 ms 15.744 ms 17.850 ms
7 tele-ic-3-ae0-0.network.virginmedia.net (212.43.163.70) 24.755 ms 21.747 ms 21.823 ms
8 162-14-250-212.static.virginmedia.com (212.250.14.162) 44.675 ms 42.598 ms 46.657 ms
9 209.85.255.175 (209.85.255.175) 17.851 ms 17.731 ms 17.860 ms
10 209.85.251.190 (209.85.251.190) 28.788 ms 40.667 ms 209.85.250.216 (209.85.250.216) 33.730 ms
11 64.233.174.185 (64.233.174.185) 31.673 ms 72.14.232.241 (72.14.232.241) 39.614 ms 32.502 ms
12 216.239.49.114 (216.239.49.114) 33.743 ms 33.646 ms 216.239.49.126 (216.239.49.126) 32.634 ms
13 216.239.59.104 (216.239.59.104) 29.647 ms 31.681 ms 31.754 ms

[N!ck]

As normal for me.

1 30 ms 100 ms 99 ms O2WirelessBox.lan [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 23 ms 23 ms 22 ms 195.66.224.125
5 23 ms 23 ms 22 ms 209.85.252.42
6 31 ms 24 ms 37 ms 72.14.233.63
7 45 ms 69 ms 40 ms 72.14.232.209
8 51 ms 37 ms 38 ms 209.85.250.141
9 37 ms 36 ms 48 ms 72.14.232.203
10 40 ms 37 ms 39 ms fg-in-f104.google.com [72.14.221.104]


Tracing route to newswww.bbc.net.uk [212.58.226.29] over a maximum of 30 hops:

1 72 ms 100 ms 99 ms O2WirelessBox.lan [192.168.1.254]
2 * * * Request timed out.
3 * * 39 ms 10.1.2.1
4 43 ms 35 ms 44 ms bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]
5 44 ms 42 ms 34 ms 212.58.238.129
6 39 ms 32 ms 42 ms newslb12.thdo.bbc.co.uk [212.58.226.29]

[Recursion]

Fine for me and im on BT (:

[Luke]

Mines fine now xD

[Robbie]

Normal for me on Be*

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=14ms TTL=121
Reply from 212.58.224.138: bytes=32 time=13ms TTL=121
Reply from 212.58.224.138: bytes=32 time=12ms TTL=121
Reply from 212.58.224.138: bytes=32 time=13ms TTL=121

Ping statistics for 212.58.224.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 14ms, Average = 13ms

C:\Users\Robbie>ping multiplay.co.uk

Pinging multiplay.co.uk [85.236.96.22] with 32 bytes of data:
Reply from 85.236.96.22: bytes=32 time=14ms TTL=123
Reply from 85.236.96.22: bytes=32 time=13ms TTL=123
Reply from 85.236.96.22: bytes=32 time=13ms TTL=123
Reply from 85.236.96.22: bytes=32 time=13ms TTL=123

Ping statistics for 85.236.96.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 14ms, Average = 13ms

[Flisker]

I'm on Be* and been getting a similar problem today, even on OpenDNS.


As normal for me.

1 30 ms 100 ms 99 ms O2WirelessBox.lan [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 23 ms 23 ms 22 ms 195.66.224.125
5 23 ms 23 ms 22 ms 209.85.252.42
6 31 ms 24 ms 37 ms 72.14.233.63
7 45 ms 69 ms 40 ms 72.14.232.209
8 51 ms 37 ms 38 ms 209.85.250.141
9 37 ms 36 ms 48 ms 72.14.232.203
10 40 ms 37 ms 39 ms fg-in-f104.google.com [72.14.221.104]


Tracing route to newswww.bbc.net.uk [212.58.226.29] over a maximum of 30 hops:

1 72 ms 100 ms 99 ms O2WirelessBox.lan [192.168.1.254]
2 * * * Request timed out.
3 * * 39 ms 10.1.2.1
4 43 ms 35 ms 44 ms bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]
5 44 ms 42 ms 34 ms 212.58.238.129
6 39 ms 32 ms 42 ms newslb12.thdo.bbc.co.uk [212.58.226.29]


Normal for me on Be*

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=14ms TTL=121
Reply from 212.58.224.138: bytes=32 time=13ms TTL=121
Reply from 212.58.224.138: bytes=32 time=12ms TTL=121
Reply from 212.58.224.138: bytes=32 time=13ms TTL=121

Ping statistics for 212.58.224.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 14ms, Average = 13ms

C:\Users\Robbie>ping multiplay.co.uk

Pinging multiplay.co.uk [85.236.96.22] with 32 bytes of data:
Reply from 85.236.96.22: bytes=32 time=14ms TTL=123
Reply from 85.236.96.22: bytes=32 time=13ms TTL=123
Reply from 85.236.96.22: bytes=32 time=13ms TTL=123
Reply from 85.236.96.22: bytes=32 time=13ms TTL=123

Ping statistics for 85.236.96.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 14ms, Average = 13ms

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 51 ms 99 ms 99 ms O2WirelessBox.lan [192.168.1.254]
2 130 ms 130 ms 130 ms xx-xxx-xxx-xxx.bethere.co.uk [xx.xxx.xxx.xxx]
3 129 ms 129 ms 128 ms 10.1.1.106
4 * 132 ms 136 ms 10.1.1.93
5 * * * Request timed out.
6 130 ms 130 ms 131 ms 83.245.126.93
7 130 ms 130 ms 130 ms 212.58.238.153
8 129 ms 129 ms 129 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

my internet connection is absolutely crap atm

Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 8128 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 7150 kbps
Actual IP throughput achieved during the test was - 869 kbps

[Creddos]

NOPE! ur on ur own m8 :D