Digital Region Community Support Forum / ISP Forum & Digital Region Discussion / RiPWiRE Related v / Really High Pings

Post Reply 
Threaded Mode | Linear Mode
Really High Pings
20-02-2012, 09:56 PM
Post: #11
Smokinloads Offline
Junior Member
**
 		Posts: 21
Joined: Feb 2012
RE: Really High Pings
    trace over 250 pings.

some of the hops are iconsistent, but overall, not bad.
Find all posts by this user
Quote this message in a reply
20-02-2012, 10:18 PM
Post: #12
gribz_uk Offline
Member
***
 		Posts: 158
Joined: Feb 2012
RE: Really High Pings
Global Crossing causing the problems, as ever, IMO. Hopefully should avoid them when Ask4 take over. *fingers crossed*
Find all posts by this user
Quote this message in a reply
20-02-2012, 10:19 PM (This post was last modified: 20-02-2012 10:21 PM by mirdragon.)
Post: #13
mirdragon Offline
Super Moderator
******
 		Posts: 1,160
Joined: Jan 2012
RE: Really High Pings
but why is @SpencerUk getting over 60ms for the first hop to Ripwire servers

the first hop from your network back to your isp should always be the fastest
Mirdragon
Forum Moderator
ISP: BT|Modem:HG612 (Modded)|Router: Smoothwall|Sync: 68Mbit/18Mbit
Network: HP Procurve|4 x TP-Link AP
Mobile: Nexus 4+6|Tab 3 8"|Asus VivoTab+Transformer TF101
Media Services: SkyHD|Xbox One|ChromeBox (OpenElec)|Samsung BDH6500|Youview|Netflix
Find all posts by this user
Quote this message in a reply
21-02-2012, 04:39 PM
Post: #14
Jimmy06 Offline
Junior Member
**
 		Posts: 37
Joined: Feb 2012
RE: Really High Pings
And heres mine from an Enta Wholesaler

Code:
Tracing route to bbc-vip011.cwwtf.bbc.co.uk [212.58.246.90]
over a maximum of 30 hops:

  1     1 ms       2    13 ms    12 ms    14 ms  lns19.inx.dsl.enta.net [188.39.1.34]
  3    13 ms    13 ms    14 ms  gi1-9.inx.dist.dsl.enta.net [188.39.1.33]
  4    13 ms    13 ms    13 ms  te2-2.interxion.dsl.enta.net [78.33.141.89]
  5    13 ms    13 ms    13 ms  te2-3.interxion.core.enta.net [87.127.236.209]
  6    14 ms    13 ms    13 ms  te4-2.telehouse-east.core.enta.net [87.127.236.137]
  7    13 ms    13 ms    18 ms  bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]
  8    13 ms    13 ms    14 ms  212.58.238.129
  9    14 ms    17 ms    13 ms  132.185.254.145
10     *        *        *     Request timed out.
11     *        *        *     Request timed out.
12    14 ms    15 ms    14 ms  ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
13    16 ms    17 ms    15 ms  132.185.255.165
14    15 ms    15 ms    14 ms  bbc-vip011.cwwtf.bbc.co.uk [212.58.246.90]

Trace complete.
Find all posts by this user
Quote this message in a reply
22-02-2012, 09:17 PM (This post was last modified: 22-02-2012 09:17 PM by SpencerUk.)
Post: #15
SpencerUk Offline
Administrator
*******
 		Posts: 1,994
Joined: Feb 2012
RE: Really High Pings
@mirdragon

I have a feeling now RiPWiRE doesn't maintain the network, its gone to pot. Quicker customers get over to Ask4 and their new providers the better!

Regards
Spencer Davies
Administrator
[Image: 3552242034.png][Image: 3740977595.png]
Visit this user's website Find all posts by this user
Quote this message in a reply
22-02-2012, 10:21 PM
Post: #16
mirdragon Offline
Super Moderator
******
 		Posts: 1,160
Joined: Jan 2012
RE: Really High Pings
my results

Mirdragon
Forum Moderator
ISP: BT|Modem:HG612 (Modded)|Router: Smoothwall|Sync: 68Mbit/18Mbit
Network: HP Procurve|4 x TP-Link AP
Mobile: Nexus 4+6|Tab 3 8"|Asus VivoTab+Transformer TF101
Media Services: SkyHD|Xbox One|ChromeBox (OpenElec)|Samsung BDH6500|Youview|Netflix
Find all posts by this user
Quote this message in a reply
23-02-2012, 02:52 AM (This post was last modified: 23-02-2012 02:52 AM by ThEGr33k.)
Post: #17
ThEGr33k Offline
Member
***
 		Posts: 216
Joined: Nov 2011
RE: Really High Pings
C:\Users\Computer>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:

1 2 18 ms 18 ms 18 ms 46.31.232.1
3 20 ms 20 ms 19 ms ae0.477.ar3.LBA1.gblx.net [208.48.236.141]
4 20 ms 19 ms 19 ms ge8-0-1000M.cr2.LBA1.gblx.net [67.16.129.86]
5 25 ms 25 ms 25 ms so4-3-2-2488M-scr2.LON3.gblx.net [67.16.162.106]

6 25 ms 25 ms 37 ms ae4-30G.scr4.LON3.gblx.net [67.16.141.142]
7 32 ms 25 ms 25 ms lag2.ar9.LON3.gblx.net [67.17.106.149]
8 26 ms 26 ms 26 ms 4.68.110.157
9 25 ms 25 ms 26 ms ae-14-51.car3.London1.Level3.net [4.69.139.68]
10 26 ms 26 ms 35 ms 195.50.90.162
11 * * * Request timed out.
12 27 ms 26 ms 26 ms ae1.er01.thdow.bbc.co.uk [132.185.254.18]
13 26 ms 26 ms 26 ms 132.185.255.130
14 26 ms 26 ms 26 ms 212.58.241.131

I get 18ms to Ripwire quite consistently. Here is to hoping we see more like mirdragons numbers after the move over! Anyone on Ask4 here who can do a trace for us (not that it matters I suppose since we are all going onto a new system... and come to it are there any details on this new system?
ISP: Ask4 DR Speed: 39.5Mbit /9.90Mbit Ping: 16ms to bbc.co.uk Line Length: ~400m
Find all posts by this user
Quote this message in a reply
23-02-2012, 03:41 AM (This post was last modified: 23-02-2012 03:42 AM by Jimmy06.)
Post: #18
Jimmy06 Offline
Junior Member
**
 		Posts: 37
Joined: Feb 2012
RE: Really High Pings
For better more reliable results your better off using pathping

Example over a wireless connection.

Code:
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
  0  Robert-LAP.myhomedns.co.uk [192.168.2.116]
  1  node1.myhomedns.co.uk [192.168.2.1]
  2  lns19.inx.dsl.enta.net [188.39.1.34]
  3  gi1-9.inx.dist.dsl.enta.net [188.39.1.33]
  4  te2-2.interxion.dsl.enta.net [78.33.141.89]
  5  te2-3.interxion.core.enta.net [87.127.236.209]
  6  te4-2.telehouse-east.core.enta.net [87.127.236.137]
  7  bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]
  8     *        *        *
Computing statistics for 175 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Robert-LAP.myhomedns.co.uk [192.168.2.116]
                                0/ 100 =  0%   |
  1    5ms     0/ 100 =  0%     0/ 100 =  0%  node1.myhomedns.co.uk [192.168.2.1]
                                0/ 100 =  0%   |
  2   16ms     0/ 100 =  0%     0/ 100 =  0%  lns19.inx.dsl.enta.net [188.39.1.34]
                                0/ 100 =  0%   |
  3   16ms     0/ 100 =  0%     0/ 100 =  0%  gi1-9.inx.dist.dsl.enta.net [188.39.1.33]
                                0/ 100 =  0%   |
  4   20ms     0/ 100 =  0%     0/ 100 =  0%  te2-2.interxion.dsl.enta.net [78.33.141.89]
                                0/ 100 =  0%   |
  5   17ms     0/ 100 =  0%     0/ 100 =  0%  te2-3.interxion.core.enta.net [87.127.236.209]
                                0/ 100 =  0%   |
  6   19ms     0/ 100 =  0%     0/ 100 =  0%  te4-2.telehouse-east.core.enta.net [87.127.236.137]
                              100/ 100 =100%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]

Trace complete.
Find all posts by this user
Quote this message in a reply
23-02-2012, 11:22 AM
Post: #19
ThEGr33k Offline
Member
***
 		Posts: 216
Joined: Nov 2011
RE: Really High Pings
(23-02-2012 03:41 AM)Jimmy06 Wrote:  For better more reliable results your better off using pathping

Example over a wireless connection.

Code:
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
  0  Robert-LAP.myhomedns.co.uk [192.168.2.116]
  1  node1.myhomedns.co.uk [192.168.2.1]
  2  lns19.inx.dsl.enta.net [188.39.1.34]
  3  gi1-9.inx.dist.dsl.enta.net [188.39.1.33]
  4  te2-2.interxion.dsl.enta.net [78.33.141.89]
  5  te2-3.interxion.core.enta.net [87.127.236.209]
  6  te4-2.telehouse-east.core.enta.net [87.127.236.137]
  7  bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]
  8     *        *        *
Computing statistics for 175 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Robert-LAP.myhomedns.co.uk [192.168.2.116]
                                0/ 100 =  0%   |
  1    5ms     0/ 100 =  0%     0/ 100 =  0%  node1.myhomedns.co.uk [192.168.2.1]
                                0/ 100 =  0%   |
  2   16ms     0/ 100 =  0%     0/ 100 =  0%  lns19.inx.dsl.enta.net [188.39.1.34]
                                0/ 100 =  0%   |
  3   16ms     0/ 100 =  0%     0/ 100 =  0%  gi1-9.inx.dist.dsl.enta.net [188.39.1.33]
                                0/ 100 =  0%   |
  4   20ms     0/ 100 =  0%     0/ 100 =  0%  te2-2.interxion.dsl.enta.net [78.33.141.89]
                                0/ 100 =  0%   |
  5   17ms     0/ 100 =  0%     0/ 100 =  0%  te2-3.interxion.core.enta.net [87.127.236.209]
                                0/ 100 =  0%   |
  6   19ms     0/ 100 =  0%     0/ 100 =  0%  te4-2.telehouse-east.core.enta.net [87.127.236.137]
                              100/ 100 =100%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]

Trace complete.

Thought about pathping but since tracert is faster and everyone else used that.
ISP: Ask4 DR Speed: 39.5Mbit /9.90Mbit Ping: 16ms to bbc.co.uk Line Length: ~400m
Find all posts by this user
Quote this message in a reply
23-02-2012, 02:12 PM (This post was last modified: 23-02-2012 07:33 PM by Jimmy06.)
Post: #20
Jimmy06 Offline
Junior Member
**
 		Posts: 37
Joined: Feb 2012
RE: Really High Pings
(23-02-2012 11:22 AM)ThEGr33k Wrote:  
(23-02-2012 03:41 AM)Jimmy06 Wrote:  For better more reliable results your better off using pathping

Example over a wireless connection.

Code:
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
  0  Robert-LAP.myhomedns.co.uk [192.168.2.116]
  1  node1.myhomedns.co.uk [192.168.2.1]
  2  lns19.inx.dsl.enta.net [188.39.1.34]
  3  gi1-9.inx.dist.dsl.enta.net [188.39.1.33]
  4  te2-2.interxion.dsl.enta.net [78.33.141.89]
  5  te2-3.interxion.core.enta.net [87.127.236.209]
  6  te4-2.telehouse-east.core.enta.net [87.127.236.137]
  7  bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]
  8     *        *        *
Computing statistics for 175 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Robert-LAP.myhomedns.co.uk [192.168.2.116]
                                0/ 100 =  0%   |
  1    5ms     0/ 100 =  0%     0/ 100 =  0%  node1.myhomedns.co.uk [192.168.2.1]
                                0/ 100 =  0%   |
  2   16ms     0/ 100 =  0%     0/ 100 =  0%  lns19.inx.dsl.enta.net [188.39.1.34]
                                0/ 100 =  0%   |
  3   16ms     0/ 100 =  0%     0/ 100 =  0%  gi1-9.inx.dist.dsl.enta.net [188.39.1.33]
                                0/ 100 =  0%   |
  4   20ms     0/ 100 =  0%     0/ 100 =  0%  te2-2.interxion.dsl.enta.net [78.33.141.89]
                                0/ 100 =  0%   |
  5   17ms     0/ 100 =  0%     0/ 100 =  0%  te2-3.interxion.core.enta.net [87.127.236.209]
                                0/ 100 =  0%   |
  6   19ms     0/ 100 =  0%     0/ 100 =  0%  te4-2.telehouse-east.core.enta.net [87.127.236.137]
                              100/ 100 =100%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]

Trace complete.

Thought about pathping but since tracert is faster and everyone else used that.

Its faster for a reason Smile

EDIT:-

Heres a pathping from my desktop.

Code:
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
  0  Robert-PC.myhomedns.co.uk [192.168.2.149]
  1  node1.myhomedns.co.uk [192.168.2.1]
  2  lns19.inx.dsl.enta.net [188.39.1.34]
  3  gi1-9.inx.dist.dsl.enta.net [188.39.1.33]
  4  te2-2.interxion.dsl.enta.net [78.33.141.89]
  5  te2-3.interxion.core.enta.net [87.127.236.209]
  6  te4-2.telehouse-east.core.enta.net [87.127.236.137]
  7  bbc-gw0-linx.prt0.thdoe.bbc.co.uk [195.66.224.103]
  8     *        *        *
Computing statistics for 175 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Robert-PC.myhomedns.co.uk [192.168
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  node1.myhomedns.co.uk [192.168.2.1
                                0/ 100 =  0%   |
  2   13ms     0/ 100 =  0%     0/ 100 =  0%  lns19.inx.dsl.enta.net [188.39.1.3
                                0/ 100 =  0%   |
  3   14ms     0/ 100 =  0%     0/ 100 =  0%  gi1-9.inx.dist.dsl.enta.net [188.3
                                0/ 100 =  0%   |
  4   13ms     0/ 100 =  0%     0/ 100 =  0%  te2-2.interxion.dsl.enta.net [78.3
                                0/ 100 =  0%   |
  5   14ms     0/ 100 =  0%     0/ 100 =  0%  te2-3.interxion.core.enta.net [87.
                                0/ 100 =  0%   |
  6   14ms     0/ 100 =  0%     0/ 100 =  0%  te4-2.telehouse-east.core.enta.net
                              100/ 100 =100%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  bbc-gw0-linx.prt0.thdoe.bbc.co.uk

Trace complete.

Pathping allows you to get a good idear of the quality of the line. Rather then a glimps of how bad/ how good the line is
Find all posts by this user
Quote this message in a reply
« Next Oldest | Next Newest »
Post Reply 


  • View a Printable Version
  • Send this Thread to a Friend
  • Subscribe to this thread


User(s) browsing this thread: 1 Guest(s)

| Digital Region Community Support Forum | Return to Top | Return to Content | Light (Archive) Mode | RSS Syndication