|
|
Did any one else just go through about 5 minutes when nothing would connect, followed by a few minutes of high packet loss?
|
|
|
Not looking good here:
C:\Program Files\Support Tools>pathping www.idnet.net
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
0 dad [192.168.1.104]
1 192.168.1.254
2 telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 telehouse-gw.idnet.net [212.69.40.1]
4 redbus-gw.idnet.net [212.69.63.1]
5 www.idnet.net [212.69.36.10]
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.254
1/ 100 = 1% |
2 309ms 2/ 100 = 2% 1/ 100 = 1% telehouse-bb-gw1-vpdn.idnet.net
0/ 100 = 0% |
3 377ms 1/ 100 = 1% 0/ 100 = 0% telehouse-gw.idnet.net
0/ 100 = 0% |
4 391ms 1/ 100 = 1% 0/ 100 = 0% redbus-gw.idnet.net
1/ 100 = 1% |
5 365ms 2/ 100 = 2% 0/ 100 = 0% www.idnet.net
Trace complete.
"604!!"
|
|
|
well it is all good here
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.2.1
2 24 ms 22 ms 24 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 24 ms 25 ms 24 ms telehouse-gw.idnet.net [212.69.40.1]
4 25 ms 24 ms 25 ms redbus-gw.idnet.net [212.69.63.1]
5 25 ms 26 ms 24 ms www.idnet.net [212.69.36.10]
richard
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
Still getting slow pings from 212.69.40.1 over 400ms every 60secs or so.
It's been going on for weeks now, though it was being sorted, silly me.
John
The Glen of Tranquillity
|
|
|
|
I have just had a period of about 4 minutes when the PC / router, could not connect to various websites, including IDNet. Which also happened last night, at about the same time. BT checking my 2MB line. ? My other PC on a sepate MaxDsl connection, carried on surfing.
Interesting............................! ? ! ? ! ?
|
|
|
Hmmm. I'm not the only one then.
John
The Glen of Tranquillity
|
|
|
|
Hmm same problem here, desconnected about 15min ago and also happend around the same time yesterday
|
|
|
Everything has been fine here for weeks and weeks now.
|
|
|
Yes, things have been fine for weeks. I suspect that some of the problems may not have anything to do with IDNet or BT.
Have a look at the Telewest & NTL furums. Problems over there too, apparently.
As for those on Tiscalt LLU & at PN the less said the better.
As prophecied, the wheels seem to have well & truly fallen off, bigtime...............!!!!
Edited by Vigilant1 (Sun 03-Sep-06 20:53:59)
|
|
|
Perhaps i should clarify my statement about things being fine for weeks and weeks. I have been with IDNet since January and everything has been fine since then, no problems at all even when being changed to ADSLMax in April.
I pinched the wheels.
|
|
|
|
Curiously enough, my MaxDsl connection sailed on through the recent general British broadband weekends of disruptiom. Perhaps Sky are testing their much hyped Internet service, or one of their bandwidth stealing applications?
Incidentally, I would not touch Sky with an extra long bargepole..................!
|
|
|
I had about 15 mins of no service at all last night, it was really weird i was online got booted off, went to reconnect it did then it booted me again, it proceeded to do this about 8 or 10 times for the next 15min then it settled down after i gave up and turned my router off and came back later!
Proud To Be An IDnetter!
|
|
|
In reply to:
I had about 15 mins of no service at all last night .....
What time was this? I had a 20 minute black hole last night, lasting for ~20 mins. Rebooting router or switching off for a while did not cure this. DSL was up, but I couldn't establish PPP.
Only after leaving it a while and trying several attempts later I finally manged to connect.
|
|
|
it was around 19:40 to 20:00 that i was offline for, i gave up at around 10mins to eight then i switched router off and chilled for abit then i restarted the router and all was fine.
Proud To Be An IDnetter!
|
|
|
It's just happened again, although I didn't get the high pings afterwards; this time I was able to get some traceroutes. I had to tracert to an IP address and use -d because nothing would resolve:
At 7.30 this morning (1st hop is my router):
1 * * * Request timed out.
2 14 ms 14 ms 14 ms 212.69.63.45
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
How it looks if it's working:
1 * * * Request timed out.
2 15 ms 15 ms 14 ms 212.69.63.45
3 16 ms 15 ms 15 ms 212.69.63.9
4 16 ms 16 ms 15 ms 213.232.64.51
5 16 ms 19 ms 16 ms 213.206.128.104
6 16 ms 16 ms 15 ms 213.206.129.152
7 16 ms 16 ms 16 ms 213.206.131.22
8 16 ms 18 ms 16 ms 4.68.116.98
9 16 ms 16 ms 17 ms 4.68.128.110
10 16 ms 16 ms 17 ms 4.68.117.41
11 85 ms 85 ms 85 ms 195.50.116.154
12 88 ms 89 ms 87 ms <my office IP address>
Trace complete.
I've only been with IDNet for a month, but I've found the connection to be less stable than my previous f2s one. If this carries on I'll be seriously considering moving on again.
|
|
|
In reply to:
At 7.30 this morning (1st hop is my router):
1 * * * Request timed out.
Sorry if I am missing something obvious, but shouldn't your first hop from pc to router always be < 1ms. Timing out between PC and router would seem to indicate a problem all of its own.
Regards
Doug
|
|
|
No, it just means that my router doesn't respond to pings.
Edit: I'll qualify that by explaining I don't have individual control over responses to pings from the WAN & LAN - it's on or off for both.
Edited by s7uar7 (Thu 07-Sep-06 08:19:51)
|
|
|
|
Hi s7uar7
We were working on the network this morning. Sorry for any inconvenience.
Regards
Simon
|
|
The above post has been made by an ISP REPRESENTATIVE (although not necessarily the ISP being discussed in the post).
|
|
|
I have been with IDNet since February this year and have had consistant and stable connection. I normally only lose connection when I reboot my router or when BT have work to do. Only twice have I lost connection to IDnet for a short period when they were working on their network. Nothing but excellent experience with them.
I realise some people have problems with pingie things but I don't play games so will never have an effect on me.
It seems all the complaints are from a few people who have these ping problems, hardly any other complaints at all.
Edited by deleted (Thu 07-Sep-06 10:34:10)
|
|
|
How odd. Same with me, but about 1 hour earlier. My connection died at about 18:40 and was dead for at least 20 minutes. Then went out shopping. On my return, about 1.5 hours later, switched on the router again and all was fine.
Methinks it's time that the IDNet customer site needs a "planned maintenance" page.
IDNet Broadband Home Max
One of the lucky ones
Sync: 8128kb/s MSR: 8128kb/s FTR: 5689kb/s
Noise Margin: 15.5dB (DS) 27.0dB (US)
Attenuation: 19.0dB (DS) 7.5dB (US)
Click for Speedtest result
|
|
|
|
Hi cjtc
We didn't do any maintenance last night.
Simon
|
|
The above post has been made by an ISP REPRESENTATIVE (although not necessarily the ISP being discussed in the post).
|
|
|
|
Check up on this in case it is relevant.:
News - September 5, 2006
BT's Exchange Maintenance Work
By: MarkJ @ 12:39 PM - Comments () - SendNews (HERE) LinkNews (HERE)ADSLGuide reports that BT is to carry out a raft of maintenance and upgrade work on 30 DSLAM (broadband) exchanges per night until October next month:
The schedule split down into regions of the UK - shown below.
* Central Midlands 4th September and 5th September
* South Midlands 6th September
* West Midlands 7th September
* East Midlands 8th to 13th September
* North Scotland 14th September
* West Scotland 15th September to 18th September
* East Scotland 19th September
* Wales (North) 20th September
* Northern Ireland 21st September
* East Anglia 22nd September to 25th September
* South Downs 26th September
* Southampton 27th September
* Severn Side 28th September
* South Wales 29th September
* North London 2nd October
* South London 3rd October
* Central London 4th October
* North Downs 5th October
* Thamesway 6th October
* Mid Yorkshire 9th October
* South Lancashire 10th October
* Lancashire 11th October
* Liverpool 12th October
* Manchester 12th October
* North East 13th October
* Cornwall 13th October
The upgrades will take place between midnight and 6am, quite possibly resulting in downtime of roughly 30 minutes. Precisely what BT is doing we do not know, although it
|
|
|
|
~18:55 - 19:15 here that evening. Has been OK since though .....
|
|
|
No Simon, it was Monday night we were talking about ... at least, that's what I was talking about
IDNet Broadband Home Max
One of the lucky ones
Sync: 8128kb/s MSR: 8128kb/s FTR: 5689kb/s
Noise Margin: 15.5dB (DS) 27.0dB (US)
Attenuation: 19.0dB (DS) 7.5dB (US)
Click for Speedtest result
|
|
|
Ah, OK. Well, we we're doing anything that night either. We would only ever carry out planned mainenance out of peak time.
Cheers
Simon
|
|
The above post has been made by an ISP REPRESENTATIVE (although not necessarily the ISP being discussed in the post).
|
|
|
Can only have been BT then, particularly since outages seemed to be spaced about an hour apart in various locations. No sweat. Still more than happy with the service you provide.
IDNet Broadband Home Max
One of the lucky ones
Sync: 8128kb/s MSR: 8128kb/s FTR: 5689kb/s
Noise Margin: 15.5dB (DS) 27.0dB (US)
Attenuation: 19.0dB (DS) 7.5dB (US)
Click for Speedtest result
|