In case you haven't seen the announcement:
We will be performing some core network maintenance tomorrow. This is to install some new equipment to add further resiliance into the network. No disruption to service is planned but, as with any work of this nature, service is At Risk.
Where was that announced, Rik, I have nothing in my mailbox?
I see it's on the website http://www.idnet.net/support/status.jsp
On the RSS feed, Glenn.
OK, I don't get the feed at work.
I don't get it at all, so thanks for the heads up, Rik, as I don't tend to check the website every day.
I dropped about 11 minutes ago, I assume this is related.
(Note: looks to be just a PPP drop)
Not necessarily, I haven't seen any effects yet, but then it could depend on factors I don't know about.
Things seem a bit slower than normal today...or it could be me ;D Typical, its back to normal as soon as I type that.
Well, the ADSL never dropped so I guess it was not something at the exchange, could be a coincidence but I just assumed given the announcement something was going on. It's fine anyway. It tested the new ADSL2+ router came back up.
As I say, it's possible that there will be a rolling effect that hasn't reached me yet. While I know what's happening, I don't know the exact details of the effects.
Quote from: Gary on Oct 29, 2011, 10:35:57
Things seem a bit slower than normal today...or it could be me ;D Typical, its back to normal as soon as I type that.
I suspect that's symptomatic of the routing changes kicking in, Gary. I've seen a few slow patches too.
just looked at router logs and I had a drop at about 10.05 till 10.18
was just getting a good run too :)
Just had a four or five minute outage. No mail or web access. Seems to have returned now.
Same here.
Yes I got (another) drop too. Suffering a few routing glitches at the minute, might take a few moments for the computers here to catch up with what's going on I guess.
Edit: 13:11 Suddenly the routing is back.
My PPP went down for around 5 minutes also, back now.
just had another 30min drop.router was connected but still got no sites for 15 mins after it was back up.
I might have to venture out the house or even read a paper..........OR MAKE GENERAL CHIT CHAT WITH THE FAMILY
:o :o :o :o
Whatever next :D
The work is now completed.
:thumb: not that I've seen any problems apart from the Forum and the mail briefly.
Same here, Ray.
Thanks for the heads up. You'd think updates like this would be emailed to each customer but that's probably too sensible.
We try to fill in the gaps, Griff. ;) Of course, if people take the RSS feed (and I do recommend it), they will have received notification.
I was wondering why the net was slow today, glad I came here to check.
Speed is still a bit slow. Hopefully it'll pick up soon.
Speed is fine here.
(http://www.speedtest.net/android/97545002.png)
Not so good here :(
Can you run a BT test and see what your profile is. Today's work should not have affected speeds.
1010ms to Machester, yikes! I get half that to Buenos Aires. I suspect it's more than just a profile issue with that lag.
Unplug your router for 30 minutes then plug it back in again and test using an ethernet cable, ensuring nothing or noone else is using your connection when you run the test.
vitriol is using the Speedtest Android app which is notoriously useless and explains the massive latency and low speed.
Could be that android is downloading updates anyway.
Should always test with an ethernet link.
Quote from: .Griff. on Oct 29, 2011, 19:17:14
vitriol is using the Speedtest Android app which is notoriously useless and explains the massive latency and low speed.
PC Test
(http://www.speedtest.net/result/1562533328.png)
Not much better.
BT Speedtest attached.
It started at about 11 this morning.
Router stats
ADSL Link Downstream Upstream
Connection Speed 8128 kbps 448 kbps
Line Attenuation 21.0 db 10.5 db
Noise Margin 8.3 db 22.0 db
Ping
C:\Users\vitriol>ping www.idnet.com
Pinging www.idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=576ms TTL=59
Reply from 212.69.36.10: bytes=32 time=505ms TTL=59
Reply from 212.69.36.10: bytes=32 time=680ms TTL=59
Reply from 212.69.36.10: bytes=32 time=509ms TTL=59
Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 505ms, Maximum = 680ms, Average = 567ms
Tracert
C:\Users\vitriol>tracert www.idnet.com
Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.1
2 475 ms 450 ms 548 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 415 ms 413 ms 504 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 330 ms 388 ms 456 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 512 ms 499 ms 580 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 667 ms 631 ms 549 ms www.idnet.net [212.69.36.10]
Trace complete.
2nd hop is pretty bad, problem at idnet?
If this is an ethernet connection to the router obviously something's not right. The BT Speedtest shows evidence of a stable connection between the router and the local exchange. The Idnet network for me is performing well i.e. wifi trace route
1 192.168.1.254 (192.168.1.254) 4.788 ms 2.202 ms 1.838 ms
2 telehouse-gw2-lo1.idnet.net (212.69.63.51) 13.579 ms 12.914 ms 13.237 ms
3 telehouse-gw5-e4-400.idnet.net (212.69.63.245) 14.144 ms 13.025 ms 12.912 ms
4 redbus-gw2-g0-1-331.idnet.net (212.69.63.5) 14.065 ms 16.352 ms 14.848 ms
5 redbus-gw1-fa2-0-300.idnet.net (212.69.63.225) 14.299 ms 14.158 ms 13.822 ms
6 www.idnet.net (212.69.36.10) 14.164 ms 15.091 ms 14.195 ms
So my guess is either exchange congestion/fault or something your side of the master socket is failing. The Android speedtest would seem to rule out anything your side of the router though. I appreciate the Android speedtest is not the best but the result seems to fit in with the others.
Thanks Steve,
I'll leave it a few more hours, guess I'll be watching the X Factor instead :(
(http://www.speedtest.net/android/97673874.png)
Back to normal it would seem. Weird.
Back to life in the slow lane sigh
(http://www.speedtest.net/result/1563441203.png)
Ping
C:\Users\vitriol>ping www.idnet.com
Pinging www.idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=667ms TTL=59
Reply from 212.69.36.10: bytes=32 time=581ms TTL=59
Reply from 212.69.36.10: bytes=32 time=456ms TTL=59
Reply from 212.69.36.10: bytes=32 time=507ms TTL=59
Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 456ms, Maximum = 667ms, Average = 552ms
Tracert
C:\Users\vitriol>tracert www.idnet.com
Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.1
2 643 ms 574 ms 522 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 528 ms 558 ms 471 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 325 ms 353 ms 384 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 739 ms 581 ms 582 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 536 ms 582 ms 489 ms www.idnet.net [212.69.36.10]
It's becoming really annoying, I've rebooted router and even powered it off for a couple of hours, as my previous post at 2am is confusing things a little.
Any further suggestions?
Talk to support tomorrow. I don't think it's anything to do with yesterday's work or we'd have more people complaining. BT exchange congestion seems the most likely culprit.
For comparison:
tracert www.idnet.com
Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms 1 ms 192.168.1.254
2 12 ms 11 ms 11 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 12 ms 13 ms 11 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 13 ms 11 ms 11 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 14 ms 11 ms 13 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 14 ms 12 ms 13 ms www.idnet.net [212.69.36.10]
Trace complete.
Just asked my sister to do a speedtest. She is with BT internet and is connected to the same exchange. She lives about 400 yards further away from the exchange than me.
She is reporting a ping of 56 and download speed of 6.86 and 0.38 up.
She's not necessarily on the same virtual pathway at the exchange, support should be able to find out if any of the VPs are congested though.
But can they do anything about it?
http://www.idnetters.co.uk/forums/index.php/topic,27354.0.html
I just had another glitch... possibly unrelated, but the 2nd or 3rd this weekend.
Edit: hmm, speed went down so maybe the SNR Margin got too low. I'm not very familiar with this ADSL2 business, I hope it doesn't keep this up.
Sounds like a resync, have you kept an eye on the router's stats?
Currently my SNR margin is 12 with loop attenuation 29. RX errors are 59/88911287, no TX errors. I think I mentioned somewhere though that at peak times the SNR margin goes down to about 6. Down rate is 12.3Mbit.
Tell me a bit about your phone wiring, do you have extensions, what's connected to the line and where is the router plugged in?
As I understand it's a master socket (there are two phone lines here), there is a (new) ADSLNation filter with a 5m RJ-11 cable to the modem and another 3m RJ-11 cable to a dial-up fax modem. The voice phones are on the other phone line, which has a socket in a completely different room.
It might just be worth checking at the test socket, behind the ADSL Nation faceplate, to eliminate any possibility of a fault in that.
Sorry I think I confused you, it's not a faceplate, that's still the original BT one. It's a dongle filter thing attached to it. If it keeps happening just bypass the filter then? Been fine for a while now but obviously the ADSL1 never went down except when there was problems. Maybe the slightly slower sync rate will keep it stable, I hope.
OK, remove the BT faceplate and plug the soap on a rope into the test socket which will be revealed.