Outage approx 9.45 pm?

[zappaDPJ]

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]

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

[zappaDPJ]

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]

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

[sof2er]

No problems here ZappaDJ

Glasgow Area

[Rik]

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

[zappaDPJ]

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]

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]

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

[DavePeachHill]

Same, everything has gone except the forum and main website

[DavePeachHill]

Oh I lie, everything now seems to be back lol

[Ray]

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

[Rik]

Same here...

[zappaDPJ]

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

[Rik]

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

[zappaDPJ]

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]

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

[zappaDPJ]

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]

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

[Steve]

Is the TBB graph working for that line?

[zappaDPJ]

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

[Steve]

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

[Rik]

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

Ugly.

[zappaDPJ]

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]

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