Jump to content
Sign in to follow this  
VznPro

Ping times on FIOS ...

Recommended Posts

Im in Murrieta, CA just got it installed...

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:Documents and SettingsGarett Miller>ping www.testmy.net

Pinging www.testmy.net [67.18.179.85] with 32 bytes of data:

Reply from 67.18.179.85: bytes=32 time=41ms TTL=52

Reply from 67.18.179.85: bytes=32 time=44ms TTL=52

Reply from 67.18.179.85: bytes=32 time=40ms TTL=52

Reply from 67.18.179.85: bytes=32 time=43ms TTL=51

Ping statistics for 67.18.179.85:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 40ms, Maximum = 44ms, Average = 42ms

C:Documents and SettingsGarett Miller>

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:Documents and SettingsGarett Miller>ping www.myspace.com

Pinging www.myspace.com [63.208.226.24] with 32 bytes of data:

Reply from 63.208.226.24: bytes=32 time=6ms TTL=248

Reply from 63.208.226.24: bytes=32 time=6ms TTL=248

Reply from 63.208.226.24: bytes=32 time=11ms TTL=248

Reply from 63.208.226.24: bytes=32 time=7ms TTL=248

Ping statistics for 63.208.226.24:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 6ms, Maximum = 11ms, Average = 7ms

C:Documents and SettingsGarett Miller>

Share this post


Link to post
Share on other sites

i'm in ny on sdsl and here is my ping to the sites he pinged but myspace is cross country for me so verizon ping this and see what you get. nyc.speakeasy.net and then we can see if they are really better.  we also need more people to post here to see the difference.    we also should make another thread comparing the 2 with ping times and trace routes to see if there is really an advantage.

C:Documents and SettingsBlunted>ping testmy.net

Pinging testmy.net [67.18.179.85] with 32 bytes of data:

Reply from 67.18.179.85: bytes=32 time=43ms TTL=53

Reply from 67.18.179.85: bytes=32 time=43ms TTL=53

Reply from 67.18.179.85: bytes=32 time=43ms TTL=53

Reply from 67.18.179.85: bytes=32 time=42ms TTL=53

Ping statistics for 67.18.179.85:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 42ms, Maximum = 43ms, Average = 42ms

C:Documents and SettingsBlunted>ping myspace.com

Pinging myspace.com [63.208.226.24] with 32 bytes of data:

Reply from 63.208.226.24: bytes=32 time=76ms TTL=247

Reply from 63.208.226.24: bytes=32 time=72ms TTL=247

Reply from 63.208.226.24: bytes=32 time=72ms TTL=247

Reply from 63.208.226.24: bytes=32 time=71ms TTL=247

Ping statistics for 63.208.226.24:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 71ms, Maximum = 76ms, Average = 72ms

C:Documents and SettingsBlunted>ping nyc.speakeasy.net

Pinging nyc.speakeasy.net [216.254.95.2] with 32 bytes of data:

Reply from 216.254.95.2: bytes=32 time=7ms TTL=57

Reply from 216.254.95.2: bytes=32 time=5ms TTL=57

Reply from 216.254.95.2: bytes=32 time=7ms TTL=57

Reply from 216.254.95.2: bytes=32 time=7ms TTL=57

Ping statistics for 216.254.95.2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 5ms, Maximum = 7ms, Average = 6ms

Share this post


Link to post
Share on other sites

I am in Plano

Pinging www.testmy.net [67.18.179.85] with 32 bytes of data:

Reply from 67.18.179.85: bytes=32 time=7ms TTL=53

Reply from 67.18.179.85: bytes=32 time=7ms TTL=52

Reply from 67.18.179.85: bytes=32 time=7ms TTL=53

Reply from 67.18.179.85: bytes=32 time=7ms TTL=53

Ping statistics for 67.18.179.85:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 7ms, Maximum = 7ms, Average = 7ms

Share this post


Link to post
Share on other sites

Here is my trace from Plano

One thing that I have noticed is if I go to other sites that test speed, my speeds do decrease quite a bit. Not sure why when I get such good readings here.

1    <1 ms    <1 ms    <1 ms  192.168.1.1

2    5 ms    4 ms    4 ms  10.33.8.1

3    4 ms    4 ms    4 ms  P6-2.LCR-01.DLLSTX.verizon-gni.net [130.81.32.17

4    7 ms    7 ms    7 ms  so-6-0-0-0.PEER-RTR1.DFW80.verizon-gni.net [1301.17.173]

5    6 ms    7 ms    7 ms  so-5-1-0-0.gar2.Dallas1.Level3.net [4.78.234.1]

6    6 ms    7 ms    7 ms  ge-1-1-51.car3.Dallas1.Level3.net [4.68.122.6]

7    7 ms    7 ms    7 ms  4.78.220.10

8    6 ms    7 ms    7 ms  vl32.dsr01.dllstx3.theplanet.com [70.85.127.61]

9    6 ms    7 ms    7 ms  dist-vlan41.dsr2-1.dllstx4.theplanet.com [70.85.27.83]

10    8 ms    7 ms    7 ms  gig1-0-1.tp-car9-1.dllstx4.theplanet.com [67.18.16.69]

11    7 ms    7 ms    7 ms  85.67-18-179.reverse.theplanet.com [67.18.179.85

Mark T.

Share this post


Link to post
Share on other sites

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:Documents and SettingsNeil Comp 2>tracert testmy.net

Tracing route to testmy.net [67.18.179.85]

over a maximum of 30 hops:

  1    11 ms    11 ms    14 ms  10.241.180.1

  2    11 ms    11 ms    28 ms  68.86.108.129

  3    15 ms    10 ms    12 ms  68.86.106.125

  4    10 ms    10 ms    10 ms  68.86.106.13

  5    10 ms    14 ms    10 ms  68.86.106.9

  6    11 ms    11 ms    12 ms  12.118.120.89

  7    26 ms    28 ms    27 ms  tbr2-p013901.attga.ip.att.net [12.123.21.142]

  8    27 ms    39 ms    28 ms  tbr1-cl1.dlstx.ip.att.net [12.122.2.89]

  9    26 ms    25 ms    26 ms  12.122.82.37

10    26 ms    27 ms    26 ms  12.119.136.14

11    25 ms    52 ms    30 ms  vl31.dsr01.dllstx3.theplanet.com [70.85.127.29]

12    39 ms    26 ms    28 ms  dist-vlan41.dsr2-1.dllstx4.theplanet.com [70.85.

127.83]

13    27 ms    27 ms    27 ms  gig1-0-1.tp-car9-1.dllstx4.theplanet.com [67.18.

116.69]

14    23 ms    24 ms    24 ms  85.67-18-179.reverse.theplanet.com [67.18.179.85

]

Trace complete.

not to bad

Share this post


Link to post
Share on other sites

ping from nyc to  cali

C:Documents and SettingsBlunted>tracert lax.speakeasy.net

Tracing route to lax.speakeasy.net [64.81.45.2]

over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  r-68-xxx-xxx.xxx.nycmny83.covad.net [68.xxx.xxx.xxx

  2    8 ms    7 ms    9 ms  172.31.255.253

  3    6 ms    6 ms    5 ms  192.168.31.41

  4    6 ms    5 ms    5 ms  ge-5-0-180.ipcolo1.NewYork1.Level3.net [63.209.1

70.233]

  5    6 ms    5 ms    5 ms  ae-1-52.bbr2.NewYork1.Level3.net [4.68.97.33]

  6    73 ms    73 ms    72 ms  as-0-0.bbr1.LosAngeles1.Level3.net [64.159.1.157

]

  7    73 ms    72 ms    72 ms  4.68.102.11

  8    72 ms    72 ms    73 ms  4.78.194.18

  9    73 ms    73 ms    73 ms  dns.lax1.speakeasy.net [64.81.45.2]

Trace complete.

C:Documents and SettingsBlunted>ping lax.speakeasy.net

Pinging lax.speakeasy.net [64.81.45.2] with 32 bytes of data:

Reply from 64.81.45.2: bytes=32 time=72ms TTL=55

Reply from 64.81.45.2: bytes=32 time=73ms TTL=55

Reply from 64.81.45.2: bytes=32 time=71ms TTL=55

Reply from 64.81.45.2: bytes=32 time=72ms TTL=55

Ping statistics for 64.81.45.2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 71ms, Maximum = 73ms, Average = 72ms

Share this post


Link to post
Share on other sites

pinging www.myspace.com

Reply from 63.208.226.25: bytes=32 time=3ms TTL=248

Reply from 63.208.226.25: bytes=32 time=3ms TTL=248

Reply from 63.208.226.25: bytes=32 time=5ms TTL=248

Reply from 63.208.226.25: bytes=32 time=10ms TTL=248

Ping statistics for 63.208.226.25:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 3ms, Maximum = 10ms, Average = 5ms

Share this post


Link to post
Share on other sites

C:Documents and Settingsmordis>tracert myspace.com

Tracing route to myspace.com [63.208.226.24]

over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1

  2    3 ms    3 ms    3 ms  10.35.3.1

  3    3 ms    2 ms    3 ms  P6-3.LCR-01.LSANCA.verizon-gni.net [130.81.32.41

]

  4    44 ms    34 ms    3 ms  so-7-1-0-0.BB-RTR1.LAX01.verizon-gni.net [130.81

.17.145]

  5    4 ms    3 ms    3 ms  ge2-35.fr1.lax.llnw.net [68.142.106.65]

  6    3 ms    3 ms    24 ms  myspace.ge2-18.fr1.lax.llnw.net [69.28.144.186]

  7    3 ms    3 ms    3 ms  63.208.226.24

Trace complete.

C:Documents and Settingsmordis>

C:Documents an

Share this post


Link to post
Share on other sites

Here is my ping times all over the world from Sacramento, CA

USA

ping www.google.com

Pinging www.l.google.com [66.102.7.147] with 32 bytes of data:

Reply from 66.102.7.147: bytes=32 time=4ms TTL=243

Reply from 66.102.7.147: bytes=32 time=4ms TTL=243

Reply from 66.102.7.147: bytes=32 time=4ms TTL=243

Reply from 66.102.7.147: bytes=32 time=4ms TTL=243

Ping statistics for 66.102.7.147:

Share this post


Link to post
Share on other sites

I'm on Fios 30/5, and out in the middle of Long Island, NY(suffolk county)

Here are some various ping times...

[table][tr][td]Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

Pinging www.testmy.net [67.18.179.85] with 32 bytes of data:

Reply from 67.18.179.85: bytes=32 time=46ms TTL=47

Reply from 67.18.179.85: bytes=32 time=46ms TTL=47

Reply from 67.18.179.85: bytes=32 time=46ms TTL=47

Reply from 67.18.179.85: bytes=32 time=46ms TTL=47

Ping statistics for 67.18.179.85:

Share this post


Link to post
Share on other sites

i'm on sdsl in long island also and fios doesnt impress me at all with pings if my sdsl can beat it in some areas. 

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:Documents and SettingsEebobb>ping testmy.net

Pinging testmy.net [67.18.179.85] with 32 bytes of data:

Reply from 67.18.179.85: bytes=32 time=44ms TTL=53

Reply from 67.18.179.85: bytes=32 time=44ms TTL=53

Reply from 67.18.179.85: bytes=32 time=43ms TTL=53

Reply from 67.18.179.85: bytes=32 time=44ms TTL=53

Ping statistics for 67.18.179.85:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 43ms, Maximum = 44ms, Average = 43ms

C:Documents and SettingsEebobb>ping myspace.com

Pinging myspace.com [63.208.226.24] with 32 bytes of data:

Reply from 63.208.226.24: bytes=32 time=73ms TTL=247

Reply from 63.208.226.24: bytes=32 time=72ms TTL=247

Reply from 63.208.226.24: bytes=32 time=72ms TTL=247

Reply from 63.208.226.24: bytes=32 time=72ms TTL=247

Ping statistics for 63.208.226.24:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 72ms, Maximum = 73ms, Average = 72ms

C:Documents and SettingsEebobb>ping nyc.speakeasy.net

Pinging nyc.speakeasy.net [216.254.95.2] with 32 bytes of data:

Reply from 216.254.95.2: bytes=32 time=5ms TTL=57

Reply from 216.254.95.2: bytes=32 time=6ms TTL=57

Reply from 216.254.95.2: bytes=32 time=6ms TTL=57

Reply from 216.254.95.2: bytes=32 time=6ms TTL=57

Ping statistics for 216.254.95.2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 5ms, Maximum = 6ms, Average = 5ms

C:Documents and SettingsEebobb>ping 64.233.161.104

Pinging 64.233.161.104 with 32 bytes of data:

Reply from 64.233.161.104: bytes=32 time=12ms TTL=244

Reply from 64.233.161.104: bytes=32 time=11ms TTL=244

Reply from 64.233.161.104: bytes=32 time=11ms TTL=244

Reply from 64.233.161.104: bytes=32 time=11ms TTL=244

Ping statistics for 64.233.161.104:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 11ms, Maximum = 12ms, Average = 11ms

C:Documents and SettingsEebobb>ping 68.142.226.53

Pinging 68.142.226.53 with 32 bytes of data:

Reply from 68.142.226.53: bytes=32 time=14ms TTL=54

Reply from 68.142.226.53: bytes=32 time=12ms TTL=54

Reply from 68.142.226.53: bytes=32 time=12ms TTL=54

Reply from 68.142.226.53: bytes=32 time=12ms TTL=54

Ping statistics for 68.142.226.53:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 12ms, Maximum = 14ms, Average = 12ms

C:Documents and SettingsEebobb>ping speakeasy.net

Pinging speakeasy.net [69.17.117.156] with 32 bytes of data:

Reply from 69.17.117.156: bytes=32 time=73ms TTL=55

Reply from 69.17.117.156: bytes=32 time=73ms TTL=55

Reply from 69.17.117.156: bytes=32 time=74ms TTL=55

Reply from 69.17.117.156: bytes=32 time=73ms TTL=55

Ping statistics for 69.17.117.156:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 73ms, Maximum = 74ms, Average = 73ms

C:Documents and SettingsEebobb>ping speedguide.net

Pinging speedguide.net [63.217.30.70] with 32 bytes of data:

Reply from 63.217.30.70: bytes=32 time=13ms TTL=54

Reply from 63.217.30.70: bytes=32 time=12ms TTL=54

Reply from 63.217.30.70: bytes=32 time=12ms TTL=54

Reply from 63.217.30.70: bytes=32 time=12ms TTL=54

Ping statistics for 63.217.30.70:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 12ms, Maximum = 13ms, Average = 12ms

C:Documents and SettingsEebobb>ping lax.speakeasy.net

Pinging lax.speakeasy.net [64.81.45.2] with 32 bytes of data:

Reply from 64.81.45.2: bytes=32 time=73ms TTL=55

Reply from 64.81.45.2: bytes=32 time=72ms TTL=55

Reply from 64.81.45.2: bytes=32 time=72ms TTL=55

Reply from 64.81.45.2: bytes=32 time=72ms TTL=55

Ping statistics for 64.81.45.2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 72ms, Maximum = 73ms, Average = 72ms

C:Documents and SettingsEebobb>

Share this post


Link to post
Share on other sites

i'm on sdsl in long island also and fios doesnt impress me at all with pings if my sdsl can beat it in some areas.

the type of connection dosent matter much

for latency the only diff between fiber and dsl/cable is the ping to first hop.

the rest is how good the ISP routing is and where you live.

i ping my gateway with 0 to 1 ms, if i was on dsl it would probl be around 3 to 5ms

that means if i have a latency against a certain site of 80ms, i would get 83 to 85 ms with dsl

ISP routing affects more

VanBuren :)

Share this post


Link to post
Share on other sites

Speakeasy adsl

C:Documents and SettingsEebobb>ping testmy.net

Pinging testmy.net [67.18.179.85] with 32 bytes of data:

Reply from 67.18.179.85: bytes=32 time=47ms TTL=54

Reply from 67.18.179.85: bytes=32 time=47ms TTL=54

Reply from 67.18.179.85: bytes=32 time=47ms TTL=54

Reply from 67.18.179.85: bytes=32 time=48ms TTL=54

Ping statistics for 67.18.179.85:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 47ms, Maximum = 48ms, Average = 47ms

C:Documents and SettingsEebobb>ping myspace.com

Pinging myspace.com [63.208.226.25] with 32 bytes of data:

Reply from 63.208.226.25: bytes=32 time=86ms TTL=250

Reply from 63.208.226.25: bytes=32 time=86ms TTL=250

Reply from 63.208.226.25: bytes=32 time=87ms TTL=250

Reply from 63.208.226.25: bytes=32 time=87ms TTL=250

Ping statistics for 63.208.226.25:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 86ms, Maximum = 87ms, Average = 86ms

C:Documents and SettingsEebobb>ping nyc.speakeasy.net

Pinging nyc.speakeasy.net [216.254.95.2] with 32 bytes of data:

Reply from 216.254.95.2: bytes=32 time=7ms TTL=62

Reply from 216.254.95.2: bytes=32 time=9ms TTL=62

Reply from 216.254.95.2: bytes=32 time=9ms TTL=62

Reply from 216.254.95.2: bytes=32 time=9ms TTL=62

Ping statistics for 216.254.95.2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 7ms, Maximum = 9ms, Average = 8ms

C:Documents and SettingsEebobb>ping 64.233.161.104

Pinging 64.233.161.104 with 32 bytes of data:

Reply from 64.233.161.104: bytes=32 time=14ms TTL=249

Reply from 64.233.161.104: bytes=32 time=14ms TTL=249

Reply from 64.233.161.104: bytes=32 time=14ms TTL=249

Reply from 64.233.161.104: bytes=32 time=14ms TTL=249

Ping statistics for 64.233.161.104:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 14ms, Maximum = 14ms, Average = 14ms

C:Documents and SettingsEebobb>ping 68.142.226.53

Pinging 68.142.226.53 with 32 bytes of data:

Reply from 68.142.226.53: bytes=32 time=16ms TTL=57

Reply from 68.142.226.53: bytes=32 time=18ms TTL=57

Reply from 68.142.226.53: bytes=32 time=16ms TTL=58

Reply from 68.142.226.53: bytes=32 time=16ms TTL=58

Ping statistics for 68.142.226.53:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 16ms, Maximum = 18ms, Average = 16ms

C:Documents and SettingsEebobb>ping speakeasy.net

Pinging speakeasy.net [69.17.117.156] with 32 bytes of data:

Reply from 69.17.117.156: bytes=32 time=76ms TTL=60

Reply from 69.17.117.156: bytes=32 time=77ms TTL=60

Reply from 69.17.117.156: bytes=32 time=77ms TTL=60

Reply from 69.17.117.156: bytes=32 time=78ms TTL=60

Ping statistics for 69.17.117.156:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 76ms, Maximum = 78ms, Average = 77ms

C:Documents and SettingsEebobb>ping speedguide.net

Pinging speedguide.net [63.217.30.70] with 32 bytes of data:

Reply from 63.217.30.70: bytes=32 time=14ms TTL=53

Reply from 63.217.30.70: bytes=32 time=15ms TTL=53

Reply from 63.217.30.70: bytes=32 time=15ms TTL=53

Reply from 63.217.30.70: bytes=32 time=15ms TTL=53

Ping statistics for 63.217.30.70:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 14ms, Maximum = 15ms, Average = 14ms

C:Documents and SettingsEebobb>ping lax.speakeasy.net

Pinging lax.speakeasy.net [64.81.45.2] with 32 bytes of data:

Reply from 64.81.45.2: bytes=32 time=78ms TTL=61

Reply from 64.81.45.2: bytes=32 time=79ms TTL=61

Reply from 64.81.45.2: bytes=32 time=79ms TTL=61

Reply from 64.81.45.2: bytes=32 time=79ms TTL=61

Ping statistics for 64.81.45.2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 78ms, Maximum = 79ms, Average = 78ms

C:Documents and SettingsEebobb>

Share this post


Link to post
Share on other sites

They may not impress you, but being way out on long island(not near the city) it used to take 20ms to sometimes 50ms(when node was crowded), just to get out of nyc from suffolk...Now its 4ms...Thats a HUGE improvement over my Optonline pings....its $6 more a month and all my pings on all the game servers I play on are 1/2 of what they were with cable, sometime lower if its a east coast server....It impresses me, so I guess that what matters..

Share this post


Link to post
Share on other sites

i also have optimum and know the pings are high but  my sdsl is solid as can be though with ping times and consistint speeds to every site i test at.  also i know your line is VERY FAST but i would expect more from fios or better pings than that.  dont get me wrong its a killer connection :D

Share this post


Link to post
Share on other sites

Its the getting to nyc that adds 5ms to my ping..If i was a bit closer to manhatten, it would probably be better to the further sites...But it was OOL or Fios..(we had no dsl options)...And I had tons of problems with OOL....If you turned your cable modem off at night, it would take up to an hour to pull an ip(meaning no internet for an hour), and then when you did get an IP, you would get 2,000/600 when its supposed to be 10,000/1,000...

I'm just happy to be rid of OOL...I really got sick of calling their so called "tech support"(I think they were just monkeys in cages).

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...