High pings again

Started by glen, Jul 20, 2009, 10:34:43

Previous topic - Next topic

0 Members and 3 Guests are viewing this topic.

Sebby


Simon_idnet

We're seeing a high level or traffic today due to the Ashes (the BBC site crashed a few mins ago) which is causing some congestion on our 20CN links. 21CN traffic is not so high.
Simon

Rik

Thanks, Simon. Bloody cricket. ;D
Rik
--------------------

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

Simon

Thanks for the heads up, Simon.  :)
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

If the game goes into a 5th day, the UK internet will grind to a halt
Glenn
--------------------

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

Simon

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

Wags

Anyone else having high pings tonight? Playing COD4 (Maidenhead based server) they are shooting up from 35 to 150ms and quite erratic.

Lance

My pings as far as j could tell on the pc earlier were absolutely fine ( ie quick loading of pages when browsing).

If you can reset your ppp session innyour router settings, it may be worth trying that.
Lance
_____

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

juiceuk

Trying to play battlefield 2142 with pings going from low twenties to over 150ms its no fun.

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=81ms TTL=59
Reply from 212.69.36.10: bytes=32 time=88ms TTL=59
Reply from 212.69.36.10: bytes=32 time=99ms TTL=59
Reply from 212.69.36.10: bytes=32 time=109ms TTL=59
Reply from 212.69.36.10: bytes=32 time=147ms TTL=59
Reply from 212.69.36.10: bytes=32 time=171ms TTL=59
Reply from 212.69.36.10: bytes=32 time=121ms TTL=59
Reply from 212.69.36.10: bytes=32 time=139ms TTL=59
Reply from 212.69.36.10: bytes=32 time=154ms TTL=59
Reply from 212.69.36.10: bytes=32 time=187ms TTL=59
Reply from 212.69.36.10: bytes=32 time=112ms TTL=59
Reply from 212.69.36.10: bytes=32 time=111ms TTL=59
Reply from 212.69.36.10: bytes=32 time=139ms TTL=59
Reply from 212.69.36.10: bytes=32 time=141ms TTL=59
Reply from 212.69.36.10: bytes=32 time=147ms TTL=59
Reply from 212.69.36.10: bytes=32 time=145ms TTL=59
Reply from 212.69.36.10: bytes=32 time=157ms TTL=59
Reply from 212.69.36.10: bytes=32 time=137ms TTL=59
Reply from 212.69.36.10: bytes=32 time=126ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 30ms, Maximum = 187ms, Average = 127ms

Whats up this time?

Lance

Have you tried a ppp reset or reboot?

I know it shouldn't be necessary, but until BT sort out the hostlink the network balancing is being watched very carefully.
Lance
_____

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

juiceuk

I'll reset the adsl line and see if that fixes it but it never normally works for me. Fingers crossed.

Lance

The best way to do it is to unplug the router get a drink and then ug it back in. That should give BT and their systems sufficient time to forget you. 
Lance
_____

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

Wags

#487
I will leave it for tonight and see what it's like tomorrow. I hope this is not a re-occurrence of the latency problems a lot of us endured a few weeks ago :fingers:. which would be unfortunate for a premium priced product :eyebrow:

(O2 LLU is now available at my exchange, which is tempting, but I understand they impose interleaving whether you want it or not which is a big negative for me, even if I would save a few quid as an O2 mobile phone user).

I see on the IDNET Network Status page that 'Broadband'   is showing as 'Sub-Optimal Service', so something is obviously awry.     

dujas

QuoteI see on the IDNET Network Status page that 'Broadband'   is showing as 'Sub-Optimal Service', so something is obviously awry.

That's probably because of:

QuoteService: Broadband
Posted: 08 September 2009 11:32:43
Updated: 08 September 2009 11:32:58
Status:In Progress
Message: BT have announced a major service outage affecting all London ADSL2+ (WBC) users. They say "exchanges are running hot and customers are experiencing intermittent connectivity and difficulty accessing www. Engineers are working on this as we speak however there is no clear ETA at this time."

The ping issue is ongoing and separate to the above, but it's starting to creep into the evenings.

Sebby

Quote from: Wags on Sep 08, 2009, 23:26:00
(O2 LLU is now available at my exchange, which is tempting, but I understand they impose interleaving whether you want it or not which is a big negative for me, even if I would save a few quid as an O2 mobile phone user).

Be (same network), on the other hand, do not. ;)

zappaDPJ

Quote from: Lance on Sep 08, 2009, 23:13:28
That should give BT and their systems sufficient time to forget you. 

I wish I could forget about BT so easily  ;D
zap
--------------------

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

Rik

 ;D

When I emailed Ian Livingston over the MK node failure last week, his only interest was that I seemed to know a lot of the terminology of WBC and, therefore, might be closely connected to BT in some way. I wonder what he'd say if I tried again over the London outage (can you imagine how many people must be affected?
Rik
--------------------

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

psp83

I've also noticed that over the last few days pings are up and down.

I've not had my usual 15ms ping in the evening for awhile now :(

Rik

Have you checked with support, Paul?
Rik
--------------------

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

psp83

Quote from: Rik on Sep 09, 2009, 12:37:08
Have you checked with support, Paul?

Not had time to be honest. I've not really got time to keep doing and logging tracerts :(

Wags

I rebooted the router today (turned off power for 30 mins and restarted) today at around midday to sort out the higher than normal pings that I have been experiencing.  Pings are back to 'normal' at around 15ms :thumb:, which is good, but whereas the connection has been solid all week at a sync of 6432 with downstream margin of 6db, the sync rate is now lower and the downstream margin looks dangerously low:

DSL Status:               Up           
DSL Modulation Mode:      GDMT         
DSL Path Mode:              FAST         
Downstream Rate:      5440 Kbps         
Upstream Rate:              448 Kbps         
Downstream Margin:      3 db         
Upstream Margin:      24 db         
Downstream Line Attenuation:      36         
Upstream Line Attenuation:      20         
           
Any thoughts as to what to do to get it back to how it was before the reboot? Should I just wait?
It was rebooted today at lunchtime.

Rik

It's down to local line conditions. If you're sure that there's nothing in your internal wiring to blame, or nothing else connected to the line, then there's little or nothing you can do. If you have access to a different router, it might be worth trying, but the low margin is likely to mean a re-sync sometime tonight. :(
Rik
--------------------

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

Wags

Thanks Rik. 

My internal wiring is all good now (you may recall I replaced the NTE5 plate with the ADSl nation faceplate, with the router plugged in this with CAT5e to my PCs).

I am always slightly apprehensive with a router reboot, especially when the sync and snr margin have been so solid for a week! :dunno:

Rik

Me too. I have kittens when I come back off holiday and power up the system. ;)
Rik
--------------------

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

Simon

You'll have litters by the end of the year then!  :D
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.