High pings again

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

Previous topic - Next topic

0 Members and 4 Guests are viewing this topic.

Tacitus

Quote from: rireed3 on Aug 07, 2009, 13:50:17
I put support onto this, and Simon told me they have already implemented an XML interface in the manner described by AAISP, and used it to reduce the SFI's BT want so they can charge.   :thumb: :thumb:

Why don't they say this is what they are doing, on their website?  Considering a premium ISP like iDNet needs every bit of publicity they can get, they don't seem very pro-active when opportunities present themselves. 


Rik

I have to agree, Tac.
Rik
--------------------

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

dujas

QuoteI would no longer short-list Zen, Tac, as I've heard they plan to implement 'compulsory' WBC when they launch the product.

QuoteHowever you do have the option of opting out of the migration if you wish however the ADSL 1 based products may eventually be withdrawn.

Posted by David Nelson on their forums, he has the rather long job title of: Forum Admin, Performance and Improvement Analyst, Team Leader for Zen Internet Business Solutions. So a customer of theirs could opt out until Zen (or BT?) switches completely over to WBC.

Rik

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

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

Simon

At least with IDNet, you're given the option to opt in.
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Gary

If they withdraw adsl 1 products what happens to all those who cant get WBC or who have fixed lines due to line length?
Damned, if you do damned if you don't

Rik

IPStream Connect will be in place, which will allow non-equipped exchanges to connect over the new technology.
Rik
--------------------

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

Gary

Quote from: Rik on Aug 08, 2009, 09:02:00
IPStream Connect will be in place, which will allow non-equipped exchanges to connect over the new technology.
Somehow I just do not trust all this, Rik  :(
Damned, if you do damned if you don't

Glenn

Gary, I think you will be in the majority to think BT will cock it up.
Glenn
--------------------

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

Tacitus

Quote from: Glenn on Aug 08, 2009, 12:34:27
Gary, I think you will be in the majority to think BT will cock it up.

Given there is no date for WBC at my exchange and even 21CN isn't scheduled until Q4 2010, I can't see it happening here until at least 2012.  They should have got  it sorted when my turn comes around.   :fingers:

Glenn

Mine too Tac, I have 21CN though
Glenn
--------------------

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

Gary

Quote from: Tacitus on Aug 08, 2009, 13:02:18
Given there is no date for WBC at my exchange and even 21CN isn't scheduled until Q4 2010, I can't see it happening here until at least 2012.  They should have got  it sorted when my turn comes around.   :fingers:
By then I hope some decent ISP has come to my exchange so I can go LLU, since its BT only right now I have zero choice really, our exchange does not have 21CN dates let alone WBC
Damned, if you do damned if you don't

dujas

#437
According to BT's own plans (they suffered a one year setback in roll-out), 55% of the UK population should be connected to a WBC 21CN enabled exchange by the end of March 2010. If your exchange doesn't have a WBC date then supposedly it's classed as a low priority and could take until the end of 2012 before being upgraded.

Gary

Quote from: dujas on Aug 08, 2009, 13:57:14
According to BT's own plans (they suffered a one year setback in roll-out), 55% of the UK population should be connected to a WBC 21CN enabled exchange by the end of March 2010. If your exchange doesn't have a WBC date then supposedly it's classed as a low priority and could take until the end of 2012 before being upgraded.
By then I may not even have a computer, they really are very boring things  ;D
Damned, if you do damned if you don't

karser

Said I would let you know how it went, well BT cocked it up lol, I was without phone or net for 2 days as they just unplugged me from exchange, that said I'm on with Aquiss now & all seems fine, ping graph from monday was with idnet, the last one I could do after bts cock up, tho other is friday my 1st night on with Aquiss properly.

The bottom line - All is well with my ping again, oddly though they put me straight onto 24mb, the router (linksys ag241) seems fine with it though, it is a 24 mb rated adsl 2 router, but not adsl2+, though what difference that makes I'm not sure. Like many others, underwhelmed is the word that best describes 24mb BB, glad I didnt pay for the "upgrade", download speeds no better than 8mb, upload is about twice the speed, pings are no different.

Heres my router stats from the new isp:

DSL Status:       Up           
               DSL Modulation Mode:      ADSL2+         
               DSL Path Mode:      INTERLEAVED         
               Downstream Rate:      20939 Kbps         
               Upstream Rate:      1076 Kbps         
               Downstream Margin:      6 db         
               Upstream Margin:      5 db         
               Downstream Line Attenuation:      11         
               Upstream Line Attenuation:      5         
               Downstream Transmit Power:      0         
               Upstream Transmit Power:      0

When I 1st got it on it was still on fastpath, but interleaving has come on today for some reason, think there must be another training period like when I 1st got adsl.

[attachment deleted by admin]

Rik

There is another training period. I saw interleaving go on in an attempt to correct the errors, then the target margin was lifted to 9db, same as for Max. I've gained 500k some of the time, upstream is slower than SuperMax. Like you, I am not greatly impressed, but at least I haven't had the pain that some have suffered, hopefully to be sorted by Monday evening according to BT.
Rik
--------------------

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

dujas

Is it just me or are pings excessively high this afternoon? Even after resetting the connection.


Rik

Mine are absolutely normal (WBC).
Rik
--------------------

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

Ray

Fine here as well. (Max)
Ray
--------------------

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

Glenn

25ms average here on max
Glenn
--------------------

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

Rik

Quote from: dujas on Aug 17, 2009, 16:31:26
Is it just me or are pings excessively high this afternoon? Even after resetting the connection.

One VP on one central was peaking briefly, 15 minutes ago. If you're still having problems let IDNet know.
Rik
--------------------

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

dujas

It's back to normal now, was most likely what you said.

Rik

Keep an eye on it, if it becomes an issue again, do some extended ping tests, eg use the -n 20 switch, and let support have the results, they can tweak for you.
Rik
--------------------

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

juiceuk

Mine have been very good since they worked the magic.
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=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms 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
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms 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 = 22ms, Maximum = 27ms, Average = 23ms

I'm a happy gamer now.

Simon

That's what we like, the word "happy".  :thumb:
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.