Whats happening???

Started by Rudds, Jun 07, 2010, 20:54:41

Previous topic - Next topic

0 Members and 3 Guests are viewing this topic.

Steve

We have a hard task master who's probably enjoying his tea >:D
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Rudds

Can we rule out whether this is a particular area affected or not.

I'm near the Leicestershire/Northamptonshire border, anyone else this way affected?
Paul

Steve

There is list of std codes affected by a current BT outage here http://status.zensupport.co.uk/outages/

01179   01202   01237
01264   01271   01276
01280   01288   01300
01305   01308   01344
01380   01392   01460
01488   01489   01491
01494   01503   01579
01590   01626   01635
01749   01761   01793
01794   01822   01934
01984   0238031   0238032
0238034   0238036   0238039
0238048   0238049   0238055
0238057   0238058   0238067
0238090   0238094   

Partial clear 01772
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

My number is listed there Steve.
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

Quote from: Rudds on Jun 07, 2010, 21:49:54
Can we rule out whether this is a particular area affected or not.

I'm near the Leicestershire/Northamptonshire border, anyone else this way affected?

Sandhurst, Berkshire.
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

gyruss

I am getting this tonight, i would love to get over 1meg



have emailed support@idnet.com as my issues are rather ongoing lately than just the one night.
Jase


Rudds

Dropped out again



My exchange is not on list.
Paul

Simon

Quote from: Sirian on Jun 07, 2010, 21:42:50
Thanks for the replies - my speed has recovered to about 3 mb/s now - was explaining in a PM that I'm a newbie and not sure how to do router stats and the like (not sure = haven't a clue) anyone point me to any resources either online or on this forum.  Hey great to know that there is "help out there". . .

Greatly appreciated
/?


You might find this a useful read, Andy:

http://www.idnetters.co.uk/forums/index.php?topic=1904.0
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

gyruss

Ping times are.. interesting.

Reply from 212.69.63.243: bytes=32 time=327ms TTL=253
Reply from 212.69.63.243: bytes=32 time=347ms TTL=253
Reply from 212.69.63.243: bytes=32 time=363ms TTL=253
Reply from 212.69.63.243: bytes=32 time=351ms TTL=253
Reply from 212.69.63.243: bytes=32 time=197ms TTL=253
Reply from 212.69.63.243: bytes=32 time=86ms TTL=253
Reply from 212.69.63.243: bytes=32 time=294ms TTL=253
Reply from 212.69.63.243: bytes=32 time=178ms TTL=253
Reply from 212.69.63.243: bytes=32 time=71ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=34ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=68ms TTL=253
Reply from 212.69.63.243: bytes=32 time=382ms TTL=253
Reply from 212.69.63.243: bytes=32 time=696ms TTL=253
Reply from 212.69.63.243: bytes=32 time=1225ms TTL=253
Reply from 212.69.63.243: bytes=32 time=80ms TTL=253
Reply from 212.69.63.243: bytes=32 time=34ms TTL=253
Reply from 212.69.63.243: bytes=32 time=154ms TTL=253
Reply from 212.69.63.243: bytes=32 time=286ms TTL=253
Reply from 212.69.63.243: bytes=32 time=285ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=298ms TTL=253
Reply from 212.69.63.243: bytes=32 time=945ms TTL=253
Reply from 212.69.63.243: bytes=32 time=51ms TTL=253
Reply from 212.69.63.243: bytes=32 time=194ms TTL=253
Reply from 212.69.63.243: bytes=32 time=88ms TTL=253
Reply from 212.69.63.243: bytes=32 time=344ms TTL=253
Reply from 212.69.63.243: bytes=32 time=162ms TTL=253
Reply from 212.69.63.243: bytes=32 time=116ms TTL=253
Reply from 212.69.63.243: bytes=32 time=34ms TTL=253
Reply from 212.69.63.243: bytes=32 time=35ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=34ms TTL=253
Reply from 212.69.63.243: bytes=32 time=36ms TTL=253
Reply from 212.69.63.243: bytes=32 time=35ms TTL=253
Reply from 212.69.63.243: bytes=32 time=35ms TTL=253
Reply from 212.69.63.243: bytes=32 time=36ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=34ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=34ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=34ms TTL=253
Reply from 212.69.63.243: bytes=32 time=33ms TTL=253
Reply from 212.69.63.243: bytes=32 time=1306ms TTL=253
Reply from 212.69.63.243: bytes=32 time=1178ms TTL=253
Reply from 212.69.63.243: bytes=32 time=1903ms TTL=253
Reply from 212.69.63.243: bytes=32 time=3298ms TTL=253
Request timed out.
Request timed out.
Request timed out.
Reply from 212.69.63.243: bytes=32 time=2987ms TTL=253
Reply from 212.69.63.243: bytes=32 time=2946ms TTL=253
Request timed out.
Reply from 212.69.63.243: bytes=32 time=3517ms TTL=253
Request timed out.
Reply from 212.69.63.243: bytes=32 time=3394ms TTL=253
Jase


Steve

I'm not sure what priority is given to pings on that server some of the variability maybe due to low priority. I usually use this one. www.idnet.net
PING www.idnet.net (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=9.421 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=9.268 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=10.149 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=10.964 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=10.991 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=9.550 ms
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=9.640 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=9.592 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=10.177 ms
64 bytes from 212.69.36.10: icmp_seq=9 ttl=59 time=9.958 ms
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Ray

Speeds somewhat lower than normal here, I'm in south Leicestershire on 01455 exchange

Ray
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sirian

Thanks Steve and Simon - I'm reading through the links you sent - great to get so much help so quickly . . .

Thanks also for the Karmas - not sure what they mean but it sounds good . .

Sirian
/?

Steve

AAISP says the Reading node is causing problems http://aaisp-btmso.blogspot.com/
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

gyruss

I get similar to www.idnet.net.

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=1775ms TTL=59
Reply from 212.69.36.10: bytes=32 time=1491ms TTL=59
Reply from 212.69.36.10: bytes=32 time=568ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=1188ms TTL=59
Reply from 212.69.36.10: bytes=32 time=921ms TTL=59
Reply from 212.69.36.10: bytes=32 time=106ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59
Reply from 212.69.36.10: bytes=32 time=380ms TTL=59
Reply from 212.69.36.10: bytes=32 time=1227ms TTL=59
Reply from 212.69.36.10: bytes=32 time=396ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59
Reply from 212.69.36.10: bytes=32 time=41ms TTL=59
Reply from 212.69.36.10: bytes=32 time=2894ms TTL=59
Reply from 212.69.36.10: bytes=32 time=2098ms TTL=59
Reply from 212.69.36.10: bytes=32 time=553ms TTL=59
Reply from 212.69.36.10: bytes=32 time=450ms TTL=59
Reply from 212.69.36.10: bytes=32 time=1945ms TTL=59
Reply from 212.69.36.10: bytes=32 time=1255ms TTL=59
Reply from 212.69.36.10: bytes=32 time=962ms TTL=59
Reply from 212.69.36.10: bytes=32 time=81ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 2894ms, Average = 587ms
Jase


Glenn

Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Simon

Quote from: Sirian on Jun 07, 2010, 22:06:25
Thanks Steve and Simon - I'm reading through the links you sent - great to get so much help so quickly . . .

Thanks also for the Karmas - not sure what they mean but it sounds good . .

Sirian
/?


Karmas are just a bit of fun, Andy.  We use them to welcome new members, give thanks for useful posts, good jokes, celebrations such as Birthdays, etc, and after a few posts, you will be able to award them too.  It's just our little way of showing gratitude for good deeds.  :)
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Sirian

Thanks Simon - in that case here's a Karma to everyone on this thread . .

:karma: :karma:

/?

Rudds

Oh well gotta go bed now, hopefully IDNet will get back to its normal status very soon. :thumb:

Thanks everyone
Paul

Glenn

Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

The few I looked at are showing diddly squat,-green
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

I looked at a few, and there aren't any changing their pages as yet.
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

There's a lot of BT issues tonight though.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Sirian

Just did another BT Speed Test and my speeds have recovered substantially - still not as good as on previous evenings but heading in the right direction. . .  Thanks again for the help on the forum - still working on router stats . .

Test1 comprises of Best Effort Test:  -provides background information.

Download  Speed
5430 Kbps
 
0 Kbps 7150 Kbps
Max Achievable Speed

Download speedachieved during the test was - 5430 Kbps
For your connection, the acceptable range of speeds is 600-7150 Kbps.
Additional Information:
Your DSL Connection Rate :8128 Kbps(DOWN-STREAM), 448 Kbps(UP-STREAM)
IP Profile for your line is - 7150 Kbps


Sirian
/?

Steve

#48
Whats the router model Sirian?

The BT speedtest is fine ,adslmax full sync and max IP profile,just the throughputs is a bit down
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Sirian

It's a Speedtouch 585 V6

/?