See the announcement here (http://www.idnetters.co.uk/forums/index.php?topic=17784.0)
Thanks Glenn, it's reassuring to know that BT is aware of the problem.
It would be more reassuring if we thought they knew how to fix it. ;)
are they cross your heart bras? ;D
BT aren't that playful, Alf.
Could they clarify whether this effects adslmax or just adsl2+?
I think a lift and separate is required ;)
Just WBC/ADSL2+, Steve.
Thanks Rik
Lets hope BT get this sorted soon!
Thanks for the update IDNet :)
:fingers:
Quote from: klipp on Dec 21, 2009, 15:24:14
Thanks Glenn, it's reassuring to know that BT is aware of the problem.
I think it's more reassuring (or actually more accurate) that BT are aware that the public are aware of the problem, therefore it is now a problem that is their problem that they'll have to fix to avoid more problems ;D
Problematical, eh Niall. ;)
Another half hour of loss of service again last night between 4:30am and 5:00am. Still annoying, but not as bad as Saturday's 12 hour loss of service.
You should sleep occasionally, Klipp. ;)
Haha, no I mean according to my router's log. ;D
;D
Sorry, couldn't help myself. ;)
It's happening again. The router says it's connected with good download speed but there is zero download speed in reality.
Chris
same here, it's been bad for a couple of hours now. i tried to reply to this thread an hour ago but it all ground to a halt again :shake:
i've let support know via a message just so they know it's still not right and they can then take it up with BT tomorrow.
Argh! This is intolerable!!
ditto, speed is pretty awful here. lots of packet loss too. sort it out BT...
Quote from: cwmusson on Dec 22, 2009, 19:56:38
...router says it's connected with good download speed but there is zero download speed in reality.
Chris
Same happened with me while my connection was slow, router said I had a connection speed of 7616 kbps whereas BT Speed Test said I had a speed of 144 kbps. Maybe the router stats are referring to your connection rate, I'm not sure tbh.
:fingers: for BT get their arses in gear soon.
You could all, of course, email BT's CEO... :whistle:
Same here last night, went down around 7.00 p.m. and not back 'til this morning, when I had to reboot the router to reconnect.
This is BT?: :dig:
Sadly, yes, Sarah. IDNet are trying to get an update from BT and will let us know asap.
Well at least the AAISP blog is blunt about it :):
[open] 21CN-BRAS-RED1-PE buggered again (http://aaisp.blogspot.com/2009/12/open-21cn-bras-red1-pe-buggered-again.html).
It also logs other nodes(?) in trouble though.
Yesterday BT told us that they had fixed the problem. They hadn't. This morning they say that they have now fixed it properly. So far, the lines that we are monitoring, have been stable...
AAISP are becoming known for their bluntness. Whilst it's fun for us, I wonder what it's doing to their relationship with BT?
See also the announcement here. (http://www.idnetters.co.uk/forums/index.php?topic=17816.msg426775#msg426775)
Quote from: Sarah on Dec 23, 2009, 10:16:39
This is BT?: :dig:
That's me digging a hole large enough to put BT and their poor services in! >:D
There isn't anywhere to dig a hole big enough, surely? ;D
Quote from: Rik on Dec 23, 2009, 10:48:06
AAISP are becoming known for their bluntness. Whilst it's fun for us, I wonder what it's doing to their relationship with BT?
It seems to work very well for them, actually, Rik.
The 'No B.S.' sign on their site says it all. They get on fine with those in BT who don't try it on, and they've done a lot of work with BT to improve the latter's systems.
However, there still appear to be some in BT who try and be obstructive and pretend there are no problems. That's when the proverbial hits the fan.
BT do seem to have a dark side, where they put their heads in the sand and proclaim "We can't see anything wrong, therefore all is well, no matter how many people tell us otherwise." :(
They can't do that so easily with Adrian's lot. Their monitoring systems are quite effective, and they often seem to know about a problem and its likely cause before BT.
They also know quickly, and can prove, whether a fault has been fixed properly. This really annoys some in BT who allegedly may return a fault as fixed when it isn't. It gets bounced back as 'unfixed' in double quick time together with notes on where the fault actually is. ;)
Quite unsettling for some in BT, but for others, the real engineers and problem solvers, it can be very useful. Those that bother to read the notes, that is.
They may seem hard on BT at times, but when it's a problem at AA's end, then activity becomes obsessively frenetic. Quite a revelation actually to watch them beat themselves to pulp sorting out their own problems.
I don't know how they compare with other ISPs - others don't even allow you to control and administer your own line, let alone allow you into the minutiae of their relationship with BT - but it's fun watching all the breast beating, and I can't fault the end product so far.
I do know that IDNet do a lot of badgering, Bob, I've heard Brian in full flood on the phone to BT. ;D I think what we hear, compared to A&A customers is down to a difference in style.
If Peterborough does it again, not sure what words the A&A blog will be left with :)
;D
They probably won't include Happy Christmas. ;)
Quote from: Sarah on Dec 23, 2009, 14:55:18
If Peterborough does it again, not sure what words the A&A blog will be left with :)
;D Perhaps they'll start joining two or three of them together. ;)
;D
Or they could do a Tricky Dicky...
It's starting again...............
Let support know quickly.
All OK here so far...but it normally doesn't start until 7-8pm
I've just noticed I've lost around 2000kbps sync speed as a result of the Peterborough effect!
Do you think it's worth asking IDNet if my profile could be reset? Especially as it's BT's doing!
Punch do you lose sync when the trouble occurs?
My Profile hasn't been affected because although I can't connect to any sites, my router still remains synced as per normal...
Hi Klipp
Nope, I stay sync'd all the time, but I did lose sync this afternoon and the router re-sync'd immediately at a speed approx 2000kbps slower.
I have a feeling I know what it is now...when the trouble first started IDNet made a change to my profile which would make things much more stable for me. This was before we all really knew what the trouble was.
No problem last night hooray, it was possible to run a very long webcast stream without a stutter.
(The last long night of the UN COP in Copenhagen - UNFCCC Webcast (http://www1.cop15.meta-fusion.com/kongresse/cop15/templ/archive.php?id_kongressmain=1&theme=cop15))
Thanks to all if this is resolved.
:fingers: :fingers: ;)
Is Peterborough still broken? I've been away since the 23rd and got back today. I still have the same problems as before (connection losses and no download speed when the router says "connected"). It was working OK from 5-9pm but the familiar problems are happening again. I'm having to send this using a mobile broadband connection as idnet is not working, even though it says "connected".
Can confirm it is once again knackered. ::)
Thanks, klipp. I hoped it might be fixed after being away for a week :-(
Ironically it was working fine the week you were away lol.
It's still broken, so 90 minutes downtime at peak time so far. It's just as well that the BBC have come up trumps with the programmes on BBC4 TV tonight. Glad I'm not relying in iplayer though ...
Connection is completely down at the moment. There seems to be a variety of error states:
- No connection whatsoever, red light on router
- Green light on router but login doesn't happen "LCP is allowed to come up"
- Seemingly connected and logged in but nothing works, not even DNS
- Connected and logged in, DNS works, but no download speed. Ping to www.idnet.net sometimes works slowly and sometimes does not work.
It seems to randomly cycle through all the above.
At the risk of ranting, I think it's disgusting that this problem has been left to affect probably thousands of internet users for weeks now. It is time for BT to pull their finger out.
It's now 3 hours downtime. I have reported this to support via email. I am wondering when the BT monopoly* has to start paying compensation due to weeks of substandard service.
* My street can't get Virgin and my exchange doesn't have o2/be. We can get sky on an llu but that doesn't count as you have to also get sky tv for that, so BT is still a genuine monopoly in my street.
My current thought is that BT generally do things badly and that the BBC generally do things well, so the monopoly parts of BT should be given to the BBC to manage.
I used to work for BT. The ordinary workers and lower management work hard to provide services to their customers. However the middle to upper management structure is all about empire building so good work by proper workers is destroyed by management. I left BT 9 years ago but people I know who still work there say it's still the same.
I had a reply from support (Miriam) on 1 January which is why I am an idnet customer.
BT will be looking into this critical issue affecting many customers in 2 or 3 days time.
This astounds me.
I work for a small company. If we had a critical issue affecting many customers and only looked at it in 2 or 3 days time we would be out of business before it was looked at.
Grrrrrr.
4.5 hours no broadband
I had problems again last night. Pretty much no internet from around 7pm to 2am. Even though the router said I was connected.
Don't worry, it's not just Peterborough being picked on. :(
I've checked with support, the issue is definitely ongoing, but IDNet are unable to chase BT until Monday, as the team specifically dealing with it haven't been at work since December 24. :sigh:
Quote from: Rik on Jan 02, 2010, 10:45:40
I've checked with support, the issue is definitely ongoing, but IDNet are unable to chase BT until Monday, as the team specifically dealing with it haven't been at work since December 24. :sigh:
How on earth can a team dealing with such an outage just take so much time off, or why can another team not have been put in place to solve this? Other service industries run over the holidays :shake:
Good question, Gary, for which I have no answer. My line's now been down a week because BT don't seem to be working. :(
as other have said, top marks for IDnet support and thanks to Miriam for replying to my email at gone midnight this morning! BT's behaviour is shocking, it's a totally different story when they are the customer and they are expecting (for example) a replacement firewall on christmas eve. you've never heard so much shouting and screaming! its a shame they dont pass on any of these SLAs to their customers be them business or domestic customers.
Couldn't agree more. :(
It appears to be temporarily fixed now. I guess complete connection loss is not important enough for BT to pay their engineers to work outside office hours.
Did you know that there is a BT board member who used to be a NuLab cabinet minister? How do you spell those words beginning with "monopol..." and "corrup...".
Y & T?
I think it's about time we contacted our local Mp's, Ofcom, newspapers and telvision to highlight this and other BT issues that now affect so many peoplethroughout the country. The organization is a shambles and has to be restructured and made legally accountable for its perfomance and service. :rant2:
QuoteIt appears to be temporarily fixed now.
It always happens in the evening.
Quote from: klipp on Jan 02, 2010, 13:40:44
It always happens in the evening.
Yup...around 7pm ish usually.
Ignor the post, silly forum not liking me having 2 windows open in FF. :rant2:
It gets confused as to which session is the live one.
I don't know about the other guys affected by this problem but it happened again for me last night, but not until around 10pm.
Router log shows "LCP allowed to come up" during the small hours of this morning. I must say it was fine yesterday evening though.
You sometimes get the feel that BT toss a coin to decide who to affect when. :(
Quote from: Rik on Jan 03, 2010, 12:30:20
You sometimes get the feel that BT toss a coin to decide who to affect when. :(
I agree, Rik, I'm sure BT's capacity is severely compromised in some areas, I can get speeds around 6.9Mbs before 9:00am and after 9:30pm but falls to this abysmal level :rant2: during the main part of the day: -
Test1 comprises of Best Effort Test: -provides background information.
Download Speed
2282 Kbps
0 Kbps 7150 Kbps
Max Achievable Speed
Download speedachieved during the test was - 2282 Kbps
For your connection, the acceptable range of speeds is 1200-7150 Kbps.
Additional Information:
Your DSL Connection Rate :8128 Kbps(DOWN-STREAM), 832 Kbps(UP-STREAM)
IP Profile for your line is - 7150 Kbps
Welcome to my world Ray ;D I sync at 2400kbs with a throughput of around 1800kbs
Quote from: PuncH on Jan 03, 2010, 07:41:11
I don't know about the other guys affected by this problem but it happened again for me last night, but not until around 10pm.
:back:
Um... I hope that was not me downloading blender, terragen and a load of art resources. It seems to strangely correlate to my internet usage! :O
Quote from: Technical Ben on Jan 03, 2010, 14:48:31
:back:
Um... I hope that was not me downloading blender, terragen and a load of art resources. It seems to strangely correlate to my internet usage! :O
SO! It's all your fault! :rant2:
:whistle:
It's starting again!!
There's a lot of complaints on ThinkBroadband too.
Yes it's broken again since about 6.30pm. The usual connected but no download speed.
I wonder how many more weeks (or months) this will go on. I don't see this being an easy fix otherwise it would have been done by now.
i don't think it's a matter of being easy or not - it's just BT being plain damn lazy and not wanting to send out engineers to fix their problems. obviously 70% packet loss isn't something worth fixing with any haste. grr. :no:
It's still broken so that's 3 hours off.
At least it's saved me from the boredom of doing my tax return online, which was my intended task for this evening.
I wonder if IDNet can give us some feedback on what the problem is, and how long it could be expected to continue. I realise it's not IDNet's fault this is happening, but it would still be good if they could fill us in on what's going on. It's very frustrating only having internet access for half the day, for weeks on end, without really knowing why.
It's still broken. So that's 5.5 hours down today so far. When it is connected there is currently 54% packet loss according to a ping to www.idnet.net so therefore useless. I wonder at what point BT have to provide compensation for loss of service?
AAISP have a graph here:
http://aaisp.blogspot.com/2010/01/open-21cn-issues-on-peterborough-bras.html
The red bits match the downtime reports in my router log.
My connection was also next to useless last night, from about 6.40pm until 4.50am!
SORT IT OUT BT!!!
My router shows the problem lasted until 5.01am for me, so that was a 10.5 hour outage.
BT haven't given a fix date to IDNet. The special team working on this fault stopped work on December 24, and return today. Clearly, BT are totally customer focussed. ::) The last fix date I saw for the issue was January 13, a full month after it started.
BT are being equally reticent with the exact nature of the fault, but given the lead time for the fix, I'm guessing they have to obtain a new piece of hardware.
Quote from: Rik on Jan 04, 2010, 08:56:14
I'm guessing they have to obtain a new piece of hardware.
Like a sandwich box and flask?
Cynic. ;D
I'm not sure if it has got anyhing to do with the Peterborough issue but I've lost my connection twice briefly this morning.
Have you seen the announcement from Miriam?
http://www.idnetters.co.uk/forums/index.php?topic=17816.msg432964#msg432964
No I had missed that. :blush:
Although I'm not experiencing the slow speeds or packet loss others are reporting.
(http://www.speedtest.net/result/671403715.png) (http://www.speedtest.net)
(http://www.pingtest.net/result/6972295.png) (http://www.pingtest.net)
Anyway I hope things improve soon for those badly affected by this. :fingers:
Thanks Rik for pointing out that announcement.
One a side note, I've just lost sync for a few minutes, did anyone else?
Argh, sync lost again!! This is probably going to wreck my profile lol. *sulks*
There's an update to the announcement...
It's starting again.... Let's hope they're monitoring this!!
They are, or at least they've said they will.
Ping and dns are not even working, so that must mean it's close to 100% packet loss tonight.
PING www.idnet.net (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=60 time=30.0 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=60 time=30.0 ms
--- 212.69.36.10 ping statistics ---
4 packets transmitted, 2 packets received, 50% packet loss
round-trip min/avg/max = 30.0/30.0/30.0 ms
:(
$ ping www.idnet.net
ping: unknown host www.idnet.net
$ ping 212.69.36.10
PING 212.69.36.10 (212.69.36.10) 56(84) bytes of data.
64 bytes from 212.69.36.10: icmp_seq=7 ttl=58 time=36.7 ms
64 bytes from 212.69.36.10: icmp_seq=11 ttl=58 time=36.7 ms
64 bytes from 212.69.36.10: icmp_seq=12 ttl=58 time=37.0 ms
64 bytes from 212.69.36.10: icmp_seq=13 ttl=58 time=35.8 ms
64 bytes from 212.69.36.10: icmp_seq=14 ttl=58 time=88.7 ms
64 bytes from 212.69.36.10: icmp_seq=22 ttl=58 time=36.1 ms
64 bytes from 212.69.36.10: icmp_seq=24 ttl=58 time=36.1 ms
64 bytes from 212.69.36.10: icmp_seq=26 ttl=58 time=36.2 ms
64 bytes from 212.69.36.10: icmp_seq=29 ttl=58 time=36.2 ms
64 bytes from 212.69.36.10: icmp_seq=32 ttl=58 time=36.2 ms
64 bytes from 212.69.36.10: icmp_seq=33 ttl=58 time=35.7 ms
64 bytes from 212.69.36.10: icmp_seq=34 ttl=58 time=36.6 ms
64 bytes from 212.69.36.10: icmp_seq=38 ttl=58 time=36.3 ms
64 bytes from 212.69.36.10: icmp_seq=39 ttl=58 time=36.7 ms
64 bytes from 212.69.36.10: icmp_seq=40 ttl=58 time=36.7 ms
64 bytes from 212.69.36.10: icmp_seq=45 ttl=58 time=37.6 ms
64 bytes from 212.69.36.10: icmp_seq=46 ttl=58 time=36.7 ms
64 bytes from 212.69.36.10: icmp_seq=49 ttl=58 time=36.6 ms
64 bytes from 212.69.36.10: icmp_seq=50 ttl=58 time=36.7 ms
^C
--- 212.69.36.10 ping statistics ---
50 packets transmitted, 19 received, 62% packet loss, time 49141ms
rtt min/avg/max/mdev = 35.786/39.274/88.768/11.675 ms
I can currently access most sites again.:)
However.. still very slow and laggy, but better than nothing.
I guess I spoke too soon. It's back to its glorious worst!!
Same here - slow and intermittent connection over the last few days. Worse in the evenings.
:welc: :karma:
Interestingly but perhaps not totally unrelated BT have confirmed that congestion on the Birmingham 20 CN BRAS is caused by themselves throttling their own network which they then obviously then pass on to the ISP. I think it's all falling apart. I think we're in for a rocky ride whilst adslmax,adsl2+ and now FTTC are all in the same pot.
We on the Peterborough node are into month 2 of only having internet for 12 out of 24 hours each day, so I suspect you're right about it being a problem for the long-haul. BT claim to be monitoring Peterborough node as we speak, yet nothing's been fixed.
I can't wait to hear BT's spin tomorrow...
:welc: :karma: Andez.
Quote from: klipp on Jan 04, 2010, 21:59:51
We on the Peterborough node are into month 2 of only having internet for 12 out of 24 hours each day
... and I'm out at work for most of the good half day :sigh:
It's still broken, so that's no usable connection for the entire evening once again.
The problems lasted until 5.15am this time.
I'm not normally one to jump on the compensation bandwagon, but I think on this occasion we're well and truly due something from BT.
Andez, :welc: :karma:
Forget about us being compensated. It'll never happen.
The aaisp blog suggests that tonight we might be looking forward to an evening of having a working connection. Here's hoping.
I think I'm right in saying that BT have no obligation to provide a broadband service. A perfect get out to avoid paying compensation. :dunno:
Quote from: klipp on Jan 05, 2010, 13:40:53
Here's hoping.
Joining you in hoping, Klipp. I'd been away and having returned Sunday night to the same problem, the updates here are very useful.
Quote from: Simon on Jan 05, 2010, 14:21:15
I think I'm right in saying that BT have no obligation to provide a broadband service. A perfect get out to avoid paying compensation. :dunno:
Just voice and 28k data I believe.
Although that applies to the level of service, there may be a separate SLA for those on broadband who's service is interrupted. If enough people were to email Ian Livingstone, there would probably be a payout.
It's that time of the evening and the internet is still working :fingers:
Well I didn't download anything yesterday, and I am back at work this week. II also don't stay up to the early hours of the morning. So I think I'm off the hook. :duck:
I'm only 20 miles from Peterborough, but have not had any problems. I get occasional breaks or slowdowns in connection, but it's usually due to me tripping over the router.
However, I don't know what pipe I am routed through. How do I find out?
Ask IDNet, Ben. They will know which node you're on. When you reach the IDNet network, we're now all on the same hostlink.
So far, so good :fingers:
I think BT have everything crossed too, Jonathan.
My internet still works........ *faints*
Been a while since I've seen this at this time of night!!
(http://www.pingtest.net/result/7100034.png) (http://www.pingtest.net)
Oh, the joy of happy smiling faces! ;D Hope it's now fixed for you, guys. :thumb:
huzzaah!
(http://www.pingtest.net/result/7104588.png)
I was a bit scepticle of BTs approach of 'lets try pulling cables until the packet loss stops' but hey if it resolves the problem and they lick every patch cable in their posession I don't care!
Now I can update my anti-virus which has been nagging me :eek4:
It's starting again..............
I can confirm huge packet loss AGAIN. :mad:
$ ping www.idnet.net
PING www.idnet.net (212.69.36.10) 56(84) bytes of data.
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=1 ttl=58 time=34.0 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=7 ttl=58 time=34.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=9 ttl=58 time=34.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=10 ttl=58 time=34.8 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=11 ttl=58 time=33.5 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=13 ttl=58 time=34.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=14 ttl=58 time=33.8 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=16 ttl=58 time=33.8 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=19 ttl=58 time=33.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=20 ttl=58 time=33.7 ms
^C
--- www.idnet.net ping statistics ---
20 packets transmitted, 10 received, 50% packet loss, time 19048ms
rtt min/avg/max/mdev = 33.430/34.044/34.870/0.431 ms
Yup...had 50% packetloss to www.idnet.net at just after 7pm.
Surprised I've been able to post this message to be honest.
It seems to be working ok again now ...
Back for now...
It's broken again. 65% packet loss.
Hmmm, it's back to its old ways here in Cambridge as well. I'm thinking of implementing RFC1149 until BT get this fixed...
Quote from: stuart_sjb on Jan 06, 2010, 20:03:03
Hmmm, it's back to its old ways here in Cambridge as well. I'm thinking of implementing RFC1149 until BT get this fixed...
I did have to google that one... but I had heard of it before. ;D
This is, quite frankly, unbelievable. I am so thankful I don't have this issue as I currently am watching my servers and internet line with a hawk-eye as we have a scientific data run over the course of these few days and any notable downtime would be a problem.
Is there any estimate of number of people affected by this? How many ISP technical lines are swamped under? Is 56k dial-up actually better than that?
No idea on numbers, esh, but it's certainly affecting all BT-based ISPs.
Has to be many thousands.
Probably tens of thousands. :shake:
Well it's that time of night again. ;D ::) :fingers:
It's getting to be a bit like waiting for the Blitz, isn't it.
Quote from: Rik on Jan 07, 2010, 18:43:23
It's getting to be a bit like waiting for the Blitz, isn't it.
LOL...there's certainly an impending feeling of doom in our house at around 7pm it must be said!
Not only is the net important for me (gaming) it's important for our eBay shop as well, so all's good when it's working.
And time to take up watching Norwich when it's not? ;D
Quote from: Rik on Jan 07, 2010, 19:11:49
And time to take up watching Norwich when it's not? ;D
PAH!
Would rather sit out in the snow than watch that rabble :D
Anyone else experiencing the return of the Problem of Doom, albeit intermittently, this evening?
So far I haven't (touch wood, fingers crossed, white rabbit etc etc)
But then I haven't touched the PC for about an hour. Just checked my router logs and there are no drops/disconnections.
Keep the rabbit close to hand :-p It is only intermittent for me, but since about 7:30pm I've been seeing a combination of lost packets and very high latency (in excess of 3 seconds for servers for which the round trip is usually only 30-40ms), leading to rather unpredictable downloads and browsing. But it's certainly an improvement on yesterday!
Just had a look at AAISP they seem to be confirming packet loss still continues to occur after the replacement part
Must have replaced the parts with more cheap Chinese bits. ;D
Maybe they bought 2nd hand and it was an old broken part they sold off a few years ago? ;)
Don't laugh, I've seen it happen :o
Anymore news on this issue at all? I didn't get a chance to call support today.
None that I've heard.
Will assume it's still open then, although now I've had no issues in the evenings my connection has been nice and stable.
Just need the margin to be reset so it'll then be back to it's former glory instead of the rather limp floppy excuse of a connection it is at the moment!
Sadly, I only ever get a limp and floppy excuse for a connection. ;)
:whistle:
;D
Mines normally rock solid and hardly wavers!
Youth is a wonderful thing. :evil:
Looks like IDNet have reset my noisemargin and it's now back to just under 15db and sync is back towards what it used to be.
Anyone else who suffered as a result of this issue had their connections reset?
Just noticed this on my rss feed
Status Notification: Announcement - 13 January 2010 15:55:57
Service: Announcement
Posted: 07 January 2010 10:04:22
Updated: 13 January 2010 15:55:57
Status:Resolved
Message: UPDATE TO PETERBOROUGH ISSUE
Further to the works carried out on 05/01/2010 BT replaced a card in the exchange.
Monitoring continues. Should the issue return further investigation will be carried out.
They replaced a card in my exchange and my line has been worse ever since. :(
Peterborough must have got your old one :thumb:
Quote from: Steve on Jan 13, 2010, 17:54:30
Just noticed this on my rss feed
Status Notification: Announcement - 13 January 2010 15:55:57
Service: Announcement
Posted: 07 January 2010 10:04:22
Updated: 13 January 2010 15:55:57
Status:Resolved
Message: UPDATE TO PETERBOROUGH ISSUE
Further to the works carried out on 05/01/2010 BT replaced a card in the exchange.
Monitoring continues. Should the issue return further investigation will be carried out.
That will be the same as this then Grin http://www.idnetters.co.uk/forums/index.php?topic=17816.msg435069#msg435069
Spoke to support today. They didn't reset my noisemargin and therefore assume it to be the DLM at the exchange that did it.
DLM has a mind of its own... :shake:
speaking of DLM (loosely at least) - do IDnet support seamless rate adaption? Was reading something about it today and I have hardware that supports it but from the looks of the RFCs it was never a confirmed standard? Looks like what DLM should be but without the resyncs.
Not sure about SRA but since BT provide the local connection and backbone would they not control its availability. It may be possible with other suppliers of ADSL2+ i.e LLU
I agree, Steve. AFAIK, BT do not yet offer the service.
Quote from: Steve on Jan 13, 2010, 23:05:22
Not sure about SRA but since BT provide the local connection and backbone would they not control its availability. It may be possible with other suppliers of ADSL2+ i.e LLU
good point, didn't look at it that way :)