Broadband Related > Known Network Issues + MSO's
Massive Demon outage?
pintosal:
Demon was my first broadband ISP around 10 years ago.
They were very good then, but now it sounds like they've joined the rest of the mediocrity.
waltergmw:
See:-
https://www.blogger.com/comment.g?blogID=12990991&postID=1133301310748099069
which gives AAISP's take on the Be situation:-
AAISP said...
Some more info and updates:
A Global Crossing fibre issue has taken down eight 10Gb links on the O2/BE broadband core.
This has been confirmed as a fibre break in the Leeds Huddersfield area. Engineers are currently on site re-splicing.
(we're not currently seeing high latency, but BE expect it to kick in by mid afternoon if this issue hasn't been resolved by then.)
The issue was raised at 06:25 today, no ETA on a fix has been issued yet.
11:24 AM, September 30, 2009
Blogger AAISP said...
Fibres have been re-spliced and this issue has been closed.
2:13 PM, September 30, 2009
broadstairs:
Glad I jumped ship a year ago, had been with Demon since we first got the web but they became too unreliable, too unresponsive and vastly too expensive. I now get BB and phone with unlimited land line calls world wide for £4 a month less than just my Demon BB.
sevenlayermuddle:
Couldn't agree more about how good Demon were ten years ago, but then they were a small privately owned company, and reputed to be 'the techies' ISP', as they seemed to pitch at people with good technical skills and accrodingly employed knowledgeable support staff. However, the company's been sold/merged/taken over several times and there really seems to be no remnant of the original ISP left.
Leaving Demon, unfortunately, is a big upheaval as we run a popular (non-commercial) website, which orignally had a demon domain name. We changed to a .com domain name seven or eight years ago, and the website's no longer even hosted by demon, but there's still an awful lot of links to that old demon site, which just redirects to the new .com. And, of course, there's still the occasional (valuable) email that arrives addressed to the old demon email addresses.
GrumblingAgain:
Hi
I was a customer badly affected by their outage yesterday and I was most unimpressed with their service (lack of). I was surprised by their service statement which said they rebooted and it didn't work. Scratch head what do we do now?
The reason for this post as I am no expert in these things, but I wonder if anyone would know from looking at this traceroute if it shows the actual cause of the problem or is it merely a symptom of some other problem?
I was tracing from my home (on VirginMedia) into our office where our office (on Demon) ....
5 28 ms 9 ms 11 ms bre-bb-b-as5-0.network.virginmedia.net [213.105.172.234]
6 12 ms 11 ms 11 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
7 81 ms 16 ms 19 ms ldn-b2-link.telia.net [213.248.100.97]
8 16 ms 16 ms 17 ms ldn-bb2-link.telia.net [80.91.249.177]
9 17 ms 18 ms 17 ms ldn-b4-link.telia.net [80.91.250.237]
10 13 ms 11 ms 10 ms thus-106917-ldn-b4.c.telia.net [213.248.100.162]
11 11 ms 12 ms 18 ms anchor-inside-4-g1-0-5.router.demon.net [193.195.25.65]
12 15 ms 11 ms 12 ms anchor-access-3-g1-1.router.demon.net [194.159.161.65]
13 11 ms 10 ms 11 ms anchor-inside-3-g5-0-1.router.demon.net [194.159.161.66]
14 16 ms 13 ms 13 ms anchor-access-3-g1-1.router.demon.net [194.159.161.65]
15 10 ms 12 ms 12 ms anchor-inside-3-g5-0-1.router.demon.net [194.159.161.66]
16 13 ms 13 ms 12 ms anchor-access-3-g1-1.router.demon.net [194.159.161.65]
17 10 ms 16 ms 9 ms anchor-inside-3-g5-0-1.router.demon.net [194.159.161.66]
18 17 ms 13 ms 12 ms anchor-access-3-g1-1.router.demon.net [194.159.161.65]
19 12 ms 11 ms 16 ms anchor-inside-3-g5-0-1.router.demon.net [194.159.161.66]
20 43 ms * 11 ms anchor-access-3-g1-1.router.demon.net [194.159.161.65]
21 13 ms 11 ms 11 ms anchor-inside-3-g5-0-1.router.demon.net [194.159.161.66]
22 13 ms 11 ms 12 ms anchor-access-3-g1-1.router.demon.net [194.159.161.65]
23 10 ms 17 ms 10 ms anchor-inside-3-g5-0-1.router.demon.net [194.159.161.66]
24 11 ms 12 ms 13 ms anchor-access-3-g1-1.router.demon.net [194.159.161.65]
25 11 ms 11 ms 11 ms anchor-inside-3-g5-0-1.router.demon.net [194.159.161.66]
26 15 ms 12 ms 13 ms anchor-access-3-g1-1.router.demon.net [194.159.161.65]
27 13 ms 11 ms 10 ms anchor-inside-3-g5-0-1.router.demon.net [194.159.161.66]
28 12 ms 11 ms 12 ms anchor-access-3-g1-1.router.demon.net [194.159.161.65]
29 11 ms 10 ms 10 ms anchor-inside-3-g5-0-1.router.demon.net [194.159.161.66]
30 10 ms 15 ms 13 ms anchor-access-3-g1-1.router.demon.net [194.159.161.65]
Trace complete.
Does the fact that it is clearly looping between [194.159.161.66] and [194.159.161.65] indicate that one of those points was wrongly configured? or is that simply what happens when an onward link fails? I could see straight away where the problem might lie, I just wonder why it would take 8 hours to sort out?
Yes it was a double headache for me yesterday what with Virgin Media falling over the day before!
Thanks
Regards
GA
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version