Dead Men Walking

QuoteTracing route to 82-197-65-246.hi-velocity.net [82.197.65.246]
over a maximum of 30 hops:

 1  <1 ms  <1 ms  <1 ms 192.168.0.1
 2  21 ms  20 ms  19 ms rdsl-lond-uk02.nw.mediaways.net [62.55.96.197]
 3  19 ms  19 ms  18 ms rmwc-lond-uk02-gigaet-6-1.nw.mediaways.net[62.55.96.9]
 4  18 ms  19 ms  20 ms rmws-lond-uk02-gigaet-0-3-0-0.nw.mediaways.net [195.71.254.21]
 5  58 ms  19 ms  19 ms rmws-lond-uk01-gigaet-0-0-0-0.nw.mediaways.net [213.20.251.237]
 6  20 ms  20 ms  19 ms linx-thn.hotlinks.co.uk [195.66.224.52]
 7  29 ms  27 ms  25 ms 82.197.95.121
 8  25 ms  23 ms  25 ms 82-197-65-246.hi-velocity.net [82.197.65.246]

Trace complete.

QuoteOriginally posted by TeaLeaf@Dec 27 2004, 01:05 PM
Are you connecting via xdsluk or ispnet.com?

TL.

[post=73114]Quoted post[/post]

[/b]

QuoteOriginally posted by Jamoe@Dec 30 2004, 01:32 PM

EDIT 3:

Ive just found out BT are behind with rolling out xdsluk, it might be later in the new year for me. Ah well.

[post=73398]Quoted post[/post]

[/b]

QuoteTracing route to 82-197-65-246.hi-velocity.net [82.197.65.246]
over a maximum of 30 hops:

 1  <1 ms  <1 ms  <1 ms 192.168.0.1
 2  20 ms  21 ms  20 ms jenna.hi-velocity.net [82.197.70.53]
 3  22 ms  21 ms  25 ms 82-197-65-246.hi-velocity.net [82.197.65.246]

Trace complete.

Pinging 82.197.65.246 with 32 bytes of data:

Reply from 82.197.65.246: bytes=32 time=20ms TTL=125
Reply from 82.197.65.246: bytes=32 time=20ms TTL=125
Reply from 82.197.65.246: bytes=32 time=19ms TTL=125
Reply from 82.197.65.246: bytes=32 time=18ms TTL=125

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

QuoteTraceRoute - Friday, December 31, 2004 11:08:35

Address: 82.197.65.246 - 82.197.65.246
Number of Packets: 1
Packet size: 32
Don't Fragment: No

#1 192.168.1.1: 10 ms
#2 10.125.64.1: 10 ms
#3 gsr01-ed.blueyonder.co.uk (62.31.64.33): 10 ms
#4 194.117.136.138: 20 ms
#5 c4l.xchangepoint.net (217.79.160.68): 80 ms
#6 82-197-65-246.hi-velocity.net (82.197.65.246): 30 ms

Statistics: Out 6, in 6, loss 0%, times (min/avg/max) 10/26/80 ms

QuotePinging 82.197.65.246 with 32 bytes of data:

Reply from 82.197.65.246: bytes=32 time=168ms TTL=118
Reply from 82.197.65.246: bytes=32 time=181ms TTL=118
Reply from 82.197.65.246: bytes=32 time=168ms TTL=118
Reply from 82.197.65.246: bytes=32 time=165ms TTL=118

Ping statistics for 82.197.65.246:
  Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
  Minimum = 165ms, Maximum = 181ms, Average = 170ms

C:\Documents and Settings\James>tracert 82.197.65.246

Tracing route to 82-197-65-246.hi-velocity.net [82.197.65.246]
over a maximum of 30 hops:

 1  <1 ms  <1 ms  <1 ms 192.168.0.1
 2  145 ms  142 ms  155 ms rdsl-lond-uk02.nw.mediaways.net [62.55.96.197]
 3  119 ms  115 ms  122 ms rmwc-lond-uk02-gigaet-6-1.nw.mediaways.net [62.5
5.96.9]
 4  146 ms  157 ms  152 ms rmws-lond-uk02-gigaet-0-3-0-0.nw.mediaways.net [
195.71.254.21]
 5  171 ms  170 ms  168 ms rmws-lond-uk01-gigaet-0-0-0-0.nw.mediaways.net [
213.20.251.237]
 6  181 ms  164 ms  156 ms linx-thn.hotlinks.co.uk [195.66.224.52]
 7  163 ms  170 ms  166 ms 82.197.95.121
 8  168 ms  165 ms  171 ms 82-197-65-246.hi-velocity.net [82.197.65.246]

Trace complete.

QuoteTracing route to 82-197-65-246.hi-velocity.net [82.197.65.246]
over a maximum of 30 hops:

 1  <1 ms  <1 ms  <1 ms 192.168.0.1
 2  128 ms  136 ms  136 ms jenna.hi-velocity.net [82.197.70.53]
 3  132 ms  133 ms  135 ms 82-197-65-246.hi-velocity.net [82.197.65.246]

Trace complete.

C:\Documents and Settings\James>ping 82.197.65.246

Pinging 82.197.65.246 with 32 bytes of data:

Reply from 82.197.65.246: bytes=32 time=94ms TTL=125
Reply from 82.197.65.246: bytes=32 time=70ms TTL=125
Reply from 82.197.65.246: bytes=32 time=64ms TTL=125
Reply from 82.197.65.246: bytes=32 time=113ms TTL=125

Ping statistics for 82.197.65.246:
  Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
  Minimum = 64ms, Maximum = 113ms, Average = 85ms

C:\Documents and Settings\James>tracert 82.197.65.246

Tracing route to 82-197-65-246.hi-velocity.net [82.197.65.246]
over a maximum of 30 hops:

 1  <1 ms  <1 ms  <1 ms 192.168.0.1
 2  115 ms  111 ms  112 ms jenna.hi-velocity.net [82.197.70.53]
 3  120 ms  122 ms  121 ms 82-197-65-246.hi-velocity.net [82.197.65.246]

Trace complete.

QuoteOriginally posted by Jamoe@Jan 3 2005, 11:59 AM
worse then my isdn line :(. Although i believe the issue is with BT and not Hi-V, lets hope its fixed soon..

[post=73704]Quoted post[/post]

[/b]

QuoteOriginally posted by "M_a_r_k_o"
Hi All

We have identified a hardware issue with the Carriers core transit router and related infrastructure and are planning on having the issue fully resolved tomorrow.

I will keep you all apprised of any developments as they happen.

Once again please accept my appologies for any inconvenience.

Regards

Mark

Quote Speed/Ping issues
Posted on Tuesday, January 04 @ 21:36:02 GMT by AndyGreen

news/comments from Hi-Velocity.it We have been working on the current situation for the past 7 days, alongside one of our carriers.

Due to the time of year and that BT have only been running on skeleton staff over the festive period, today was the first decent opportunity to work closely with BT. BT are now heavily involved, and the issue escalated to the highest point.

A fault has been identified between BT and our carrier. This fault is being worked on, and we will have an update at midday tomorrow (Wednesday 5th Jan).

If at this point, we believe a resolution is more than 10 working days away we will commence a systematic migration of all affected users onto a new network at our own expense.

We see this as a last resort and the carrier we are working with at the moment is running at 25% capacity on their BT Central. This, therefore, indicates a high-level networking issue as opposed to a capacity issue.

Hi-Velocity appreciates your patience and under-standing during this time and will, as always endeavour to resolve this issue to a speedy and satisfactory result.

Mark Barber - Technical Director - Hi-Velocity
Anthony Bennett - Sales Director - Hi-Velocity

QuoteOriginally posted by MAD_ness@Jan 4 2005, 06:27 PM
I always seem to get the best pings when I am on ............usually hovering around the 20 - 30  mark !!!!!!!
good old eclipse  8)
wish smite could have hung on for a while before swapping IP's ....coulda saved all this hassle he's havin' !!!!!  :unsure:

[post=73814]Quoted post[/post]

[/b]

QuoteOriginally posted by Hi-Velocity
Speed/Ping issues

UPDATE @ 20:00 - 5th Jan 05

We have been carrying out extensive testing with our carrier today and have discovered a hardware issue. Replacement Hardware has been delivered ready for testing tomorrow AM. Once the testing has been completed, the replacement hardware will be installed. This should alleviate the speed/ping issues. At this time, our carrier will also review some aspects of their network to provide improved performance.

Mark Barber - Hi-Velocity Support Director will be on site at our carriers premises for both the Hardware installation and the network review.

If this still does not fix the problem, then we will start the systematic migration of users. This will then resolve the issues.

More updates when we have them.

QuoteOriginally posted by Benny@Jan 6 2005, 01:53 PM
Please say you aren't paying full whack for that service yet?

[post=73982]Quoted post[/post]

[/b]

QuoteOriginally posted by TeaLeaf@Jan 6 2005, 03:24 PM
There's a choice in a contractual agreement?

I think you'll find that this is covered in their contract (as with every other ISP). You pay the contractual amount and you'll not be able to riggle out of it! £23.99pm for a 1Mbps connection is still pretty good though especially when the people actually do try to help out and get problems resolved - especially in this case as the problem isn't their own but one of their carrier's.

TL.

[post=73988]Quoted post[/post]

[/b]

QuoteOriginally posted by smite@Jan 6 2005, 05:40 PM
Just lose the loss

QuoteOriginally posted by Hi-Velocity
Speed / Ping Issues Update 07/01/2005 20:00

Antho writes "Following another full day on site with our carrier the situation is now as follows.

There are 2 network upgrades / card changes planned, the first of these will take place at 5am tomorrow (Saturday 8th January). This should alleviate issues for certain users.

The second cannot be carried out until 11am Monday 10th Jan due to a needed part not arriving with us until 9am Monday.

This should see user issues resolved.

As a precaution I have also today requested the MAC codes for the 600 or so affected users, I will have these by Wednesday 12th Jan, so should we need to, we can start the migration process.

We appologise for the lack of information today, and that this issue will not be resolved in time to give you all the weekend surfing experience that you crave and deserve. We will update you tomorrow with the result of tomorrow mornings work then again on Monday. Once again we would like to thank you all for your patience and understanding.

Anthony Bennett - Sales Director
Mark Barber - Technical Director"

Quote Speed / Ping Issues Update 10/01/2005 14:50

Antho writes "There will be a series of outages this afternoon (no more that 5 and for no longer than 3 minutes each) As we move all customers over to the new fibre which has now been run. Once this has been completed we will have a clearer picture as to where we are. We regret that this work has to be done during business hours

Anthony Bennett - Sales Director"

QuoteOriginally posted by Hi-Velocity
Speed / Ping Issues Update 10/01/2005 18.20

Antho writes "Our first planned upgrade (the Gig fibre link) to our carrier, has not gone to plan. The fibre was run and is fine, however there was an issue with our Foundry Bigiron 15000 switch communicating with our carriers Cisco switch. This is not something that we have seen happen before and therefore was completely unexpected. We have logged the issue with Foundry and expect their feedback tonight. Depending on the feedback received and the time that we receive it, we may re attempt this upgrade tonight. Failing that it will be tomorrow morning. The second phase of our planned upgrade at our end will go ahead within the next hour and will result in 2 minutes downtime across the entire platform. This however on its own will not resolve the speed / ping issues.

Based on the feedback from Foundry and the upgrade going ahead on our carrier link in the next 24hrs we will then, if necessary start the migration process.

Anthony Bennett - Sales Director

QuoteOriginally posted by Hi-Velocity
Speed / Ping Issues Update 11/01/2005 20.40

Today our carrier taken further steps to resolve this issue. During the upgrades mentioned below, some other issues have been identified. The ETA for complete and final resolution of this problem is Friday 14th January.

Whilst we appreciate that this may not satisfy all customers, we would like to thank you all for bearing with us during this difficult time.

We will update you when we have any more information for you.

Anthony Bennett, Sales Director - Hi-Velocity

QuotePing / Speed Issues Update 12/01/05 19:55

Antho writes "Firstly my appologies for the delay in updating you. For the last two days we have been close to having the full news, however we didn't want to announce anything before we had a solution in place with our carrier.

We can confirm that a fully working solution is due to be in place by this coming Friday. This is a process that Hi-Velocity have been heavily involved with.

We have upgraded numerous parts of our network over the last week with severeal new fibre links going into place, in an attempt to alleviate packet loss/ping/speed issues. Once all this was complete and we had proven that our network was in no way at fault our carrier escalated the problem further within BT. It would appear that their BT Central Pipe capacity was running at maximum (maxing out from about 11am most days). This was particulary unusual as their Central Pipes were running at 1/3rd of the BT recommended number of users.

A New STM4 (622 Mbps BT Central Pipe) is due next month. In the interim Hi-Velocity have been instrumental in negotiating a deal whereby our affected carrier will lease some BT Central Pipe capacity from another of our platform providers. We will be handing this off to our carrier across our fibre network backbone. Traffic will immediately be loadbalanced across this extra BT Central Pipe capacity, giving plenty of headroom whislt we wait for BT to complete installation of the new STM4.

We have had to wait until now to deliver the full verdict and fix as this is a complex commercial and technical solution.

Whilst we did state that we would commence migrations of affected customers it became clear that this process would take longer than the proposed fix, and would therefore have proved worthless. We came to a decision that it was in the best interest of our customers to pursue this resolve.

We appreciate your patience and look forward to Friday as I am sure you all will!

Anthony Bennett - Sales Director
Mark Barber - Technical Director"

QuoteSpeed/Ping Issues Update 14/01/2005

Unfortunately I am the bearer of yet more bad news. It could be worse however it is by no means the news that I wanted to be giving you. The tunnel between the two providers in order to provide the BT Central Capacity is up and running. A test connection over this tunnel has also been established, however as with all things nowadays there is one company that likes to throw a spanner in the works. BT. Contrary to the timescale they had previously given us, they cannot reroute the relevant realm onto the new capacity until Monday at 14:30pm. This is due to the way in which their network updates. Unfortunately this means that there will be no relief on the amount of traffic being sent down this Central until that time. The news is a big blow to us as we had been told that we would have a fix in place by now.
The only encouragement that we can take and give you is that he physical connection between the two companies is up, running and tested. At 14:30 on Monday one realm will be moved to the new capacity.

None of our customers will experience any downtime when this happens.

Once again my sincerest appologies.

Anthony Bennett - Depressed Sales Director

QuoteOriginally posted by Jamoe@Jan 14 2005, 08:02 PM
(My size 10 Vans are awaiting instructions, wheres the nearest BT CEO? ;) )

[post=74893]Quoted post[/post]

[/b]

QuoteTracing route to clarity.jolt.co.uk [195.149.21.11]
over a maximum of 30 hops:

 1  <1 ms  <1 ms  <1 ms  
 2  19 ms  20 ms  22 ms jenna.hi-velocity.net [82.197.70.53]
 3  36 ms  37 ms  31 ms 82-197-65-226.hi-velocity.net [82.197.65.226]
 4  24 ms  23 ms  21 ms 82.197.95.90
 5  21 ms  23 ms  20 ms lon1-10.nildram.net [217.79.160.15]
 6  22 ms  23 ms  20 ms 84.12.225.130
 7  33 ms  21 ms  22 ms jolt-gw.nildram.net [195.149.20.126]
 8  27 ms  26 ms  29 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.

QuoteOriginally posted by TeaLeaf@Jan 17 2005, 03:48 PM
3.45pm - the update should have gone through at 2.30pm today, so here's a tracert to clarity. It seems good and is certianly better than normal for this time of day during the 'crisis' period.

TL.

[post=75092]Quoted post[/post]

[/b]

QuotePinging 82.197.65.246 with 32 bytes of data:

Reply from 82.197.65.246: bytes=32 time=21ms TTL=125
Reply from 82.197.65.246: bytes=32 time=22ms TTL=125
Reply from 82.197.65.246: bytes=32 time=23ms TTL=125
Reply from 82.197.65.246: bytes=32 time=19ms TTL=125

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

Tracing route to 82-197-65-246.hi-velocity.net [82.197.65.246]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 22 ms 24 ms 21 ms jenna.hi-velocity.net [82.197.70.53]
3 26 ms 23 ms 22 ms 82-197-65-246.hi-velocity.net [82.197.65.246]

Trace complete.

Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=21ms TTL=57
Reply from 195.149.21.11: bytes=32 time=22ms TTL=57
Reply from 195.149.21.11: bytes=32 time=20ms TTL=57
Reply from 195.149.21.11: bytes=32 time=24ms TTL=57

Ping statistics for 195.149.21.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 24ms, Average = 21ms

Tracing route to clarity.jolt.co.uk [195.149.21.11]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 22 ms 21 ms 25 ms jenna.hi-velocity.net [82.197.70.53]
3 23 ms 21 ms 27 ms 82-197-65-226.hi-velocity.net [82.197.65.226]
4 22 ms 22 ms 26 ms ge-loop.tengu.rb-mer.c4l.co.uk [82.197.95.90]
5 26 ms 26 ms 24 ms lon1-10.nildram.net [217.79.160.15]
6 23 ms 25 ms 24 ms 84.12.225.130
7 27 ms 24 ms 25 ms jolt-gw.nildram.net [195.149.20.126]
8 23 ms 26 ms 26 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.

Quote 1  <1 ms  <1 ms  <1 ms 192.168.7.1
 2  26 ms  20 ms  312 ms jenna.hi-velocity.net [82.197.70.53]
 3  23 ms  23 ms  23 ms 82-197-65-226.hi-velocity.net [82.197.65.226]
 4  22 ms  24 ms  21 ms ge-loop.tengu.rb-mer.c4l.co.uk [82.197.95.90]
 5  26 ms  23 ms  24 ms lon1-10.nildram.net [217.79.160.15]
 6  24 ms  32 ms  22 ms 84.12.225.130
 7  24 ms  23 ms  26 ms jolt-gw.nildram.net [195.149.20.126]
 8  25 ms  24 ms  25 ms clarity.jolt.co.uk [195.149.21.11]

QuoteYour line speed:

1002.5 Kbps

122.9 K bytes/sec

QuotePing statistics for 82.197.65.246:
  Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
  Minimum = 21ms, Maximum = 26ms, Average = 23ms

QuoteOriginally posted by smite@Jan 21 2005, 09:18 PM
Mine was better last night.

[post=75500]Quoted post[/post]

[/b]

QuoteOriginally posted by whitey@Jan 18 2005, 11:40 AM
I'll be ordering ADSL before the end of next week and had been planning to use Hi-V. I just hope they've got the performance sorted as there still seems to be some issues according to the Hi-V forum :(

[post=75149]Quoted post[/post]

[/b]

QuoteOriginally posted by whitey@Feb 8 2005, 04:53 PM
Get online later cause I want to see what CZ is like with a good connection

[post=76658]Quoted post[/post]

[/b]

QuoteOriginally posted by BlueBall@Feb 8 2005, 04:58 PM
You were enough of a problem on dial up. You'll be a nightmare now :(

;)

[post=76659]Quoted post[/post]

[/b]

Quoteaccess.to.my.anus.is-denied.co.uk