Outage approx 9.45 pm?

zappaDPJ · Sep 03, 2010, 22:29:33

I just lost FTTC for around 30-40 minutes. I tried my ADSL connection but that was down as well. FTTC has just come back by my ADSL line is still down.

Anyone else?

PS and completely O/T: My router is telling me...

A New Firmware Version is Found. Do You Want to Download the New Version Now?
Current Version 1.2.6
New Version 1.2.30

Does that make sense to you?

Bill · Sep 03, 2010, 22:59:04

No outage here, but things "felt" a bit sluggish for a while around then.

zappaDPJ · Sep 03, 2010, 23:24:02

Cheers, perhaps it's local to me, FTTC is still up (just) but my ADSL is still down.

My FTTC is currently experiencing 74% packet loss

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\zappaDPJ>ping idnet.net -n 100

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 212.69.36.10:
Packets: Sent = 100, Received = 26, Lost = 74 (74% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 25ms, Average = 23ms

C:\Users\zappaDPJ>

zappaDPJ · Sep 04, 2010, 03:06:28

Dropped again perhaps. Posting on the phone but I've no idea from which network.

sof2er · Sep 04, 2010, 03:29:17

No problems here ZappaDJ

Glasgow Area

Rik · Sep 04, 2010, 10:04:20

I can't find any BT outage reports, Zap. Phone support, they will respond for a 'no connection'.

zappaDPJ · Sep 04, 2010, 15:42:05

Thanks for the replies. I've managed to get connected again on ADSL. My FTTC connection appears to be dying a slow death. I'll start a new thread on it because I want to keep all the data in one thread.

I won't bother support until Monday now I'm up and running again.

jezuk1 · Sep 05, 2010, 16:36:06

Connections are dropping almost at random to various networks around europe, nothing is really staying connected for more than a few minutes at the moment

Rik · Sep 05, 2010, 16:38:25

I've lost everything but the forum and idnet mail atm.

DavePeachHill · Sep 05, 2010, 16:39:40

Same, everything has gone except the forum and main website

DavePeachHill · Sep 05, 2010, 16:40:13

Oh I lie, everything now seems to be back lol

Ray · Sep 05, 2010, 16:41:00

So had I, but it seems to have started coming back now.

Rik · Sep 05, 2010, 16:41:27

Same here...

zappaDPJ · Sep 05, 2010, 17:41:37

I've completely lost FTTC but I've had no issues at all with ADSL all day that I'm aware of.

Rik · Sep 05, 2010, 17:43:46

That has to be a BT issue, Zap, phone or email support.

zappaDPJ · Sep 05, 2010, 17:47:59

Yeah, I think it's either adapted its rate to oblivion or it could be that there's been a a hardware failure because I can't even access the router which seems odd.

I'm fine on my other line so I won't bug support until tomorrow.

Rik · Sep 05, 2010, 17:50:13

Sounds a bit like a failed router, doesn't it.

zappaDPJ · Sep 05, 2010, 18:07:25

I do wonder, I had a lot of difficulty getting into it in the first place so I made sure I bookmarked it. That worked for a day or two but stopped working when the connection started to die.

Rik · Sep 05, 2010, 18:10:15

Sadly, we can't even recommend you swap out the modem.

Steve · Sep 05, 2010, 18:12:17

Is the TBB graph working for that line?

zappaDPJ · Sep 05, 2010, 18:37:54

The last time I looked it was a just a slab of red (100% packet loss)

Steve · Sep 05, 2010, 18:39:51

Have you tried with a PC plugged straight into the VDSL modem.

Rik · Sep 05, 2010, 18:40:13

Quote from: zappaDPJ on Sep 05, 2010, 18:37:54
The last time I looked it was a just a slab of red (100% packet loss)

Ugly.

zappaDPJ · Sep 05, 2010, 19:03:25

Quote from: Steve on Sep 05, 2010, 18:39:51
Have you tried with a PC plugged straight into the VDSL modem.

Why didn't I think of that

I'll give it a try now.

zappaDPJ · Sep 05, 2010, 19:11:55

I've tried it, Windows 7 reports a problem, tries to fix it and comes back with a very funny suggestion screen with three options, one of which is phone a friend

Rik · Sep 05, 2010, 19:16:19

It isn't sounding like Chris Tarrant as well is it?

zappaDPJ · Sep 05, 2010, 19:20:47

No but in its current state it's about as much use as Chris Tarrant

Rik · Sep 05, 2010, 19:23:47

zappaDPJ · Sep 06, 2010, 18:30:37

Just a quick update and a thanks to support for all their help so far.

It looks like I have an intermittent issue my side of BT's socket, possibly a hardware connectivity issue. I'm up and running again on FTTC. Dismantling the whole show and reconnect it seems to provide a fix when there's no connectivity. I have a few other minor issues with it that I need to look into but first I need to work out exactly which part of the hardware is causing the problem.

Rik · Sep 06, 2010, 18:32:01

Good luck with that, Zap.