Ping times Jan 28 onwards

Started by MarkE, Jan 28, 2009, 13:49:28

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Dopamine

My pings are now varying again. Fast for several minutes, then slow again, then back to normal. Very strange. This is how it's been for several days.

All yesterday evening I was getting periods of 2 or 3 minutes where I couldn't access any sites at all, yet there was no connection loss, no PPP drop, and most strangely of all a live radio feed I was listening to on www.soma.fm kept on playing smoothly. I was up late too, until 3am, so I'm pretty sure it has nothing to do with congestion.

I do hope this is sorted before much longer.

Rik

The connection issues may well have been the router problem that Simon has covered in announcements. The pings could be the congested central within IDNet, or they might be exchange congestion at work. Have a word with support, and see what they can do to help you.
Rik
--------------------

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

talos

Results from http://www.speed.io
(Copied on 2009-02-12 19:35:24)
Download: 1651 Kbit/s
Upload : 383 kbit/s
Connects : 1920 conn/min
Ping: 44 ms

Not so bad at the moment, but it does seem to vary with the time of day, what might cause that?

Glenn

Congestion at the exchange, maybe the central you are on gets congested at time too?
Glenn
--------------------

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

goingonholiday

I understand there are some problems - any update on when a permanent fix will be in place?  I've lost connection at various times since the january update, pre january was getting stable 3mb+ consistently, now down to 1.5mb if lucky and unstable?  Ping below, any suggestions very welcome? - don't mind paying when service is good but a bit fed up to be honest.

Pinged www.idnet.co.uk and getting between 160ms and 180ms - typical one below
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 166ms, Maximum = 181ms, Average = 173ms

Glenn

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

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

talos

Just a suggestion, have you tried rebooting your modem?, it's worked for me and a few others, but if you hang about for a while
I'm sure someone more knowledgeable will be along soon or give Idnet a call in the morning.

goingonholiday

Thanks I have tried the router and will try leaving it off tonight.  The minor irritation for me is working full time means I'm never in when IDNet are available on the phone!  I'll switch off tonight and see if it's any better tomorrow night.

If anyone from IDNet reads then I think a definitive when you expect everything to be fixed and back to normal is needed rather than the techy details of what's broken!


Simon

Quote from: goingonholiday on Feb 12, 2009, 21:04:20
If anyone from IDNet reads then I think a definitive when you expect everything to be fixed and back to normal is needed rather than the techy details of what's broken!

I understand the frustrations you feel, but with things of this nature, it would be irresponsible for IDNet to make promises of a definite time on an overall fix, as there are several factors at play, some of which haven't played nicely with each other.  That said, things are now looking better for many users, so we (on the forum) are hopeful that the improvements continue.  :)

If you continue to have problems, drop them an email, and I'm sure it could be arranged for someone to call you at a convenient time.
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

David

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\David>ping Idnet.net

Pinging Idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=141ms TTL=59
Reply from 212.69.36.10: bytes=32 time=165ms TTL=59
Reply from 212.69.36.10: bytes=32 time=128ms TTL=59
Reply from 212.69.36.10: bytes=32 time=117ms 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 = 117ms, Maximum = 165ms, Average = 137ms

C:\Users\David>

Shot up again
Many hammer all over the wall and believe that with each blow they hit the nail on the head.

Steve

Mine for a change have been good all evening. Perhaps David try giving the router a kick again if its effecting your browsing etc. If its still poor perhaps a word with support tomorrow to see if they can shed some light.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

David

Thanks Steve worth a try I guess   ???
Many hammer all over the wall and believe that with each blow they hit the nail on the head.

Lance

Goingonholiday - if your throughput has fallen it seems this is going to be partly unrelated to the other issues. Does your router tell you if you have lost sync or just ppp?
Lance
_____

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

vitriol

Very good at 22:50

C:\Users\vitriol>ping 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=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms 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 = 22ms, Maximum = 24ms, Average = 22ms

zappaDPJ

I don't have any supporting data but the last two evenings have been the worst so far for me. Pings to www.idnet.com average 170ms at peak times and well in excess of 300ms into the Telia network and beyond. At off peak it's 13ms to idnet and 35ms to Telia. I've tried router restarts when things are bad but it makes no difference at all.
zap
--------------------

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

Simon

Speak to IDNet, Zap, as things should be levelling out now, but they may be able to give something a prod for you.
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

zappaDPJ

I think I will do, I'll run a ping plot tomorrow and mail it off to them. Thanks :)
zap
--------------------

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

uxbod

Yep pinging the DNS server did seem to slow down in the early part of the evening ... flattened out again though.

[attachment deleted by admin]

uxbod

Well now on SuperMax and with Simon_IDNET help very pleased with the result :)


Rik

Rik
--------------------

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

uxbod

Plus taking out a Cisco contract and now latest IOS ... worth every penny :)

Rik

These are my pings in the past hour or so...

[attachment deleted by admin]
Rik
--------------------

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

goingonholiday

My pings are back to normal today and speed has returned - hurray!

Lance, Unfortunately your question didn't mean anything to me, had a look at router admin screen and nothing sprung out as answering the question!  Hoping things are back to normal so will see what happens.

thanks

Sebby


goingonholiday

It's a Belkin - comes up as Belkin54g as the default name.

Connection has dropped once tonight and pings are back all over the place so may have spoken too soon!  Is there anything I should look for?