User comments on ISPs
  >> Zen Internet


Register (or login) on our website and you will not see this ad.


Pages in this thread: 1 | 2 | (show all)   Print Thread
Standard User Rhole
(newbie) Thu 24-Apr-14 13:24:25
Print Post

Trace route.


[link to this post]
 
Hi.

Can anyone on a Zen Fibre connection send a ping and then a tracert to the following IP address... 199.91.189.57

Then copy the results to this thread. Particularly from the North of England--but anywhere is fine really. Thinking of joining Zen.

Much apprechiated. Cheers.
Standard User Geordish
(learned) Thu 24-Apr-14 14:37:08
Print Post

Re: Trace route.


[re: Rhole] [link to this post]
 
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. router.asus.com 0.0% 79 3.9 4.0 3.4 8.9 0.8
2. losubs.subs.dsl4.wh-man.zen.net.uk 0.0% 79 12.4 12.0 10.9 15.8 1.0
3. no-dns-yet-62-3-86-13.zen.co.uk 0.0% 79 15.2 16.2 11.0 74.0 12.7
4. ae2-117.man11.ip4.tinet.net 0.0% 79 11.3 16.7 9.5 70.2 13.2
5. xe-7-2-2.lon10.ip4.tinet.net 0.0% 79 18.2 19.1 17.7 25.8 1.3
6. ae8.edge4.London.Level3.net 2.6% 79 18.3 20.3 18.1 79.9 7.4
7. vl-3606-ve-230.csw2.London1.Level3.net 0.0% 79 95.9 96.0 94.5 108.3 2.2
8. ae-56-221.ebr2.London1.Level3.net 0.0% 79 96.7 95.5 94.6 97.7 0.5
9. ae-44-44.ebr1.NewYork1.Level3.net 0.0% 79 116.8 101.9 95.1 116.8 7.1
10. ae-61-61.csw1.NewYork1.Level3.net 0.0% 79 97.5 96.2 95.1 101.0 0.9
11. ae-62-62.ebr2.NewYork1.Level3.net 0.0% 79 97.8 96.1 95.1 99.2 0.8
ae-72-72.ebr2.NewYork1.Level3.net
12. ae-5-5.car1.Montreal2.Level3.net 0.0% 79 136.2 124.9 94.7 291.8 51.9
13. ae-11-11.car2.Montreal2.Level3.net 51.9% 79 128.3 119.6 94.9 297.3 51.4
14. ORMUCO-COMM.car2.Montreal2.Level3.net 0.0% 79 91.1 92.0 90.7 95.6 0.8
15. 192.34.76.10 0.0% 79 142.3 94.2 90.5 142.3 8.4
16. 199.91.189.242 0.0% 79 91.7 92.4 91.5 95.0 0.6
17. 199.91.189.57 0.0% 79 91.9 92.2 90.9 99.1 1.1


92ms latency end to end.
Standard User lexden16
(member) Thu 24-Apr-14 14:49:27
Print Post

Re: Trace route.


[re: Rhole] [link to this post]
 
traceroute to 199.91.189.57 (199.91.189.57), 25 hops max, 40 byte packets
1 *
2 217.118.16.162 (217.118.16.162) 0.289 ms
3 te2-7.ccr01.sxb03.atlas.cogentco.com (149.11.26.13) 0.618 ms
4 te7-6.ccr01.sxb01.atlas.cogentco.com (154.54.74.249) 0.590 ms
5 te0-7-0-9.mpd21.fra03.atlas.cogentco.com (154.54.75.13) 3.907 ms
6 be2263.ccr41.ams03.atlas.cogentco.com (154.54.61.5) 10.943 ms
7 be2182.ccr21.lpl01.atlas.cogentco.com (154.54.77.246) 20.901 ms
8 be2384.ccr21.ymq02.atlas.cogentco.com (154.54.44.137) 91.694 ms
9 38.122.42.34 (38.122.42.34) 90.402 ms
10 192.34.76.10 (192.34.76.10) 90.714 ms
11 199.91.189.242 (199.91.189.242) 90.579 ms
12 199.91.189.57 (199.91.189.57) 90.851 ms


West Midlands


Register (or login) on our website and you will not see this ad.

Standard User mixt
(experienced) Thu 24-Apr-14 15:45:38
Print Post

Re: Trace route.


[re: Rhole] [link to this post]
 
Southeast Kent.

Text
1
23
45
67
89
1011
1213
traceroute to 199.91.189.57 (199.91.189.57), 30 hops max, 60 byte packets
 1  62.3.84.23  7.680 ms  7.598 ms  7.564 ms 2  62.3.84.229  7.534 ms  7.502 ms  7.463 ms
 3  83.231.235.229  7.432 ms  7.404 ms  7.375 ms 4  130.117.14.173  7.338 ms  7.309 ms  7.522 ms
 5  130.117.49.85  7.969 ms  7.372 ms  7.328 ms 6  154.54.73.113  7.841 ms  7.343 ms  7.256 ms
 7  130.117.49.34  14.188 ms  14.101 ms  14.024 ms 8  154.54.44.137  93.914 ms  93.854 ms  95.049 ms
 9  38.122.42.34  87.554 ms  87.464 ms  87.329 ms10  192.34.76.10  94.601 ms  94.533 ms  94.472 ms
11  199.91.189.242  87.940 ms  87.823 ms  88.325 ms12  199.91.189.57  88.217 ms  87.910 ms  87.749 ms


ZeN | 21CN | IPv6 via HE | 60/20Mb FTTC
Previous ISPs: <aaisp.net> | Virgin Media (50Mb/Cable) | Be* Un Limited | ZeN
Is Linux routing your internet connection?
Need to make BIND geo-aware?
Standard User ukwiz
(fountain of knowledge) Fri 25-Apr-14 10:09:08
Print Post

Re: Trace route.


[re: Rhole] [link to this post]
 
From the south coast...

traceroute to 199.91.189.57 (199.91.189.57), 64 hops max
 1   192.168.1.254 (billion) 0.496ms 0.520ms 0.446ms 
 2   62.3.84.23 (losubs.subs.dsl5.th-lon.zen.net.uk) 11.541ms 11.306ms 11.214ms 
 3   62.3.84.225 (ge-2-1-0-123.cr2.th-lon.zen.net.uk) 16.759ms 12.004ms 11.454ms 
 4   62.3.80.41 (ge-2-0-0-0.cr1.th-lon.zen.net.uk) 11.273ms 11.273ms 11.043ms 
 5   77.67.66.225 (xe-8-2-2.lon10.ip4.tinet.net) 11.488ms 12.016ms 11.470ms 
 6   89.149.184.74 (xe-1-3-0.mtl10.ip4.tinet.net) 96.299ms 96.302ms 96.451ms 
 7   216.221.156.110 (ormuco-gw.ip4.tinet.net) 96.760ms 97.680ms 96.791ms 
 8   192.34.76.2 (192.34.76.2) 96.734ms 134.295ms 96.683ms 
 9   199.91.189.234 (199.91.189.234) 97.263ms 97.963ms 97.004ms 
 10   199.91.189.57 (199.91.189.57) 96.893ms 97.301ms 97.192ms 

PING 199.91.189.57 (199.91.189.57) 56(84) bytes of data.
64 bytes from 199.91.189.57: icmp_req=1 ttl=244 time=97.4 ms
64 bytes from 199.91.189.57: icmp_req=2 ttl=244 time=97.2 ms
64 bytes from 199.91.189.57: icmp_req=3 ttl=244 time=97.3 ms
64 bytes from 199.91.189.57: icmp_req=4 ttl=244 time=97.0 ms
64 bytes from 199.91.189.57: icmp_req=5 ttl=244 time=97.0 ms
64 bytes from 199.91.189.57: icmp_req=6 ttl=244 time=97.3 ms
64 bytes from 199.91.189.57: icmp_req=7 ttl=244 time=97.1 ms
64 bytes from 199.91.189.57: icmp_req=8 ttl=244 time=97.0 ms
64 bytes from 199.91.189.57: icmp_req=9 ttl=244 time=97.0 ms
64 bytes from 199.91.189.57: icmp_req=10 ttl=244 time=97.0 ms


David

BT (poor) -> Zen (excellent) -> O2 (started well, went downhill -> IDNet (No complaints - but 100GB cap) -> Zen (unlimited)
Standard User Chrysalis
(legend) Fri 25-Apr-14 11:37:12
Print Post

Re: Trace route.


[re: ukwiz] [link to this post]
 
might be worth stating if on zen backhaul or BTw, because I find it interesting one guy is going straight to cogent with no internal zen hops and another has a bunch of zen internal hops followed by a different transit provider.

Standard User Geordish
(learned) Fri 25-Apr-14 11:51:32
Print Post

Re: Trace route.


[re: Chrysalis] [link to this post]
 
In reply to a post by Chrysalis:
might be worth stating if on zen backhaul or BTw, because I find it interesting one guy is going straight to cogent with no internal zen hops and another has a bunch of zen internal hops followed by a different transit provider.


The person who posted going straight onto Cogent posted a traceroute that originated from plusnet's network. Second hop is 217.118.16.162.

whois 217.118.16.162 | grep descr
descr: intergenia AG
descr: PlusServer AG

Additionally, is looks like there was some connectivity issues in TiNet's network yesterday, as today the route has significantly shortened. Its also around 3ms lower latency.
Text
1
23
45
67
89
10
Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. router.asus.com                   0.0%    16    3.5   4.1   3.5   6.0   0.6 2. losubs.subs.dsl5.wh-man.zen.net.  0.0%    16   12.2  12.3  10.9  15.7   1.3
 3. no-dns-yet-62-3-86-29.zen.co.uk   0.0%    16   11.4  12.8  11.1  31.3   4.9 4. ae2-117.man11.ip4.tinet.net       0.0%    16   11.5  14.1  10.7  36.6   7.5
 5. xe-0-0-0.mtl10.ip4.tinet.net      0.0%    16  144.4  95.1  87.8 144.4  15.6 6. ormuco-gw.ip4.tinet.net           0.0%    16   89.9  89.7  88.7  92.4   1.1
 7. 192.34.76.2                       0.0%    16   90.2  91.6  88.7 123.1   8.4 8. 199.91.189.234                    0.0%    16   89.5  89.9  88.9  94.1   1.2
 9. 199.91.189.57                     0.0%    15   92.6  90.1  89.0  92.6   1.1
Standard User lexden16
(member) Fri 25-Apr-14 11:56:27
Print Post

Re: Trace route.


[re: Geordish] [link to this post]
 
Traceroute from MacOSX/Utility/Terminal. I am on a Zen WMBC connection.
traceroute to 199.91.189.57 (199.91.189.57), 64 hops max, 52 byte packets

1 fritz.box (xxx.xxx.xxx.x) 0.621 ms 0.333 ms 0.338 ms
2 losubs.subs.dsl2.th-lon.zen.net.uk (62.3.84.21) 9.779 ms 9.757 ms 9.792 ms
3 ge-2-1-0-129.cr2.th-lon.zen.net.uk (62.3.84.245) 9.983 ms 10.137 ms 9.742 ms
4 ge-2-0-0-0.cr1.th-lon.zen.net.uk (62.3.80.41) 10.058 ms 10.178 ms 10.010 ms
5 xe-8-2-2.lon10.ip4.tinet.net (77.67.66.225) 10.228 ms 10.191 ms 10.408 ms
6 xe-7-3-0.mtl10.ip4.tinet.net (141.136.106.106) 95.318 ms 94.654 ms 95.177 ms
7 ormuco-gw.ip4.tinet.net (216.221.156.110) 95.154 ms 95.439 ms 95.774 ms
8 192.34.76.2 (192.34.76.2) 95.339 ms 95.530 ms 95.532 ms
Standard User caffn8me
(knowledge is power) Fri 25-Apr-14 15:50:20
Print Post

Re: Trace route.


[re: Rhole] [link to this post]
 
North London, Zen backhaul, line speed 80Mbps down, 20Mbps up, no interleaving

$ traceroute 199.91.189.57

Tracing route to 199.91.189.57 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  router [10.18.76.254] 
  2     5 ms     5 ms     5 ms  losubs.subs.dsl6.th-lon.zen.net.uk [62.3.84.27] 
  3     6 ms     5 ms     5 ms  no-dns-yet-62-3-86-133.zen.co.uk [62.3.86.133] 
  4     6 ms     5 ms     5 ms  ge-2-0-0-0.cr1.th-lon.zen.net.uk [62.3.80.41] 
  5     5 ms     5 ms     6 ms  xe-8-2-2.lon10.ip4.tinet.net [77.67.66.225] 
  6    90 ms    90 ms    90 ms  xe-4-2-0.mtl10.ip4.tinet.net [141.136.107.125] 
  7    90 ms    90 ms    90 ms  ormuco-gw.ip4.tinet.net [216.221.156.110] 
  8    90 ms    91 ms    91 ms  192.34.76.2 
  9    92 ms    91 ms    91 ms  199.91.189.234 
 10    91 ms    90 ms    90 ms  199.91.189.57 

Trace complete.

$ ping 199.91.189.57 

Pinging 199.91.189.57 with 32 bytes of data:
Reply from 199.91.189.57: bytes=32 time=91ms TTL=244
Reply from 199.91.189.57: bytes=32 time=91ms TTL=244
Reply from 199.91.189.57: bytes=32 time=91ms TTL=244
Reply from 199.91.189.57: bytes=32 time=91ms TTL=244

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


Sarah

--
If I can't drink my bowl of coffee three times daily, then in my torment, I will shrivel up like a piece of roast goat

Spiders on coffee - Badass spiders on drugs

Edited by caffn8me (Fri 25-Apr-14 16:01:07)

Standard User Rhole
(newbie) Fri 25-Apr-14 18:11:12
Print Post

Re: Trace route.


[re: Rhole] [link to this post]
 
Thank you all for the replys to this! I am looking for a new provider as my current one is not available for me at a new place. Current ISP uses Sub-loop unbundling. So no it is ISP equipment from the cabinet with no BT kit anywhere.

My current route to the IP address in Canada is this (goes over Cognet):

C:\Windows\system32>tracert 199.91.189.57

Tracing route to 199.91.189.57 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 6 ms 5 ms 188.64.38.1
3 16 ms 15 ms 15 ms 172.24.0.17
4 15 ms 14 ms 15 ms gi0-0-0-1.nr11.b015595-1.lon01.atlas.cogentco.com [149.6.147.57]
5 14 ms 14 ms 14 ms 154.25.2.197
6 15 ms 15 ms 14 ms te0-7-0-5.ccr21.lon01.atlas.cogentco.com [154.54.74.109]
7 14 ms 15 ms 15 ms be2314.ccr21.lon13.atlas.cogentco.com [154.54.72.253]
8 20 ms 20 ms 20 ms be2285.ccr21.lpl01.atlas.cogentco.com [130.117.49.126]
9 92 ms 91 ms 92 ms be2384.ccr21.ymq02.atlas.cogentco.com [154.54.44.137]
10 91 ms 91 ms 91 ms 38.122.42.34
11 91 ms 91 ms 91 ms 10.2.2.1
12 91 ms 91 ms 91 ms 192.34.76.2
13 91 ms 90 ms 91 ms 199.91.189.234
14 90 ms 90 ms 91 ms 199.91.189.57

Trace complete.


It seems that Zens internal network is very capable and the Exchange I am moving to is no congested for BT based backhaul (obviously don't know if it is further down the line). Zen don't have a PoP there, but they have PoP's at the 2 nearest towns. So I assume traffic will only use BT backhaul until it reaches that?

Anyway, the trace routes have been very useful.

I was primarily looking at Sky and Plusnet, however with a friend near me on Plusnet I tested the route and the traffic went over Level3. Level3 seem to introduce extra hops for this destination, even routing in odd ways via Paris then Amsterdam before making it's way to Canada. Sky LLU connections also seem to take this route. Peak time latency is a real issue of these 2 ISPs for that IP address.

I am after a steady and constantly good peak time latency to the IP 199.91.189.57. So, while I cannot guarentee stability of traffic through peering providers, I am looking for the least number of hops. So gives the best 'chance' that latency is stable enough. Also, Cognet at least do seem to have a good route for traffic to this IP address. From the traces it seems Tinet do too.

The trace test that goes via Manchester then on to Level3 is a concern though, but nobody else seems to have that route.

The only other ISP I am considering is TalkTalk Business due to the priority connection. Also, TalkTalk speeds in my area are good from another friends connection. However I would much prefer Zen because of their reputation.
Pages in this thread: 1 | 2 | (show all)   Print Thread

Jump to