Tiscali / TalkTalk User

JohnT · 19-01-2003, 06:00 PM

I noticed that this site seemed a bit slow so i ran a few tests and noticed there were high ping times?

Pinging www.freedom2support.net [64.136.143.150] with 32 bytes of data:

Reply from 64.136.143.150: bytes=32 time=1619ms TTL=231
Reply from 64.136.143.150: bytes=32 time=1598ms TTL=231
Reply from 64.136.143.150: bytes=32 time=1598ms TTL=231
Reply from 64.136.143.150: bytes=32 time=1638ms TTL=231
Reply from 64.136.143.150: bytes=32 time=1638ms TTL=231
Reply from 64.136.143.150: bytes=32 time=1618ms TTL=231
Reply from 64.136.143.150: bytes=32 time=1638ms TTL=231
Reply from 64.136.143.150: bytes=32 time=1638ms TTL=231
Reply from 64.136.143.150: bytes=32 time=1618ms TTL=231
Reply from 64.136.143.150: bytes=32 time=1638ms TTL=231

Ping statistics for 64.136.143.150:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1598ms, Maximum = 1638ms, Average = 1624ms

Stewart · 19-01-2003, 06:13 PM

Pinging www.freedom2support.net [64.136.143.150] with 32 bytes of data:

Reply from 64.136.143.150: bytes=32 time=261ms TTL=238
Reply from 64.136.143.150: bytes=32 time=275ms TTL=238
Reply from 64.136.143.150: bytes=32 time=253ms TTL=238
Reply from 64.136.143.150: bytes=32 time=243ms TTL=238

Is fine here, thats quite good pings to be honest considering I'm on dialup, are you still having this problem, and is anyone else?

JohnT · 19-01-2003, 07:08 PM

Yep although i think it maybe something specfic to my connection though as (risking a flame by Justin) a traceroute is fine until 206-72-91-200.wi.skypipeline.com then things go through the roof

Although the fact that my connection goes a a couple of 192.168.* addresses could making things interesting (do a traceroute to devnull.force9.co.uk to see what i mean)

Justin · 19-01-2003, 07:49 PM

Quote:

Tracing route to www.freedom2support.net [64.136.143.150]
over a maximum of 30 hops:

 1   145 ms   139 ms   139 ms  172.26.139.149
 2   131 ms   150 ms   129 ms  172.26.230.153
 3   124 ms   139 ms   139 ms  212.67.96.113
 4   148 ms   300 ms   268 ms  212.67.96.83
 5   438 ms   407 ms   397 ms  fe6-1-bdr2.onetel.net.uk [212.67.96.66]
 6   171 ms   135 ms   139 ms  195.8.110.125
 7   135 ms   139 ms   139 ms  so5-0-0-2488M.cr2.LON3.gblx.net [64.214.65.97]
 8   126 ms   128 ms   128 ms  pos2-0-622M.ar2.LON2.gblx.net [208.49.136.58]
 9   137 ms   139 ms   136 ms  ge-0.linx.londen02.uk.bb.verio.net [195.66.224.1
38]
10   156 ms   149 ms   150 ms  p4-0-1-0.r00.amstnl02.nl.bb.verio.net [129.250.2
.51]
11   148 ms   150 ms   139 ms  p4-0-3-0.r01.amstnl02.nl.bb.verio.net [129.250.2
.133]
12   223 ms   225 ms   236 ms  p4-0-1-0.r80.nwrknj01.us.bb.verio.net [129.250.2
.222]
13   236 ms   225 ms   225 ms  p4-0-3-0.r00.nwrknj01.us.bb.verio.net [129.250.5
.39]
14   281 ms   290 ms   289 ms  p16-0-1-1.r20.mlpsca01.us.bb.verio.net [129.250.
5.112]
15   294 ms   300 ms   289 ms  p64-0-0-0.r21.mlpsca01.us.bb.verio.net [129.250.
2.182]
16   289 ms   289 ms   300 ms  p16-1-1-1.r20.lsanca01.us.bb.verio.net [129.250.
5.96]
17   298 ms   300 ms   300 ms  ge-0-2-0.a05.lsanca01.us.ra.verio.net [129.250.2
9.122]
18   287 ms   289 ms   288 ms  p4-0-0-0.a00.lsanca18.us.ra.verio.net [129.250.4
6.114]
19   296 ms   300 ms   300 ms  ge-1-1.a01.lsanca18.us.ra.verio.net [129.250.46.
126]
20   287 ms   289 ms   289 ms  ge-1-1.a00.lsanca16.us.ra.verio.net [129.250.46.
106]
21   297 ms   300 ms   311 ms  ge-3-3.a00.lsanca16.us.ce.verio.net [198.173.172
.158]
22   298 ms   300 ms   300 ms  (null) [209.189.52.218]
23   304 ms   311 ms   300 ms  206-72-91-200.wi.skypipeline.com [206.72.91.200]

24   335 ms   311 ms   311 ms  64.136.128.246
25   306 ms   311 ms   310 ms  64.136.143.150

Trace complete.

Thats on Dialup, and no problems, anyone on F2S getting the same problem? I appologise for the number of Verio Routers, but everything that goes through Verio these days seems to be getting routed through what seems like routers that are sitting next to each other.

Regards,

JohnT · 19-01-2003, 10:05 PM

I am convinced its something to do with this connection look at these two traceroutes one from my current connection and one from a f2s payg connection both are from a isdn hh line/connection (the usb version)

Quote:

Tracing route to www.freedom2support.net [64.136.143.150]

over a maximum of 30 hops:

 1    95 ms    99 ms    99 ms  nac0431987-plusnet-c1-hg2.mdip.bt.net [194.74.71.170]

 2    84 ms    99 ms    99 ms  192.168.254.3

 3    82 ms    99 ms    99 ms  192.168.253.2

 4    99 ms    99 ms    99 ms  vlan601.rhogan1.core.quay.plus.net [212.159.4.5]

 5    97 ms    99 ms    99 ms  bhuna.core.plus.net [212.159.15.253]

 6    86 ms    99 ms    99 ms  atm.core.telehouse.plus.net [212.159.1.66]

 7    84 ms    99 ms    99 ms  jalpiaza.core.telehouse.plus.net [212.159.1.81]

 8    82 ms    99 ms    99 ms  lvl3gw.thn.packetexchange.net [212.187.197.193]

 9    80 ms    99 ms    99 ms  212.113.3.29

10    98 ms    99 ms    99 ms  gige6-2.core2.London1.Level3.net [212.187.131.182]

11    86 ms    99 ms    99 ms  verio-level3.London1.Level3.net [212.187.131.86]

12   104 ms   119 ms   119 ms  p4-0-1-0.r00.amstnl02.nl.bb.verio.net [129.250.2.51]

13   102 ms   119 ms   119 ms  p4-0-3-0.r01.amstnl02.nl.bb.verio.net [129.250.2.133]

14   280 ms   239 ms   199 ms  p4-0-1-0.r80.nwrknj01.us.bb.verio.net [129.250.2.222]

15   196 ms   199 ms   199 ms  p4-0-3-0.r00.nwrknj01.us.bb.verio.net [129.250.5.39]

16   324 ms   279 ms   259 ms  p16-0-1-1.r20.mlpsca01.us.bb.verio.net [129.250.5.112]

17   522 ms   279 ms   279 ms  p64-0-0-0.r21.mlpsca01.us.bb.verio.net [129.250.2.182]

18   240 ms   259 ms   259 ms  p16-1-1-1.r20.lsanca01.us.bb.verio.net [129.250.5.96]

19   258 ms   259 ms   259 ms  ge-0-2-0.a05.lsanca01.us.ra.verio.net [129.250.29.122]

20   243 ms   259 ms   259 ms  p4-0-0-0.a00.lsanca18.us.ra.verio.net [129.250.46.114]

21   242 ms   259 ms   259 ms  ge-1-1.a01.lsanca18.us.ra.verio.net [129.250.46.126]

22   240 ms   259 ms   259 ms  ge-1-1.a00.lsanca16.us.ra.verio.net [129.250.46.106]

23  1957 ms  1939 ms  1959 ms  ge-3-3.a00.lsanca16.us.ce.verio.net [198.173.172.158]

24   258 ms   259 ms   259 ms  209.189.52.218

25  1923 ms  1959 ms  1939 ms  206-72-91-200.wi.skypipeline.com [206.72.91.200]

26  2018 ms  2039 ms  2059 ms  64.136.128.246

27  2039 ms  2019 ms  2019 ms  64.136.143.150

Trace complete.

Quote:

Tracing route to www.freedom2support.net [64.136.143.150]

over a maximum of 30 hops:

 1   123 ms   124 ms   110 ms  nac0894963-freedom2surf-fer-2.mdip.bt.net [213.121.144.89]

 2   110 ms   123 ms   110 ms  194-106-56-89.router.freedom2surf.net [194.106.56.89]

 3   124 ms   123 ms   124 ms  i-194-106-32-59.freedom2surf.net [194.106.32.59]

 4    96 ms   124 ms   110 ms  i-194-106-32-35.freedom2surf.net [194.106.32.35]

 5   110 ms   123 ms   110 ms  213.130.48.145

 6    96 ms   124 ms   123 ms  ge-0-0-0.r00.londen03.uk.bb.verio.net [213.130.47.14]

 7   110 ms   137 ms   151 ms  p4-1-3-0.r00.londen02.uk.bb.verio.net [129.250.2.20]

 8   137 ms   137 ms   152 ms  p4-0-1-0.r00.amstnl02.nl.bb.verio.net [129.250.2.51]

 9   137 ms   137 ms   165 ms  p4-0-3-0.r01.amstnl02.nl.bb.verio.net [129.250.2.133]

10   206 ms   233 ms   247 ms  p4-0-1-0.r80.nwrknj01.us.bb.verio.net [129.250.2.222]

11   206 ms   233 ms   248 ms  p4-0-3-0.r00.nwrknj01.us.bb.verio.net [129.250.5.39]

12   288 ms   302 ms   302 ms  p16-0-1-1.r20.mlpsca01.us.bb.verio.net [129.250.5.112]

13   289 ms   302 ms   288 ms  p64-0-0-0.r21.mlpsca01.us.bb.verio.net [129.250.2.182]

14   288 ms   302 ms   302 ms  p16-1-1-1.r20.lsanca01.us.bb.verio.net [129.250.5.96]

15   289 ms   302 ms   302 ms  ge-0-2-0.a05.lsanca01.us.ra.verio.net [129.250.29.122]

16   288 ms   289 ms   302 ms  p4-0-0-0.a00.lsanca18.us.ra.verio.net [129.250.46.114]

17   274 ms   303 ms   302 ms  ge-1-1.a01.lsanca18.us.ra.verio.net [129.250.46.126]

18   275 ms   302 ms   302 ms  ge-1-1.a00.lsanca16.us.ra.verio.net [129.250.46.106]

19   261 ms   275 ms   274 ms  ge-3-3.a00.lsanca16.us.ce.verio.net [198.173.172.158]

20   288 ms   302 ms   302 ms  209.189.52.218

21   288 ms   303 ms   302 ms  206-72-91-200.wi.skypipeline.com [206.72.91.200]

22   275 ms   302 ms   302 ms  64.136.128.246

23   302 ms   302 ms   275 ms  64.136.143.150

Trace complete.

When i went back to the plusnet one after disconnecting frm f2s the traceroute was the same *shrug* (in fact it stayed that way no matter how many times i reconnected/rebooted etc however seeing as the plusnet one is a 1:1 connection that could be expected)

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Old F2s site	Terminator_007	General Chit-Chat	4	07-02-2004 09:16 PM
Watch out, web site quota restrictions!	PaulBM	Webspace & Domain Names	7	12-09-2003 02:00 PM
can't go to certain site	somy	Freedom2Surf Broadband	6	25-06-2003 05:55 PM
Main Freedom2Support Site Offline	Justin	Website Comments, Suggestions & News	2	24-04-2003 08:47 PM
Nice site	Rod Evans	Website Comments, Suggestions & News	1	19-03-2003 06:35 PM

Tiscali / TalkTalk User

Advertisement

TalkTalk User Links

TalkTalkUser Partners

19-01-2003, 06:00 PM	#1
JohnT Tiscali User Member Join Date: Dec 2002 Posts: 18 Thanks: 0 Thanked 0 Times in 0 Posts	I noticed that this site seemed a bit slow so i ran a few tests and noticed there were high ping times? Pinging www.freedom2support.net [64.136.143.150] with 32 bytes of data: Reply from 64.136.143.150: bytes=32 time=1619ms TTL=231 Reply from 64.136.143.150: bytes=32 time=1598ms TTL=231 Reply from 64.136.143.150: bytes=32 time=1598ms TTL=231 Reply from 64.136.143.150: bytes=32 time=1638ms TTL=231 Reply from 64.136.143.150: bytes=32 time=1638ms TTL=231 Reply from 64.136.143.150: bytes=32 time=1618ms TTL=231 Reply from 64.136.143.150: bytes=32 time=1638ms TTL=231 Reply from 64.136.143.150: bytes=32 time=1638ms TTL=231 Reply from 64.136.143.150: bytes=32 time=1618ms TTL=231 Reply from 64.136.143.150: bytes=32 time=1638ms TTL=231 Ping statistics for 64.136.143.150: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1598ms, Maximum = 1638ms, Average = 1624ms

19-01-2003, 06:13 PM	#2
Stewart Tiscali User Member Join Date: May 2002 Posts: 83 Thanks: 0 Thanked 0 Times in 0 Posts	Pinging www.freedom2support.net [64.136.143.150] with 32 bytes of data: Reply from 64.136.143.150: bytes=32 time=261ms TTL=238 Reply from 64.136.143.150: bytes=32 time=275ms TTL=238 Reply from 64.136.143.150: bytes=32 time=253ms TTL=238 Reply from 64.136.143.150: bytes=32 time=243ms TTL=238 Is fine here, thats quite good pings to be honest considering I'm on dialup, are you still having this problem, and is anyone else?

19-01-2003, 07:08 PM	#3
JohnT Tiscali User Member Join Date: Dec 2002 Posts: 18 Thanks: 0 Thanked 0 Times in 0 Posts	Yep although i think it maybe something specfic to my connection though as (risking a flame by Justin) a traceroute is fine until 206-72-91-200.wi.skypipeline.com then things go through the roof Although the fact that my connection goes a a couple of 192.168.* addresses could making things interesting (do a traceroute to devnull.force9.co.uk to see what i mean)

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)