Can you give me some more information regarding 'Hostlink' please? At the mo I have zero knowledge of this :blush:
It's the 21CN equivalent of a central, Q, the pathway ISPs use to move their data. Faster and more flexible than the old centrals, for WBC customers it allows IDNet to offer extra bandwidth at no extra charge. Unfortunately, for those not able to connect via WBC, there are no bandwidth benefits, due to BT's charging policy.
IPStream connect should launch on Thursday and will resolve capacity problems and the network imbalances as people are moved over.
Quote from: Rik on Oct 26, 2009, 18:18:18and will resolve capacity problems and the network imbalances
:zip:
Thanks Rik :thumb: Hopefully the resolution of capacity and network inbalance problems may help me in sunny NE Scotland to a slightly better connection? :fingers:
It should, Q. :)
Hope it sorts mine as well :P Though was told by support that "I have confirmed with BT that this problem is down to congestion within the exchange on the VP you are connected to. The VP has been sent for regrade. This type of regrade within the BT network is normally done within 10 working days.
5 days and counting..... been logging speeds daily, did some pings as well but they were ok so stopped doing them.
IDNet have one last chance as my 2 work connections are really poor at certain times of the day. Let's hope that the new hostlink sorts things once and for all. :fingers:
Quote from: Sebby on Oct 28, 2009, 00:18:31
IDNet have one last chance as my 2 work connections are really poor at certain times of the day. Let's hope that the new hostlink sorts things once and for all. :fingers:
I think many are echoing that feeling Sebby, if this does not work I may have to consider another provider as I get awful slowdowns in the day sometimes :fingers:
Will this reduce congestion as well [tyhe hostlink]? As my pings have shot up since my laptop died. And now I have my new pc up and running I want to get the most out of it. getting around 100ms when 30-50 was the norm. :(
It should reduce any congestion within the IDNet network, but if the problem is a congested exchange, then it will do nothing for that.
Isn't the hostlink supposed to go live today?
I wonder what will happen to my pings, I await with baited breath!
PING www.idnet.net (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=13.031 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=14.793 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=14.250 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=15.301 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=14.608 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=14.064 ms
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=14.808 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=14.069 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=15.726 ms
64 bytes from 212.69.36.10: icmp_seq=9 ttl=59 time=14.160 ms
--- www.idnet.net ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 13.031/14.481/15.726/0.710 ms
Quote from: stevethegas on Oct 29, 2009, 07:57:22
Isn't the hostlink supposed to go live today?
I wonder what will happen to my pings, I await with baited breath!
PING www.idnet.net (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=13.031 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=14.793 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=14.250 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=15.301 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=14.608 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=14.064 ms
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=14.808 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=14.069 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=15.726 ms
64 bytes from 212.69.36.10: icmp_seq=9 ttl=59 time=14.160 ms
--- www.idnet.net ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 13.031/14.481/15.726/0.710 ms
I think it is, saying that my pings have been great since yesterday, :fingers: things seem nippier, or I'm just slower ;D
You are older Gary ;D
Quote from: Gary on Oct 29, 2009, 08:08:45
I think it is, saying that my pings have been great since yesterday, :fingers: things seem nippier, or I'm just slower ;D
Indeed today is the day for the link to go live, but it needs to be tested before support can start transferring people over!
Quote from: Glenn on Oct 29, 2009, 08:10:00
You are older Gary ;D
Don't remind me Glenn ;D
Quote from: Lance on Oct 29, 2009, 08:21:24
Indeed today is the day for the link to go live, but it needs to be tested before support can start transferring people over!
Testing sounds ominous, what's the schedule for getting us non WBC folks over to it?
We don't know an exact date, Gary, but the IPStream Connect link has gone live this morning and is now on test. IDNet won't be switching people, as such, initially, but whenever you login after the service goes live, you will automatically be connected to the hostlink. After a month or so, anyone who's not needed to reconnect will be booted off the system to force the move - this may cause stale sessions, but there's no other way to do it.
Quote from: Rik on Oct 29, 2009, 08:56:51
We don't know an exact date, Gary, but the IPStream Connect link has gone live this morning and is now on test. IDNet won't be switching people, as such, initially, but whenever you login after the service goes live, you will automatically be connected to the hostlink. After a month or so, anyone who's not needed to reconnect will be booted off the system to force the move - this may cause stale sessions, but there's no other way to do it.
I take it a sticky will be put up to say the hostlink is like for so we can reboot our routers and be put onto it?
As soon as IDNet are happy, they'll announce it.
Whats the status of the existing centrals? I am correct in thinking that they will remain until the contract/lease or whatever expires
They will, Steve, but that time will be as short as IDNet can make it.
Quote from: Rik on Oct 29, 2009, 09:23:44
As soon as IDNet are happy, they'll announce it.
That may be a while, I am sure they want it to be right this time with no issues for users.
How right you are, but A&A have had no problems so they expect a speedy 'go live'.
But they had David's help! >:D
:rofl:
Quote from: stevethegas on Oct 29, 2009, 09:38:26
But they had David's help! >:D
:lol:
Quote from: Rik on Oct 29, 2009, 09:41:25
:rofl:
I think he had a hand in their new invoice system by the looks of it ;D
:pmsl:
:rofl2:
:zip: :hehe:
I must say despite my often cynical outlook ,the hostlink connection ( for those of us on good old adsl max) has exceeded my expectations, pings remain low and very stable, the ping to ping variation is minimal. Throughput has remained high for me with a small drop about mid evening.So that praise no doubt will put the dampers on it. :thumb:
so far since it went live my through put has been nice and high the only thing that has changed is my Ping has increased slightly but im still a very happy bunny
Quote from: stevethegas on Nov 19, 2009, 20:55:45
I must say despite my often cynical outlook ,the hostlink connection ( for those of us on good old adsl max) has exceeded my expectations, pings remain low and very stable, the ping to ping variation is minimal. Throughput has remained high for me with a small drop about mid evening.So that praise no doubt will put the dampers on it. :thumb:
:iagree:
IDNet were pretty confident about the hostlink, A&A's testing had shown no issues, unlike those afflicting all early WBC adoptors.
I've just swapped our router at work for a Draytek Vigor 2820VSn, and things are even better now.
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Vigor.router [192.168.1.1]
2 6 ms 6 ms 6 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 7 ms 8 ms 6 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 6 ms 7 ms 7 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 7 ms 7 ms 6 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 7 ms 7 ms 7 ms www.idnet.net [212.69.36.10]
Trace complete.
Now I've moved to SuperMax, I'm experiencing no slowdowns at lunchtime either. :)
So that puts the BT setup in the frame, Seb. :(
It does. It's a shame that one has to pay more for a service that should be standard, but such is life (at least where BT are involved). :)
Email Ian Livingstone, he'll get fed up with us eventually. :evil:
Those pings look pretty good,I managed to improve mine as well by using a Draytek modem or do you think its down to the supermax?
I do, Steve, I saw it shave 4ms off my pings.
My pings dropped to around 10-11ms on SuperMax with the original SpeedTouch 585v6, but have fallen to around 6ms with the Draytek.