For enyone on Be* on fast path
10-02-2008, 14:40
|
#1
|
|
Inactive
Join Date: Oct 2007
Posts: 623
|
For enyone on Be* on fast path
just wondering eny gamers out there who are on Be* on the fast path thingy can u post a ping result pls
ping 82.133.85.65 -n 10
|
|
|
10-02-2008, 15:54
|
#2
|
|
Inactive
Join Date: Jan 2004
Posts: 3,898
|
Re: For enyone on Be* on fast path
I'll be joining BE shortly, and hopefully will be able to get put on fastpath.
I'll try and remember to post a ping then if no one else has in the meantime.
But thats over a week away...
|
|
|
10-02-2008, 16:42
|
#3
|
|
Inactive
Join Date: Oct 2007
Posts: 623
|
Re: For enyone on Be* on fast path
K thanks hope you remember
|
|
|
10-02-2008, 16:58
|
#4
|
|
Inactive
Join Date: Jan 2004
Posts: 3,898
|
Re: For enyone on Be* on fast path
Quote:
Originally Posted by Jonathan90
K thanks hope you remember
|
I've posted on the BE forums so maybe one of the people there will do it for you in the meantime.
|
|
|
10-02-2008, 19:17
|
#5
|
|
Inactive
Join Date: Jan 2004
Posts: 3,898
|
Re: For enyone on Be* on fast path
Here's the results.
From: smaugy
Quote:
Reply from 82.133.85.65: bytes=32 time=30ms TTL=54
Reply from 82.133.85.65: bytes=32 time=29ms TTL=54
Reply from 82.133.85.65: bytes=32 time=28ms TTL=54
Reply from 82.133.85.65: bytes=32 time=29ms TTL=54
Reply from 82.133.85.65: bytes=32 time=29ms TTL=54
Reply from 82.133.85.65: bytes=32 time=29ms TTL=54
Reply from 82.133.85.65: bytes=32 time=30ms TTL=54
Reply from 82.133.85.65: bytes=32 time=29ms TTL=54
Reply from 82.133.85.65: bytes=32 time=29ms TTL=54
Reply from 82.133.85.65: bytes=32 time=29ms TTL=54
Ping statistics for 82.133.85.65:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 30ms, Average = 29ms
|
From rich1068 (pinged CF by mistake)
Quote:
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=41ms TTL=46
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=41ms TTL=46
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=40ms TTL=46
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=41ms TTL=46
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=39ms TTL=46
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=39ms TTL=46
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=39ms TTL=46
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=39ms TTL=46
Pinging [87.106.129.133] with 32 bytes ->bytes=32 time=39ms TTL=46
Ping statistics for above hosts:
Packets: Sent = 9, Received = 9, Lost = 0 (0% loss)
Approximate round trip times (RTT) in milli-seconds:
Minimum = 39ms, Maximum = 41ms, Average = 39ms
|
From: matt-s
Quote:
|
I'm NOT on fastpath and I get a ping of 38ms too. Would have thought the fastpath guys should get less?
|
From: Siteguru
Quote:
Pinging 82.133.85.65 with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=40ms TTL=53
Reply from 82.133.85.65: bytes=32 time=36ms TTL=53
Reply from 82.133.85.65: bytes=32 time=36ms TTL=53
Reply from 82.133.85.65: bytes=32 time=38ms TTL=53
Ping statistics for 82.133.85.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 40ms, Average = 37ms
|
Additonal Notes: Via wi-fi
From: ntriantafyllou
Quote:
am on fastpath Annex M - up 2,169 / down 18,835 - Shoreditch Exchange
Pinging 82.133.85.65 with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Reply from 82.133.85.65: bytes=32 time=7ms TTL=51
Ping statistics for 82.133.85.65:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 7ms, Average = 7ms
|
From: gillyallan
Quote:
I sync around 22,500 on fastpath. Live in Central Scotland
Pinging 82.133.85.65 with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=34ms TTL=53
Reply from 82.133.85.65: bytes=32 time=34ms TTL=53
Reply from 82.133.85.65: bytes=32 time=34ms TTL=53
Reply from 82.133.85.65: bytes=32 time=34ms TTL=53
Reply from 82.133.85.65: bytes=32 time=34ms TTL=53
Reply from 82.133.85.65: bytes=32 time=33ms TTL=53
Reply from 82.133.85.65: bytes=32 time=34ms TTL=53
Reply from 82.133.85.65: bytes=32 time=33ms TTL=53
Reply from 82.133.85.65: bytes=32 time=34ms TTL=53
Reply from 82.133.85.65: bytes=32 time=38ms TTL=53
Ping statistics for 82.133.85.65:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 38ms, Average = 34ms
|
Thanks to the people at the BE forums.
|
|
|
10-02-2008, 21:09
|
#6
|
|
Inactive
Join Date: Oct 2007
Posts: 623
|
Re: For enyone on Be* on fast path
thankyou dragon your that appreciated
|
|
|
10-02-2008, 22:14
|
#7
|
|
Inactive
Join Date: Jan 2004
Posts: 3,898
|
Re: For enyone on Be* on fast path
Heres mine from BT broadband.
C:\Users\Dragon>ping 82.133.85.65 -n 10
Pinging 82.133.85.65 with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=61ms TTL=51
Reply from 82.133.85.65: bytes=32 time=23ms TTL=51
Reply from 82.133.85.65: bytes=32 time=18ms TTL=51
Reply from 82.133.85.65: bytes=32 time=298ms TTL=51
Reply from 82.133.85.65: bytes=32 time=16ms TTL=51
Reply from 82.133.85.65: bytes=32 time=130ms TTL=51
Reply from 82.133.85.65: bytes=32 time=94ms TTL=51
Reply from 82.133.85.65: bytes=32 time=17ms TTL=51
Reply from 82.133.85.65: bytes=32 time=18ms TTL=51
Reply from 82.133.85.65: bytes=32 time=57ms TTL=51
Ping statistics for 82.133.85.65:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 298ms, Average = 73ms
C:\Users\Dragon>
Although
C:\Users\Dragon>ping 192.168.1.1 -n 10
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=18ms TTL=255
Reply from 192.168.1.1: bytes=32 time=4ms TTL=255
Reply from 192.168.1.1: bytes=32 time=4ms TTL=255
Reply from 192.168.1.1: bytes=32 time=4ms TTL=255
Reply from 192.168.1.1: bytes=32 time=4ms TTL=255
Reply from 192.168.1.1: bytes=32 time=27ms TTL=255
Reply from 192.168.1.1: bytes=32 time=7ms TTL=255
Reply from 192.168.1.1: bytes=32 time=15ms TTL=255
Reply from 192.168.1.1: bytes=32 time=87ms TTL=255
Reply from 192.168.1.1: bytes=32 time=60ms TTL=255
Ping statistics for 192.168.1.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 87ms, Average = 23ms
C:\Users\Dragon>
Quite a bit of that variation can be attributed to my UPA (powerline) adaptors.
---------- Post added at 23:14 ---------- Previous post was at 22:57 ----------
C:\Users\Dragon>ping 192.168.1.1 -n 10
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=21ms TTL=255
Reply from 192.168.1.1: bytes=32 time=8ms TTL=255
Reply from 192.168.1.1: bytes=32 time=11ms TTL=255
Reply from 192.168.1.1: bytes=32 time=7ms TTL=255
Reply from 192.168.1.1: bytes=32 time=7ms TTL=255
Reply from 192.168.1.1: bytes=32 time=7ms TTL=255
Reply from 192.168.1.1: bytes=32 time=6ms TTL=255
Reply from 192.168.1.1: bytes=32 time=3ms TTL=255
Reply from 192.168.1.1: bytes=32 time=11ms TTL=255
Reply from 192.168.1.1: bytes=32 time=29ms TTL=255
Ping statistics for 192.168.1.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 29ms, Average = 11ms
C:\Users\Dragon>ping 82.133.85.65 -n 10
Pinging 82.133.85.65 with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=17ms TTL=51
Reply from 82.133.85.65: bytes=32 time=17ms TTL=51
Reply from 82.133.85.65: bytes=32 time=24ms TTL=51
Reply from 82.133.85.65: bytes=32 time=18ms TTL=51
Reply from 82.133.85.65: bytes=32 time=19ms TTL=51
Reply from 82.133.85.65: bytes=32 time=18ms TTL=51
Reply from 82.133.85.65: bytes=32 time=16ms TTL=51
Reply from 82.133.85.65: bytes=32 time=15ms TTL=51
Reply from 82.133.85.65: bytes=32 time=15ms TTL=51
Reply from 82.133.85.65: bytes=32 time=15ms TTL=51
Ping statistics for 82.133.85.65:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 24ms, Average = 17ms
C:\Users\Dragon>
That made a slight difference (Swapped the UPA adaptors for a pair of homeplugs I had handy)
|
|
|
20-02-2008, 23:10
|
#8
|
|
Inactive
Join Date: Jan 2004
Posts: 3,898
|
Re: For enyone on Be* on fast path
Be* fastpath
C:\Users\Dragon>ping 82.133.85.65 -n 10
Pinging 82.133.85.65 with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=34ms TTL=53
Reply from 82.133.85.65: bytes=32 time=25ms TTL=53
Reply from 82.133.85.65: bytes=32 time=25ms TTL=53
Reply from 82.133.85.65: bytes=32 time=29ms TTL=53
Reply from 82.133.85.65: bytes=32 time=27ms TTL=53
Reply from 82.133.85.65: bytes=32 time=26ms TTL=53
Reply from 82.133.85.65: bytes=32 time=32ms TTL=53
Reply from 82.133.85.65: bytes=32 time=25ms TTL=53
Reply from 82.133.85.65: bytes=32 time=26ms TTL=53
Reply from 82.133.85.65: bytes=32 time=25ms TTL=53
Ping statistics for 82.133.85.65:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 34ms, Average = 27ms
C:\Users\Dragon>
|
|
|
24-02-2008, 19:55
|
#9
|
|
Inactive
Join Date: Oct 2007
Posts: 623
|
Re: For enyone on Be* on fast path
Thanks Dragon glad u remembered btw were are you
|
|
|
24-02-2008, 20:40
|
#10
|
|
Inactive
Join Date: Jan 2004
Posts: 3,898
|
Re: For enyone on Be* on fast path
basingstoke
|
|
|
25-02-2008, 01:55
|
#11
|
|
Inactive
Join Date: Feb 2008
Posts: 154
|
Re: For enyone on Be* on fast path
i used to be with an entanet reseller titanadsl and i was averging sub 20ms on most sites well impressed.
|
|
|
25-02-2008, 19:40
|
#12
|
|
Inactive
Join Date: Jan 2004
Posts: 3,898
|
Re: For enyone on Be* on fast path
My powerline adaptors can add 5ms + and if i get a bit of noise on the mains it can go waay up.
|
|
|
12-03-2008, 10:50
|
#13
|
|
Inactive
Join Date: Mar 2005
Location: Middlesbrough [TS10]
Age: 40
Services: TT Fibre Large 78mbit
Posts: 967
|
Re: For enyone on Be* on fast path
Are we talking about ADSL or LLU here?
|
|
|
12-03-2008, 13:58
|
#14
|
|
cf.mega poster
Join Date: Sep 2003
Posts: 12,048
|
Re: For enyone on Be* on fast path
llu is adsl
llu is simply unbundled adsl I think it stands for local loop unbundling but not sure. Typically an isp like ukonline or be who are unbundled have much lower traffic costs as they dont have to pay for expensive bt centrals and in addition they use their own dslam equipment so can offer adsl2+ services, in addition they are also not subject to bras automatic profiling so synch speed is the speed you get. Not all llu isps rock of course, tiscali who utilise llu decide to take advantage of the lower costs by cramming customers in and charge them minimal prices so the contention ratio is too high.
|
|
|
13-03-2008, 04:38
|
#15
|
|
Inactive
Join Date: Apr 2007
Location: Emsworth
Services: TV (M), Phone (M), Broadband (XXL)
Posts: 39
|
Re: For enyone on Be* on fast path
From my Be Fastpath connection at work:
Quote:
ping -c 10 82.133.85.65
PING 82.133.85.65 (82.133.85.65) 56(84) bytes of data.
64 bytes from 82.133.85.65: icmp_seq=1 ttl=53 time=25.9 ms
64 bytes from 82.133.85.65: icmp_seq=2 ttl=53 time=24.8 ms
64 bytes from 82.133.85.65: icmp_seq=3 ttl=53 time=24.9 ms
64 bytes from 82.133.85.65: icmp_seq=4 ttl=53 time=25.9 ms
64 bytes from 82.133.85.65: icmp_seq=5 ttl=53 time=25.3 ms
64 bytes from 82.133.85.65: icmp_seq=6 ttl=53 time=25.2 ms
64 bytes from 82.133.85.65: icmp_seq=7 ttl=53 time=25.2 ms
64 bytes from 82.133.85.65: icmp_seq=8 ttl=53 time=25.1 ms
64 bytes from 82.133.85.65: icmp_seq=9 ttl=53 time=25.4 ms
64 bytes from 82.133.85.65: icmp_seq=10 ttl=53 time=25.5 ms
--- 82.133.85.65 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8999ms
rtt min/avg/max/mdev = 24.898/25.366/25.936/0.341 ms
|
HTH
Dave
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT. The time now is 15:16.
|