IDNet network problems

Started by Gary, Apr 15, 2015, 16:58:18

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

zappaDPJ

Here's mine for comparison.



Just like yesterday it's been better than it was Mon to Fri, I was able to watch F1 this afternoon with some occasional buffering. It's not so good now though, I'm getting a lot of major lag spikes and my latency is all over the place. Throughput is down but acceptable, nowhere near as bad as it was in the week.

zap
--------------------

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

Bill

#76
Very similar to mine, as expected :(



From 3pm to 5pm, and again from 7pm to 9pm (times approx, indicated by the red marker spikes) my connection was PPPoE from a MacBook direct to the modem, running on battery with no apps, just the OS. (edit- with wireless and IPv6 off)

Comparing it with yours, which is usually a bit worse than mine, I think it rules out my LAN as being the cause.


(The big red spike at ~10:30 was me finding out that I'd forgotten how to set up a PPPoE connection on a Mac :eek4:)
Bill
BQMs-  IPv4  IPv6

Bill

@lozcart: Actually, I think your BQM is showing a "lite" version of what Zappa and I are seeing on ours.
Bill
BQMs-  IPv4  IPv6

zappaDPJ

Exactly as I predicted my connection has become completely unusable again today. Why support can't see this from their side is utterly beyond me.




Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\zappaDPJ>ping idnet.com -n 100

Pinging idnet.com [212.69.36.207] with 32 bytes of data:
Reply from 212.69.36.207: bytes=32 time=26ms TTL=62
Reply from 212.69.36.207: bytes=32 time=22ms TTL=62
Reply from 212.69.36.207: bytes=32 time=61ms TTL=62
Reply from 212.69.36.207: bytes=32 time=37ms TTL=62
Reply from 212.69.36.207: bytes=32 time=67ms TTL=62
Reply from 212.69.36.207: bytes=32 time=49ms TTL=62
Reply from 212.69.36.207: bytes=32 time=41ms TTL=62
Reply from 212.69.36.207: bytes=32 time=56ms TTL=62
Reply from 212.69.36.207: bytes=32 time=38ms TTL=62
Reply from 212.69.36.207: bytes=32 time=52ms TTL=62
Reply from 212.69.36.207: bytes=32 time=38ms TTL=62
Reply from 212.69.36.207: bytes=32 time=46ms TTL=62
Reply from 212.69.36.207: bytes=32 time=42ms TTL=62
Reply from 212.69.36.207: bytes=32 time=39ms TTL=62
Reply from 212.69.36.207: bytes=32 time=60ms TTL=62
Reply from 212.69.36.207: bytes=32 time=42ms TTL=62
Reply from 212.69.36.207: bytes=32 time=57ms TTL=62
Reply from 212.69.36.207: bytes=32 time=81ms TTL=62
Reply from 212.69.36.207: bytes=32 time=56ms TTL=62
Reply from 212.69.36.207: bytes=32 time=100ms TTL=62
Reply from 212.69.36.207: bytes=32 time=66ms TTL=62
Reply from 212.69.36.207: bytes=32 time=87ms TTL=62
Request timed out.
Reply from 212.69.36.207: bytes=32 time=85ms TTL=62
Reply from 212.69.36.207: bytes=32 time=83ms TTL=62
Request timed out.
Request timed out.
Reply from 212.69.36.207: bytes=32 time=48ms TTL=62
Reply from 212.69.36.207: bytes=32 time=41ms TTL=62
Reply from 212.69.36.207: bytes=32 time=38ms TTL=62
Reply from 212.69.36.207: bytes=32 time=34ms TTL=62
Reply from 212.69.36.207: bytes=32 time=43ms TTL=62
Reply from 212.69.36.207: bytes=32 time=54ms TTL=62
Reply from 212.69.36.207: bytes=32 time=46ms TTL=62
Reply from 212.69.36.207: bytes=32 time=32ms TTL=62
Reply from 212.69.36.207: bytes=32 time=59ms TTL=62
Reply from 212.69.36.207: bytes=32 time=57ms TTL=62
Reply from 212.69.36.207: bytes=32 time=40ms TTL=62
Reply from 212.69.36.207: bytes=32 time=31ms TTL=62
Reply from 212.69.36.207: bytes=32 time=49ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=48ms TTL=62
Reply from 212.69.36.207: bytes=32 time=52ms TTL=62
Reply from 212.69.36.207: bytes=32 time=39ms TTL=62
Reply from 212.69.36.207: bytes=32 time=28ms TTL=62
Reply from 212.69.36.207: bytes=32 time=43ms TTL=62
Reply from 212.69.36.207: bytes=32 time=50ms TTL=62
Reply from 212.69.36.207: bytes=32 time=50ms TTL=62
Request timed out.
Reply from 212.69.36.207: bytes=32 time=53ms TTL=62
Reply from 212.69.36.207: bytes=32 time=24ms TTL=62
Reply from 212.69.36.207: bytes=32 time=28ms TTL=62
Reply from 212.69.36.207: bytes=32 time=36ms TTL=62
Reply from 212.69.36.207: bytes=32 time=31ms TTL=62
Reply from 212.69.36.207: bytes=32 time=39ms TTL=62
Reply from 212.69.36.207: bytes=32 time=38ms TTL=62
Reply from 212.69.36.207: bytes=32 time=49ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=31ms TTL=62
Reply from 212.69.36.207: bytes=32 time=41ms TTL=62
Reply from 212.69.36.207: bytes=32 time=30ms TTL=62
Reply from 212.69.36.207: bytes=32 time=41ms TTL=62
Reply from 212.69.36.207: bytes=32 time=28ms TTL=62
Reply from 212.69.36.207: bytes=32 time=28ms TTL=62
Reply from 212.69.36.207: bytes=32 time=32ms TTL=62
Reply from 212.69.36.207: bytes=32 time=58ms TTL=62
Reply from 212.69.36.207: bytes=32 time=28ms TTL=62
Reply from 212.69.36.207: bytes=32 time=40ms TTL=62
Reply from 212.69.36.207: bytes=32 time=49ms TTL=62
Reply from 212.69.36.207: bytes=32 time=51ms TTL=62
Reply from 212.69.36.207: bytes=32 time=39ms TTL=62
Reply from 212.69.36.207: bytes=32 time=47ms TTL=62
Reply from 212.69.36.207: bytes=32 time=55ms TTL=62
Reply from 212.69.36.207: bytes=32 time=44ms TTL=62
Reply from 212.69.36.207: bytes=32 time=25ms TTL=62
Reply from 212.69.36.207: bytes=32 time=46ms TTL=62
Reply from 212.69.36.207: bytes=32 time=41ms TTL=62
Reply from 212.69.36.207: bytes=32 time=35ms TTL=62
Reply from 212.69.36.207: bytes=32 time=59ms TTL=62
Reply from 212.69.36.207: bytes=32 time=48ms TTL=62
Reply from 212.69.36.207: bytes=32 time=47ms TTL=62
Request timed out.
Request timed out.
Reply from 212.69.36.207: bytes=32 time=70ms TTL=62
Request timed out.
Reply from 212.69.36.207: bytes=32 time=56ms TTL=62
Reply from 212.69.36.207: bytes=32 time=21ms TTL=62
Reply from 212.69.36.207: bytes=32 time=54ms TTL=62
Reply from 212.69.36.207: bytes=32 time=38ms TTL=62
Reply from 212.69.36.207: bytes=32 time=52ms TTL=62
Reply from 212.69.36.207: bytes=32 time=40ms TTL=62
Request timed out.
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=44ms TTL=62
Reply from 212.69.36.207: bytes=32 time=54ms TTL=62
Reply from 212.69.36.207: bytes=32 time=56ms TTL=62
Reply from 212.69.36.207: bytes=32 time=57ms TTL=62
Request timed out.
Request timed out.
Reply from 212.69.36.207: bytes=32 time=47ms TTL=62

Ping statistics for 212.69.36.207:
    Packets: Sent = 100, Received = 90, Lost = 10 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 100ms, Average = 45ms

C:\Users\zappaDPJ>
zap
--------------------

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

zappaDPJ

#79
And just to be sure that I've done everything required of me, here's the same data from a PPPoE connection.




C:\Users\zappaDPJ>ping idnet.com -n 100

Pinging idnet.com [212.69.36.207] with 32 bytes of data:
Reply from 212.69.36.207: bytes=32 time=26ms TTL=63
Reply from 212.69.36.207: bytes=32 time=56ms TTL=63
Reply from 212.69.36.207: bytes=32 time=27ms TTL=63
Reply from 212.69.36.207: bytes=32 time=58ms TTL=63
Reply from 212.69.36.207: bytes=32 time=24ms TTL=63
Reply from 212.69.36.207: bytes=32 time=28ms TTL=63
Reply from 212.69.36.207: bytes=32 time=60ms TTL=63
Reply from 212.69.36.207: bytes=32 time=51ms TTL=63
Reply from 212.69.36.207: bytes=32 time=51ms TTL=63
Reply from 212.69.36.207: bytes=32 time=61ms TTL=63
Reply from 212.69.36.207: bytes=32 time=49ms TTL=63
Reply from 212.69.36.207: bytes=32 time=75ms TTL=63
Request timed out.
Request timed out.
Reply from 212.69.36.207: bytes=32 time=54ms TTL=63
Reply from 212.69.36.207: bytes=32 time=32ms TTL=63
Reply from 212.69.36.207: bytes=32 time=48ms TTL=63
Request timed out.
Reply from 212.69.36.207: bytes=32 time=34ms TTL=63
Reply from 212.69.36.207: bytes=32 time=43ms TTL=63
Reply from 212.69.36.207: bytes=32 time=32ms TTL=63
Reply from 212.69.36.207: bytes=32 time=51ms TTL=63
Reply from 212.69.36.207: bytes=32 time=58ms TTL=63
Reply from 212.69.36.207: bytes=32 time=53ms TTL=63
Reply from 212.69.36.207: bytes=32 time=55ms TTL=63
Reply from 212.69.36.207: bytes=32 time=51ms TTL=63
Reply from 212.69.36.207: bytes=32 time=42ms TTL=63
Reply from 212.69.36.207: bytes=32 time=43ms TTL=63
Reply from 212.69.36.207: bytes=32 time=43ms TTL=63
Reply from 212.69.36.207: bytes=32 time=35ms TTL=63
Reply from 212.69.36.207: bytes=32 time=42ms TTL=63
Reply from 212.69.36.207: bytes=32 time=42ms TTL=63
Reply from 212.69.36.207: bytes=32 time=40ms TTL=63
Reply from 212.69.36.207: bytes=32 time=40ms TTL=63
Reply from 212.69.36.207: bytes=32 time=28ms TTL=63
Reply from 212.69.36.207: bytes=32 time=43ms TTL=63
Reply from 212.69.36.207: bytes=32 time=49ms TTL=63
Request timed out.
Reply from 212.69.36.207: bytes=32 time=39ms TTL=63
Reply from 212.69.36.207: bytes=32 time=33ms TTL=63
Reply from 212.69.36.207: bytes=32 time=55ms TTL=63
Reply from 212.69.36.207: bytes=32 time=30ms TTL=63
Reply from 212.69.36.207: bytes=32 time=45ms TTL=63
Reply from 212.69.36.207: bytes=32 time=35ms TTL=63
Reply from 212.69.36.207: bytes=32 time=38ms TTL=63
Reply from 212.69.36.207: bytes=32 time=28ms TTL=63
Reply from 212.69.36.207: bytes=32 time=34ms TTL=63
Reply from 212.69.36.207: bytes=32 time=38ms TTL=63
Reply from 212.69.36.207: bytes=32 time=33ms TTL=63
Reply from 212.69.36.207: bytes=32 time=40ms TTL=63
Reply from 212.69.36.207: bytes=32 time=37ms TTL=63
Reply from 212.69.36.207: bytes=32 time=38ms TTL=63
Reply from 212.69.36.207: bytes=32 time=27ms TTL=63
Reply from 212.69.36.207: bytes=32 time=26ms TTL=63
Reply from 212.69.36.207: bytes=32 time=19ms TTL=63
Reply from 212.69.36.207: bytes=32 time=43ms TTL=63
Reply from 212.69.36.207: bytes=32 time=18ms TTL=63
Reply from 212.69.36.207: bytes=32 time=33ms TTL=63
Reply from 212.69.36.207: bytes=32 time=46ms TTL=63
Reply from 212.69.36.207: bytes=32 time=55ms TTL=63
Reply from 212.69.36.207: bytes=32 time=57ms TTL=63
Request timed out.
Reply from 212.69.36.207: bytes=32 time=59ms TTL=63
Reply from 212.69.36.207: bytes=32 time=43ms TTL=63
Reply from 212.69.36.207: bytes=32 time=47ms TTL=63
Reply from 212.69.36.207: bytes=32 time=43ms TTL=63
Reply from 212.69.36.207: bytes=32 time=31ms TTL=63
Reply from 212.69.36.207: bytes=32 time=42ms TTL=63
Reply from 212.69.36.207: bytes=32 time=42ms TTL=63
Reply from 212.69.36.207: bytes=32 time=45ms TTL=63
Reply from 212.69.36.207: bytes=32 time=58ms TTL=63
Reply from 212.69.36.207: bytes=32 time=42ms TTL=63
Reply from 212.69.36.207: bytes=32 time=34ms TTL=63
Reply from 212.69.36.207: bytes=32 time=62ms TTL=63
Reply from 212.69.36.207: bytes=32 time=30ms TTL=63
Reply from 212.69.36.207: bytes=32 time=23ms TTL=63
Request timed out.
Reply from 212.69.36.207: bytes=32 time=29ms TTL=63
Reply from 212.69.36.207: bytes=32 time=39ms TTL=63
Request timed out.
Reply from 212.69.36.207: bytes=32 time=41ms TTL=63
Reply from 212.69.36.207: bytes=32 time=37ms TTL=63
Reply from 212.69.36.207: bytes=32 time=40ms TTL=63
Reply from 212.69.36.207: bytes=32 time=33ms TTL=63
Reply from 212.69.36.207: bytes=32 time=29ms TTL=63
Reply from 212.69.36.207: bytes=32 time=38ms TTL=63
Reply from 212.69.36.207: bytes=32 time=33ms TTL=63
Reply from 212.69.36.207: bytes=32 time=36ms TTL=63
Reply from 212.69.36.207: bytes=32 time=37ms TTL=63
Reply from 212.69.36.207: bytes=32 time=38ms TTL=63
Reply from 212.69.36.207: bytes=32 time=41ms TTL=63
Reply from 212.69.36.207: bytes=32 time=31ms TTL=63
Reply from 212.69.36.207: bytes=32 time=39ms TTL=63
Reply from 212.69.36.207: bytes=32 time=26ms TTL=63
Reply from 212.69.36.207: bytes=32 time=38ms TTL=63
Reply from 212.69.36.207: bytes=32 time=41ms TTL=63
Reply from 212.69.36.207: bytes=32 time=26ms TTL=63
Reply from 212.69.36.207: bytes=32 time=29ms TTL=63
Reply from 212.69.36.207: bytes=32 time=22ms TTL=63
Reply from 212.69.36.207: bytes=32 time=36ms TTL=63

Ping statistics for 212.69.36.207:
    Packets: Sent = 100, Received = 93, Lost = 7 (7% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 75ms, Average = 40ms

C:\Users\zappaDPJ>

My Router = Netgear Wireless-G WGR614v10 with the latest firmware

But let's be clear, the above data was gathered using a PPPoE connection.
zap
--------------------

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

Bill

At about 08:30 today I disconnected my router from the modem and used the MacBook to set up a PPPoE connection, as I did (twice) yesterday.

Apart from a couple of checks to make sure the connection was still live I did nothing whatever on the internet for the next two and a half hours or so.

BQM:



The problem may or may not be with IDNet but it sure as hell isn't on my LAN.
Bill
BQMs-  IPv4  IPv6

Bill

About 11:45 I swapped the modem for a spare, same type- HG512, model 3B.

You can see the spike, let's see what happens now...
Bill
BQMs-  IPv4  IPv6

Gary

No issues here, and the other two FTTC BQM's on craigs (not the dedicated IDnet one) since I'm not sure if that is IDNets as Simon D seems to think its not, show no issues like yours at all, Bill. I think last week was a read herring so to speak. Something occurred but may have been out of IDnets network, and my loosing sync with the ECI cab could have been a engineer fiddling (all ECI cabs have to have warming plates put in them as ECI Cab ventilation allows to much moisture in  :eyebrow: so I imagine with that, vectoring cards being put in cabs that and usual line card work going on there will be bumps on the way, also ECI G.inp seems to have ground to a halt. Its odd that you and Zap seem to have tandem issues though, what it is  :dunno:  Hope it gets sorted soon once and for all. 
Damned, if you do damned if you don't

Simon

#83
It seems it has to be something common with Zap's and Bill's connections, although they are not in the same locality.  Same equipment?   :dunno:

There's a little bit of redness on mine this morning, but nothing too bad. 

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

Bill

Quote from: Gary on Apr 20, 2015, 12:09:53Its odd that you and Zap seem to have tandem issues though

Yes it is, but as we're nowhere near each other, use different routers and different systems (Zappa, afaik, uses Windows, I use OS X and Linux) I don't see how it's likely to be anything on our systems... it's weird :(
Bill
BQMs-  IPv4  IPv6

Bill

Zappa's seems to have suddenly cleared up... what did he do?
Bill
BQMs-  IPv4  IPv6

Ray

Mine is still ok as well:-

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

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

Simon

Quote from: Bill on Apr 20, 2015, 12:29:30
Zappa's seems to have suddenly cleared up... what did he do?

Unplugged it?  ;D :out:
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Bill

Tbh that was my first thought too, but then realised that would give solid red!
Bill
BQMs-  IPv4  IPv6

zappaDPJ

Quote from: Bill on Apr 20, 2015, 12:29:30
Zappa's seems to have suddenly cleared up... what did he do?

I lost my rag while on the phone to support, 30 minutes later (according to my daughter) the Internet started working.

Compare these stats with what I posted earlier.




Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\zappaDPJ>ping idnet.com -n 100

Pinging idnet.com [212.69.36.207] with 32 bytes of data:
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62

Ping statistics for 212.69.36.207:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 19ms, Average = 18ms

C:\Users\zappaDPJ>


zap
--------------------

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

Bill

Well, I'd prefer to avoid doing that, hopefully whatever happened to yours will happen to mine :fingers:

Mine is improving, but a gentle decline in latency doesn't give me that warm feeling that it won't change its mind again...
Bill
BQMs-  IPv4  IPv6

Simon

No idea what they did, Zap?
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

zappaDPJ

I've just had a long chat with Brian, they did nothing and they are totally baffled. They are sending out a different modem/router to see what effect that might have.
zap
--------------------

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

Simon_idnet

Quote from: Simon on Apr 20, 2015, 14:11:04
No idea what they did, Zap?

Wish we could take the credit but we've not found anything that we *can* fiddle with to change things. All we can see is that Zap downloaded a lot between around 11am and noon - does that tally with your activity this morning Zap?

zappaDPJ

Quote from: Simon_idnet on Apr 20, 2015, 14:34:03
Wish we could take the credit but we've not found anything that we *can* fiddle with to change things. All we can see is that Zap downloaded a lot between around 11am and noon - does that tally with your activity this morning Zap?

It does Simon. My daughter downloaded a TV program to avoid stream buffering.

Quote from: Bill on Apr 20, 2015, 14:04:00
Well, I'd prefer to avoid doing that, hopefully whatever happened to yours will happen to mine :fingers:

Mine is improving, but a gentle decline in latency doesn't give me that warm feeling that it won't change its mind again...

Yours does seem to have improved slightly at exactly the same time as mine improved substantially. I wonder if it would be worth a modem/router reboot?
zap
--------------------

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

Bill

Quote from: zappaDPJ on Apr 20, 2015, 14:41:25
Yours does seem to have improved slightly at exactly the same time as mine improved substantially. I wonder if it would be worth a modem/router reboot?

The time resolution on those BQMs isn't good enough to be completely sure, but I think it was just after that abrupt drop that I swapped the modem for a spare.

My feeling at the moment is not to touch anything for a few days... if it seems to be working, don't try to fix it :P
Bill
BQMs-  IPv4  IPv6

Bill

Quote from: Simon_idnet on Apr 20, 2015, 14:34:03All we can see is that Zap downloaded a lot between around 11am and noon - does that tally with your activity this morning Zap?

I've just been replacing Ubuntu 14 with Linux Mint 17 on an old (and slow!) laptop- about half a gig of updates etc to download which went as sweet as you like.
Bill
BQMs-  IPv4  IPv6

zappaDPJ

Quote from: Bill on Apr 20, 2015, 14:52:20
My feeling at the moment is not to touch anything for a few days... if it seems to be working, don't try to fix it :P

Probably a wise move :)
zap
--------------------

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

zappaDPJ

There's something really odd going on. Yesterday when I disconnected my router to perform tests using a PPPoE connection into the modem it miraculously fixed all my problems. Today I installed the Billion modem/router supplied by IDNet to test my connection. It's early days but it looks like I'm back to square one. I'm on now on a new IP to see if that was a factor but it doesn't seem so. At some point soon I'm going to try continually rebooting the modem/router to see if I can force a decent connection.




Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\zappaDPJ>ping idnet.com -n 100

Pinging idnet.com [212.69.36.207] with 32 bytes of data:
Reply from 212.69.36.207: bytes=32 time=29ms TTL=62
Reply from 212.69.36.207: bytes=32 time=32ms TTL=62
Reply from 212.69.36.207: bytes=32 time=35ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=25ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=40ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Request timed out.
Reply from 212.69.36.207: bytes=32 time=21ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=33ms TTL=62
Reply from 212.69.36.207: bytes=32 time=21ms TTL=62
Reply from 212.69.36.207: bytes=32 time=23ms TTL=62
Reply from 212.69.36.207: bytes=32 time=37ms TTL=62
Reply from 212.69.36.207: bytes=32 time=23ms TTL=62
Reply from 212.69.36.207: bytes=32 time=21ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=40ms TTL=62
Reply from 212.69.36.207: bytes=32 time=22ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=22ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=22ms TTL=62
Reply from 212.69.36.207: bytes=32 time=20ms TTL=62
Reply from 212.69.36.207: bytes=32 time=20ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=22ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=36ms TTL=62
Reply from 212.69.36.207: bytes=32 time=20ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=20ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=23ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=20ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=30ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=20ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=20ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=21ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=18ms TTL=62
Reply from 212.69.36.207: bytes=32 time=21ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=22ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=34ms TTL=62
Reply from 212.69.36.207: bytes=32 time=34ms TTL=62
Reply from 212.69.36.207: bytes=32 time=24ms TTL=62
Reply from 212.69.36.207: bytes=32 time=22ms TTL=62
Reply from 212.69.36.207: bytes=32 time=30ms TTL=62
Reply from 212.69.36.207: bytes=32 time=22ms TTL=62
Reply from 212.69.36.207: bytes=32 time=28ms TTL=62
Reply from 212.69.36.207: bytes=32 time=22ms TTL=62
Reply from 212.69.36.207: bytes=32 time=25ms TTL=62
Reply from 212.69.36.207: bytes=32 time=45ms TTL=62
Reply from 212.69.36.207: bytes=32 time=24ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=46ms TTL=62
Reply from 212.69.36.207: bytes=32 time=27ms TTL=62
Reply from 212.69.36.207: bytes=32 time=42ms TTL=62
Request timed out.
Request timed out.
Reply from 212.69.36.207: bytes=32 time=31ms TTL=62
Reply from 212.69.36.207: bytes=32 time=19ms TTL=62
Reply from 212.69.36.207: bytes=32 time=33ms TTL=62
Reply from 212.69.36.207: bytes=32 time=43ms TTL=62
Reply from 212.69.36.207: bytes=32 time=31ms TTL=62
Reply from 212.69.36.207: bytes=32 time=50ms TTL=62
Reply from 212.69.36.207: bytes=32 time=26ms TTL=62
Reply from 212.69.36.207: bytes=32 time=22ms TTL=62
Reply from 212.69.36.207: bytes=32 time=23ms TTL=62
Reply from 212.69.36.207: bytes=32 time=62ms TTL=62
Reply from 212.69.36.207: bytes=32 time=20ms TTL=62
Reply from 212.69.36.207: bytes=32 time=22ms TTL=62
Reply from 212.69.36.207: bytes=32 time=26ms TTL=62
Request timed out.
Reply from 212.69.36.207: bytes=32 time=20ms TTL=62
Reply from 212.69.36.207: bytes=32 time=25ms TTL=62
Reply from 212.69.36.207: bytes=32 time=27ms TTL=62
Request timed out.
Reply from 212.69.36.207: bytes=32 time=36ms TTL=62
Reply from 212.69.36.207: bytes=32 time=38ms TTL=62

Ping statistics for 212.69.36.207:
    Packets: Sent = 100, Received = 95, Lost = 5 (5% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 62ms, Average = 24ms

C:\Users\zappaDPJ>
zap
--------------------

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

Bill

#99
Quote from: zappaDPJ on Apr 21, 2015, 15:13:29
There's something really odd going on.

There is indeed- just replied to a "How's it going?" email from Simon D, saying basically "Not brilliant, but better than it has been recently".

I may have spoken too soon :(



My Billion arrived today but I was out shopping- I'll pick it up tomorrow.


edit- so as not to give the wrong impression, that big spike at about noon was me tripping over the modem's power lead :red:
Bill
BQMs-  IPv4  IPv6