Well I have to confess that I rarely wonder what is wrong with *your* ping (the higher your ping is the better it is for my survival chances I reckon), but here is what is wrong with mine.
If there is anyone out there who can post some salient analysis or comment (other than 'you got a shite ping there TL') then I would greatly appreciate it.
TL. :end:
(http://www.btinternet.com/~p.d.herbert/homer-030709.JPG)
but id love to have your ping TL.
Sheepy, even allowing for your 56k'er nature, if you *really* want that ping then you must either be certifiable or be looking at a different graph :lol:
TL. 8)
the graphs meen nothing to me, but looking at the top bit ur average pings seem to be below 40 on the top fw servers
I'm sure you could see this bit, but you are losing on the r1.telecomplete router.
I had a look at the dsl routers reports to see if anyone else whinged about it, can't see anthing.
You can't do much about your route, you can't influence it. I let you know if I find anything else.
If you can find out who and where they are it could be worth contacting them and seeing if there is a problem. Or at least getting them to look at it, as other than that your ping is pretty good.
Yup, Hop 7 is a heavily loaded router that is not really coping very well. It is probably fine for surfing web pages through but is a "gamer's nightmare".
Unfortunately, it is outwith your control. However, your ISP may be able to speak to them on your behalf or at least point out to them that there seems to be a slight problem :-)
A useful website is internet traffic Report on http://www.internettrafficreport.com/ (http://www.internettrafficreport.com/) which will allow you to see if there is an "internet" problem or whether it is confined to one of the providers you have to route through.
Yep I saw that one!
The bit that is concerning is actually the amount of lag that is picked up early in the route and then this carries forward into later hops. The single big lag (as it did not carry through to the final hop) is less of a worry, it is more the carried forward lag that is shown. So if my understanding of ping and traceroute is sound, you can ignore the top section altogether and focus on the shape of the graphs shown in the individual timelines for each hop. Where there is an iincidence of high latency that is carried forward to the next hop then this results in 'real' lag experienced by the user. Lots of the graph shows carried latency at quite high levels, way too much for ISDN. The massive lag spikes seem to just be the cherry on the cake. Anybody want to take my cherry? 8O
/me notes that I can't really say that, but I already did so there :P
TL. 8)
take it up with your isp tech guys? Send in a report and your trace findings. See if theres anything in the forums for your isp.
If that doesnt help then get telewest cable :P
I ran a trace prog like that once, didnt understand it. It was part of a massive tracert drive that went on in the bygames forums once upon a time. They found the weak links to the gaming servers that some people were having eventually and something actually got done about it :D
Yup, I contributed to that too. it was nice to see TW actually admit they had a prob for once and also fix it permanently
'you got a shite ping there TL'
TL, funny enough I've noticed issues with telecomplete and they seemed to get worse over the weekend ending with my shutting down the crosswired NIC with telecomplete.
For now your traffic should enter via caladan or as5334 or whatever it is.
Hows that?
Hey TeaBag, how is your ping now? I just brough back up the peering with telecomplete..... seems they had a fibre cut..... sounds painful :-)
Fibre cuts are nowhere near as painful as paper cuts. :D
Bugger getting me coat it's way too hot, i'll get my bikini.
Stryker, I have been routing in via caladan over the weekend and still appear to be now - at least until the penultimate hop when I hit netserve-gw.cust.telecomplete.net. I'll let you know how it goes a ltitle later tonight and I'll try to check it via a few other ISPs too. Cheers for the feedback :D
TL. 8)
netserve be my unofficial tec-partner come co-habiter of the rack. That is crosswired!
This was from last night TL, nice ping :-)
(http://www.sutherlandweb.pwp.blueyonder.co.uk/dmw/images/TLping.jpg)
Now that would be really handy if you also had a trace to post. There are about 300 ways onto the crosswired network from just one or two hops away.
Can I have another screen dump with trace pleeeeease?
(http://www.btinternet.com/~p.d.herbert/homer.deadmen.co030716-2.JPG)
QuoteEver wondered what's wrong with your ping?
No
And here, especially for your delectation, is my ping from tonight's brief encounter with CS where I managed to spend the best part of 7 full rounds lagged out for all bar a few seconds of them........ :evil:
I am fit to explode........
TL. :microwave:
(http://www.btinternet.com/~p.d.herbert/homer.deadmen.co.uk030722.JPG)
so what about that conn I sorted for you?
I have used it, but I am also trying to persevere with getting my own 'already paid for' connection sorted with the provider. Whilst I'm very grateful for the clean connection you gave me (it provided some good clean time online), it is not a long-term solution - the last thing I need is to be paying for 300 hours per month ISDN via one ISDN and then run up a bill for another 150 hours via Nildram :( My current ISP is doing a fair amount of upgrades and is in discussion with me about the ping problems.
One thing I would ask Stryker about though is rack co-habitor Telecomplete as they seem to have a few routers that are not just overloaded but almost completely dead - they regularly introduce wopping great big lag spikes into the mix at my end :(
We keep trying.
TL. 8)
all the lag seems to be right there with your provider..... whoever that is that you use to hookup.
QuoteI have used it, but I am also trying to persevere with getting my own 'already paid for' connection sorted with the provider. Whilst I'm very grateful for the clean connection you gave me (it provided some good clean time online), it is not a long-term solution - the last thing I need is to be paying for 300 hours per month ISDN via one ISDN and then run up a bill for another 150 hours via Nildram :( My current ISP is doing a fair amount of upgrades and is in discussion with me about the ping problems.
One thing I would ask Stryker about though is rack co-habitor Telecomplete as they seem to have a few routers that are not just overloaded but almost completely dead - they regularly introduce wopping great big lag spikes into the mix at my end :(
We keep trying.
TL. 8)
I'd Recommend Nildram to almost anyone.. I've been with them since November and have yet to have any issues with my Ping or the quality of service. Nilly Rocks IMO