Results 1 to 26 of 26
  1. #1
    Join Date
    Jun 2002
    Posts
    166

    What can you say about this trace route (site5.com) >>

    Not very good isn't it ?... It's the same since 4 hours (I live in France) :


    Target Name: www.site5.com
    IP: 64.21.152.4
    Date/Time: 10/06/2002 20:00:17

    1 54 ms AAnnecy-101-1-4-1.abo.wanadoo.fr [193.251.17.1]
    2 59 ms [193.253.10.242]
    3 60 ms P2-0.nrlyo102.Lyon.francetelecom.net [193.252.101.114]
    4 60 ms P7-0.ntsta102.Paris.francetelecom.net [193.251.126.98]
    5 59 ms [193.251.126.158]
    6 140 ms P12-0.NYKCR2.New-york.opentransit.net [193.251.241.134]
    7 140 ms P6-0.NYKBB1.New-york.opentransit.net [193.251.241.234]
    8 140 ms iar1-so-3-3-0-0.NewYork.cw.net [208.173.135.49]
    9 140 ms agr1-loopback.NewYork.cw.net [206.24.194.101]
    10 140 ms dcr1-so-7-0-0.NewYork.cw.net [206.24.207.65]
    11 140 ms agr4-so-0-0-0.NewYork.cw.net [206.24.207.62]
    12 160 ms acr2-loopback.Chicago.cw.net [208.172.2.62]
    13 170 ms [208.172.1.130]
    14 160 ms nycmny2wcx3-oc48.wcg.net [64.200.240.38]
    15 169 ms nycmnyhlce1-oc48.wcg.net [64.200.87.110]
    16 170 ms nycmny2lce1-netaccess-atm.wcg.net [64.200.86.150]
    17 170 ms a9-0-0-1165.msfc1.oct.nac.net [209.123.11.10]
    18 169 ms core1-nj-nac.site5.com [207.99.16.214]
    19 * [-] Unreachable - 100% packet loss


    >> What do you think about ?

  2. #2
    Join Date
    Mar 2000
    Posts
    100
    The traceroute looks fairly normal, with a bottleneck in the opentransit.net network. But I wonder why the last hop is timing out for you. Here's what I get:

    3 link74-165.cent.net (199.232.74.165) 18.499 ms 17.622 ms 20.273 ms
    4 res1-br2-g1-0-0.gnaps.net (199.232.131.35) 18.502 ms 18.772 ms 21.120 ms
    5 mae-east-atm.peer.nac.net (198.32.187.103) 34.304 ms 34.317 ms 35.516 ms
    6 a9-0-0-64.msfc1.oct.nac.net (209.123.11.65) 39.806 ms 42.339 ms 41.123 ms
    7 core1-nj-nac.site5.com (207.99.16.214) 43.369 ms 38.220 ms 41.123 ms
    8 64-21-152-4.site5.com (64.21.152.4) 42.750 ms 35.491 ms 38.977 ms

    The return is normal. Looks like your problem is the routers in New York.

  3. #3
    Join Date
    Jun 2002
    Posts
    166
    I've got this kind of traceroute, like the one you have, for good host in France or in Europe (I'm french). Maybe it's that's why this traceroute is not very good ?

  4. #4
    Join Date
    Apr 2001
    Location
    Amsterdam
    Posts
    52
    The traceroute looks fairly normal, with a bottleneck in the opentransit.net network.
    That's about the time it takes to do a transatlantic flight at the speed of light

    JD

  5. #5
    Join Date
    Jun 2002
    Posts
    166
    This light is quite slow...

  6. #6
    Join Date
    Jun 2002
    Location
    New Jersey
    Posts
    19
    We(NAC) would have better connectivity to opentransit if their peering policies weren't so tight.

    The bottleneck is out of the NAC and Site5 networks

    5 59 ms [193.251.126.158]
    6 140 ms P12-0.NYKCR2.New-york.opentransit.net [193.251.241.134]
    7 140 ms P6-0.NYKBB1.New-york.opentransit.net [193.251.241.234]
    8 140 ms iar1-so-3-3-0-0.NewYork.cw.net [208.173.135.49]
    9 140 ms agr1-loopback.NewYork.cw.net [206.24.194.101]
    10 140 ms dcr1-so-7-0-0.NewYork.cw.net [206.24.207.65]
    11 140 ms agr4-so-0-0-0.NewYork.cw.net [206.24.207.62]
    12 160 ms acr2-loopback.Chicago.cw.net [208.172.2.62]

  7. #7
    Join Date
    Jun 2002
    Posts
    166
    New traceroute, always the same unfortunately :

    Target Name: www.site5.com
    IP: 64.21.152.4
    Date/Time: 10/06/2002 23:03:49

    1 51 ms AAnnecy-101-1-4-1.abo.wanadoo.fr [193.251.17.1]
    2 49 ms [193.253.10.242]
    3 49 ms P2-0.nrlyo102.Lyon.francetelecom.net [193.252.101.114]
    4 58 ms P7-0.ntsta102.Paris.francetelecom.net [193.251.126.98]
    5 57 ms [193.251.126.158]
    6 140 ms P12-0.NYKCR2.New-york.opentransit.net [193.251.241.134]
    7 139 ms P6-0.NYKBB1.New-york.opentransit.net [193.251.241.234]
    8 140 ms iar1-so-3-3-0-0.NewYork.cw.net [208.173.135.49]
    9 137 ms agr1-loopback.NewYork.cw.net [206.24.194.101]
    10 140 ms dcr1-so-7-0-0.NewYork.cw.net [206.24.207.65]
    11 140 ms agr4-so-0-0-0.NewYork.cw.net [206.24.207.62]
    12 159 ms acr2-loopback.Chicago.cw.net [208.172.2.62]
    13 159 ms [208.172.1.130]
    14 159 ms nycmny2wcx3-oc48.wcg.net [64.200.240.38]
    15 160 ms nycmnyhlce1-oc48.wcg.net [64.200.87.110]
    16 159 ms nycmny2lce1-netaccess-atm.wcg.net [64.200.86.150]
    17 169 ms a9-0-0-1165.msfc1.oct.nac.net [209.123.11.10]
    18 170 ms core1-nj-nac.site5.com [207.99.16.214]
    19 * [-] Unreachable - 100% packet loss

  8. #8
    Join Date
    Apr 2001
    Location
    Amsterdam
    Posts
    52
    Originally posted by jamesc
    We(NAC) would have better connectivity to opentransit if their peering policies weren't so tight.

    The bottleneck is out of the NAC and Site5 networks

    5 59 ms [193.251.126.158]
    6 140 ms P12-0.NYKCR2.New-york.opentransit.net [193.251.241.134]
    7 140 ms P6-0.NYKBB1.New-york.opentransit.net [193.251.241.234]
    8 140 ms iar1-so-3-3-0-0.NewYork.cw.net [208.173.135.49]
    9 140 ms agr1-loopback.NewYork.cw.net [206.24.194.101]
    10 140 ms dcr1-so-7-0-0.NewYork.cw.net [206.24.207.65]
    11 140 ms agr4-so-0-0-0.NewYork.cw.net [206.24.207.62]
    12 160 ms acr2-loopback.Chicago.cw.net [208.172.2.62]
    Seriously I don't see a problem. 70 to 80 ms is the time it takes to get across the ocean and back. Here's a traceroute from Amsterdam to site5 along a different route.

    1 10 ms 10 ms [xxx.xxx.xxx.xxx]
    2 20 ms 20 ms 32.ge-0-0-0.xr1.pbw.xs4all.net [194.109.5.77]
    3 20 ms 20 ms r16.PO1-1.asd-KQ1.NL.KPNQwest.net [134.222.199.61]
    4 20 ms 20 ms r1-Se1-1-0.0.ledn-KQ1.NL.kpnqwest.net [134.222.96.37]
    5 30 ms 30 ms nlams0605-tc-p6-0.kpnqwest.net [213.174.71.21]
    6 30 ms 21 ms nlams0910-tc-r5-0.kpnqwest.net [213.174.69.179]
    7 30 ms 30 ms gblon0523-tc-p11-0.kpnqwest.net [213.174.70.245]
    8 30 ms 30 ms gblon0303-tc-r6-0.kpnqwest.net [213.174.68.229]
    9 40 ms 40 ms r13-PO1-1.Ldn-KQ4.UK.KPNQwest.net [134.222.249.49]
    10 30 ms 30 ms rt-linx-a.thdo.bbc.co.uk [195.66.224.103]
    11 30 ms 30 ms [195.206.65.134]
    12 110 ms 110 ms nac-gw.thdo.bbc.co.uk [212.58.255.178]
    13 110 ms 110 ms a9-0-0-245.msfc1.oct.nac.net [209.123.11.217]
    14 110 ms 110 ms core1-nj-nac.site5.com [207.99.16.214]
    15 * * [-]

    You'll notice that crossing the ocean and going back (between 11 and 12) still takes 80 ms.

    response time = 2 * distance / (speed of light * efficiency loss) + router response times

  9. #9
    Join Date
    Nov 2001
    Location
    London
    Posts
    4,857
    Do you get 100% packet loss when tracing to pwebtech.com or nac.net?
    Matthew Russell | Namecheap
    Twitter: @mattdrussell

    www.namecheap.com - hosting from a registrar DONE RIGHT!

  10. #10
    That packet loss is inside our router. The server that you are trying to ping has ICMP disabled--which is why all of your packets are being dropped.

    Try pinging/tracerouting meltdown.site5.com of just site5.com.
    Matt Lightner - http://www.mattlightner.com/
    - First initial to the last name at the mail service provided by the world's largest search engine
    - Founder and CEO (Former) Site5.com, sold in 2008
    - Really honestly wants to be a good WHT citizen but can never remember all the correct etiquette. Mods, sorry in advance

  11. #11
    Join Date
    Jun 2002
    Posts
    166
    Hello,

    The traceroute for meltdown.site5.com is ok. Can you explain why I've got problem with www.site5.com please ?


    Target Name: meltdown.site5.com
    IP: 216.118.109.201
    Date/Time: 11/06/2002 09:20:41

    1 48 ms AAnnecy-101-1-4-1.abo.wanadoo.fr [193.251.17.1]
    2 48 ms [193.253.10.242]
    3 51 ms P2-0.nrlyo102.Lyon.francetelecom.net [193.252.101.114]
    4 56 ms P7-0.ntsta102.Paris.francetelecom.net [193.251.126.98]
    5 58 ms [193.251.126.158]
    6 132 ms P12-0.NYKCR2.New-york.opentransit.net [193.251.241.134]
    7 132 ms P6-0.NYKBB1.New-york.opentransit.net [193.251.241.234]
    8 131 ms iar1-so-3-3-0-0.NewYork.cw.net [208.173.135.49]
    9 133 ms agr2-loopback.NewYork.cw.net [206.24.194.102]
    10 131 ms dcr2-so-7-1-0.NewYork.cw.net [206.24.207.197]
    11 133 ms agr4-so-6-0-0.NewYork.cw.net [206.24.207.206]
    12 150 ms acr2-loopback.Chicago.cw.net [208.172.2.62]
    13 159 ms [208.172.1.130]
    14 160 ms nycmny2wcx3-oc48.wcg.net [64.200.240.38]
    15 159 ms nycmnyhlce1-oc48.wcg.net [64.200.87.110]
    16 159 ms nycmny2lce1-netaccess-atm.wcg.net [64.200.86.150]
    17 287 ms a9-0-0-1165.msfc1.oct.nac.net [209.123.11.10]
    18 163 ms core1-nj-nac.site5.com [207.99.16.214]
    19 161 ms [216.118.109.201]


    And for nac.net, I've got this :

    Target Name: www.nac.net
    IP: 207.99.0.101
    Date/Time: 11/06/2002 09:22:17

    1 47 ms AAnnecy-101-1-4-1.abo.wanadoo.fr [193.251.17.1]
    2 50 ms [193.253.10.242]
    3 50 ms P2-0.nrlyo102.Lyon.francetelecom.net [193.252.101.114]
    4 55 ms P7-0.ntsta102.Paris.francetelecom.net [193.251.126.98]
    5 54 ms [193.251.126.158]
    6 132 ms P12-0.NYKCR2.New-york.opentransit.net [193.251.241.134]
    7 130 ms P6-0.NYKBB1.New-york.opentransit.net [193.251.241.234]
    8 132 ms iar1-so-3-3-0-0.NewYork.cw.net [208.173.135.49]
    9 130 ms agr2-loopback.NewYork.cw.net [206.24.194.102]
    10 132 ms dcr2-so-7-1-0.NewYork.cw.net [206.24.207.197]
    11 131 ms agr4-so-6-0-0.NewYork.cw.net [206.24.207.206]
    12 151 ms acr2-loopback.Chicago.cw.net [208.172.2.62]
    13 157 ms [208.172.1.130]
    14 157 ms nycmny2wcx3-oc48.wcg.net [64.200.240.38]
    15 159 ms nycmnyhlce1-oc48.wcg.net [64.200.87.110]
    16 157 ms nycmny2lce1-netaccess-atm.wcg.net [64.200.86.150]
    17 161 ms a9-0-0-1066.msfc1.oct.nac.net [209.123.11.245]
    18 161 ms www.nac.net [207.99.0.101]


    >> What do you thing about it ? Thank you
    Last edited by Bot; 06-11-2002 at 03:44 AM.

  12. #12
    Originally posted by Bot
    Hello,

    The traceroute for meltdown.site5.com is ok. Can you explain why I've got problem with www.site5.com please ?
    Basically, we have ICMP traffic disabled on the server that hosts site5.com, so your traceroute packets are getting dropped. Meltdown is another server on our network, however it does not have ICMP disabled.

    So pinging site5.com will not return any response, even though you can see for yourself that the server is online and fully functional.

    Hope that clears things up.
    Last edited by Matt Lightner; 06-11-2002 at 03:47 AM.
    Matt Lightner - http://www.mattlightner.com/
    - First initial to the last name at the mail service provided by the world's largest search engine
    - Founder and CEO (Former) Site5.com, sold in 2008
    - Really honestly wants to be a good WHT citizen but can never remember all the correct etiquette. Mods, sorry in advance

  13. #13
    Join Date
    Jun 2002
    Posts
    166
    Yes thank you, I understand

    I ask you this because I'm searching for a very good host for a commercial site. I've got 3 names on my list : site5, pair and futurequest. I'll make my choice soon

  14. #14
    Join Date
    Jun 2002
    Location
    New Jersey
    Posts
    19
    Well, if its any consideration, look at all the personal attention you got from NAC and Site5 on this. I think you found your choice

  15. #15
    Join Date
    Nov 2001
    Location
    Vancouver
    Posts
    2,416
    Originally posted by Bot I've got 3 names on my list : site5, pair and futurequest. I'll make my choice soon [/B]
    Until recently I had accounts on both Site5 and Pair. I have had one commercial revenue generating site hosted at Site5 for over a year.

    Either are excellent choices. We dropped our service on Pair but in no way is that a reflection of their capabilities, only that they do not offer a service which I requried for one of our web properties.

  16. #16
    Join Date
    Jun 2002
    Posts
    166
    Thanx for your answers. I've got really better traceroute with Pair but I don't know if it's really important ?

  17. #17
    Join Date
    Nov 2001
    Location
    Vancouver
    Posts
    2,416
    You should try using this tool:

    http://www.tracert.com/cgi-bin/trace.pl

    Trace to meltdown.site5.com and to pair.com and see what you get, from different parts of the world.

    For example, from germany to pair / site5

    traceroute to pair.com (66.39.3.7), 30 hops max, 40 byte packets
    1 fe0-0r0.ffm1.de.carpe.net (212.96.130.129) 1.091 ms 0.941 ms 0.869 ms
    2 frankfurt41.de.eqip.net (195.206.67.65) 1.724 ms 1.635 ms 1.638 ms
    3 frankfurt5.de.eqip.net (195.206.64.89) 2.045 ms 2.081 ms 2.645 ms
    4 frankfurt50.de.eqip.net (195.206.65.149) 1.925 ms 2.036 ms 2.121 ms
    5 amstelveen55.nl.eqip.net (195.90.66.157) 10.06 ms 9.972 ms 10.02 ms
    6 amsterdam11.nl.eqip.net (195.90.66.226) 11.649 ms 10.411 ms 10.652 ms
    7 pos4-0-1-155M.br1.AMS2.gblx.net (62.8.32.109) 11.195 ms 10.816 ms 10.848 ms
    8 so3-1-0-622M.cr2.AMS2.gblx.net (62.8.32.61) 11.579 ms 11.438 ms 11.035 ms
    9 pos1-0-622M.cr1.CLE1.gblx.net (206.132.111.110) 101.558 ms 102.418 ms 101.465 ms
    10 so-0-0-0-622M.ar2.CLE1.gblx.net (206.132.111.158) 101.287 ms 102.049 ms 101.431 ms
    11 PairNetworks.t3-1-0-0.ar2.CLE1.gblx.net (64.211.111.110) 107.838 ms 107.719 ms 107.52 ms
    12 www.pair.com (66.39.3.7) 107.694 ms 107.882 ms 107.988 ms


    Site5:

    --------------------------------------------------------------------------------
    traceroute to host / ip
    --------------------------------------------------------------------------------

    traceroute to meltdown.site5.com (216.118.109.201), 30 hops max, 40 byte packets
    1 fe0-0r0.ffm1.de.carpe.net (212.96.130.129) 1.117 ms 0.798 ms 0.769 ms
    2 frankfurt41.de.eqip.net (195.206.67.65) 1.697 ms 1.563 ms 1.574 ms
    3 frankfurt5.de.eqip.net (195.206.64.89) 1.758 ms 1.832 ms 1.762 ms
    4 frankfurt50.de.eqip.net (195.206.65.149) 1.916 ms 1.838 ms 1.691 ms
    5 frankfurt55.de.eqip.net (195.90.66.141) 2.581 ms 2.819 ms 2.294 ms
    6 london55.gb.eqip.net (195.90.66.74) 15.975 ms 15.871 ms 15.767 ms
    7 london50.gb.eqip.net (195.90.66.137) 16.636 ms 16.594 ms 17.441 ms
    8 london2.gb.eqip.net (195.90.64.26) 16.657 ms 17.037 ms 17.025 ms
    9 195.206.65.134 (195.206.65.134) 17.109 ms 17.195 ms 17.432 ms
    10 nac-gw.thdo.bbc.co.uk (212.58.255.178) 91.871 ms 92.931 ms 91.444 ms
    11 a9-0-0-245.msfc1.oct.nac.net (209.123.11.217) 93.066 ms 93.75 ms 95.993 ms
    12 core1-nj-nac.site5.com (207.99.16.214) 95.92 ms 94.462 ms 93.875 ms
    13 216.118.109.201 (216.118.109.201) 94.976 ms 93.927 ms 93.816 ms

    I tried a French source, it was more or less 90-100ms for both.

    Where will your users be from? France? UK? USA? Yes, all of the above? You can check out the response and routes from various locations and make a decision on your own.

    But as I said before, I don't think you can go wrong with either. I have been a client of both and will soon be adding to our Site5 relationship.

  18. #18
    Join Date
    Apr 2001
    Location
    Amsterdam
    Posts
    52
    Personally I like the visual traceroute utility, because it draws the actual route on a world map:

    http://www.visualware.com/visualroute/livedemo.html

    JD

  19. #19
    Join Date
    Jun 2002
    Posts
    166
    Yes, I've download Visualroute and it's really great to SEE the route !

    >> Mwatkins : my users will be in England and France.

  20. #20
    Join Date
    Sep 2001
    Location
    Belgium
    Posts
    84
    Not good on my end:

    Report for www.site5.com [64.21.152.4]

    Analysis: IP packets are being lost past network "Net Access Corporation" at hop 15. There is insufficient cached information to determine the
    next network at hop 16.

    --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    | Hop | %Loss | IP Address | Node Name | Location | Tzone | ms | Graph | Network |
    --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    | 0 | | 213.224.150.114 | D5E09672.kabel.telenet.be | * | | | | Telenet Operaties N.V. |
    | 1 | | 213.224.150.1 | D5E09601.kabel.telenet.be | ?(Belgium) | +01:00 | 21 | x | Telenet Operaties N.V. |
    | 2 | | 10.30.23.57 | - | ... | | 1 | x | (private use) |
    | 3 | | 213.224.253.66 | D5E0FD42.kabel.telenet.be | ?(Belgium) | +01:00 | 8 | x | Telenet Operaties N.V. |
    | 4 | | 213.224.126.2 | IBNOCM02-SRP5-0.telenet-ops.be | ?(Belgium) | +01:00 | 14 | x | Telenet Operaties N.V. |
    | 5 | 100 | | | | | | | |
    | 6 | | 212.3.238.1 | - | ?Brussels, Belgium | +01:00 | 13 | x | Level3 Communications International |
    | 7 | | 212.3.239.34 | ge-7-1-0-12.mp2.Brussels1.Level3.net | Brussels, Belgium | +01:00 | 11 | x | Level3 Communications International |
    | 8 | | 212.187.128.57 | so-3-0-0.mp2.London1.Level3.net | London, UK | * | 8 | x | European MPLS core |
    | 9 | | 212.187.131.149 | unknown.Level3.net | - | | 13 | x | 2nd London1 Gateway infrastructure |
    | 10 | | 212.113.0.113 | pos2-0.metro1-londencyh00.London1.Level3.net | London, UK | * | 19 | x | London Telehouse inter-router WANS |
    | 11 | | 195.66.224.103 | rt-linx-a.thdo.bbc.co.uk | - | | 16 | x | London Internet exchange (LINX) |
    | 12 | | 212.58.239.130 | - | ?(United Kingdom) | * | 26 | x- | BBC Internet Services, EU Infrastructure. |
    | 13 | | 212.58.255.178 | nac-gw.thdo.bbc.co.uk | - | | 114 | x------- | BBC Internet Services, US Infrastructure. |
    | 14 | | 209.123.11.217 | a9-0-0-245.msfc1.oct.nac.net | - | | 101 | x- | Net Access Corporation |
    | 15 | | 207.99.16.214 | core1-nj-nac.site5.com | ?Parsippany, NJ 07054 | | 104 | x | Net Access Corporation |
    | ... | | | | | | | | |
    | ? | | 64.21.152.4 | www.site5.com | ?Parsippany, NJ 07054 | | | | Net Access Corporation |
    --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    Roundtrip time to 207.99.16.214, average = 104ms, min = 96ms, max = 110ms -- 12-jun-02 12:22:18
    http://www.avalancheonline.net

  21. #21
    Join Date
    Jun 2002
    Posts
    166
    Try this adress : meltdown.site5.com

  22. #22
    Join Date
    Apr 2001
    Location
    Amsterdam
    Posts
    52
    Originally posted by Bot
    meltdown.site5.com
    Seems like demanding the gods to name your server meltdown...

    Maybe the next one should named crash.site5.com

  23. #23
    Join Date
    Nov 2001
    Location
    Vancouver
    Posts
    2,416
    Yes try meltdown.site5.com for tracing - as was pointed out earlier on this thread, the site5.com machine has ICMP intentionally disabled.

    Here's a trace from Belgium - only 8 hops...

    traceroute to meltdown.site5.com (216.118.109.201), 32 hops max, 38 byte packets
    1 g4-1-0-3.c7513.science.belnet.net (193.190.199.69) 1.053 ms
    2 g1-1.c12410.science.belnet.net (193.191.254.9) 0.528 ms
    3 g6-0.c12008.brussels.belnet.net (193.190.197.181) 0.345 ms
    4 p1-0.c7206vxr.london.belnet.net (193.191.254.22) 5.689 ms
    5 core1.ltn.nac.net (195.66.224.94) 6.614 ms
    6 a9-0-0-245.msfc1.oct.nac.net (209.123.11.217) 78.553 ms
    7 core1-nj-nac.site5.com (207.99.16.214) 80.072 ms
    8 216.118.109.201 (216.118.109.201) 79.578 ms

    That's better than I get from Vancouver BC. I think I will move!

  24. #24
    Originally posted by janderk
    Seems like demanding the gods to name your server meltdown...

    Maybe the next one should named crash.site5.com
    lol... will add that one to the list of new names.

    Fortunately there are no customers on that server, so it isn't as mission-critical as some of our other systems (i.e alwaysup.site5.com, invincible.site5.com and solidasarock.site5.com).
    Matt Lightner - http://www.mattlightner.com/
    - First initial to the last name at the mail service provided by the world's largest search engine
    - Founder and CEO (Former) Site5.com, sold in 2008
    - Really honestly wants to be a good WHT citizen but can never remember all the correct etiquette. Mods, sorry in advance

  25. #25
    Join Date
    Jun 2002
    Posts
    166
    Matt, can you give us some adress of big sites that Site5 are hosting please ?

  26. #26
    Originally posted by Bot
    Matt, can you give us some adress of big sites that Site5 are hosting please ?
    Not really, because our clients have a right to privacy. We have quite a few customers on this forum--if they would like to give you their URL they are more tham welcome to, but we will not do so on our own without their permission. If you have further questions about our services, your best bet would be to email them to our sales team at [email protected].
    Matt Lightner - http://www.mattlightner.com/
    - First initial to the last name at the mail service provided by the world's largest search engine
    - Founder and CEO (Former) Site5.com, sold in 2008
    - Really honestly wants to be a good WHT citizen but can never remember all the correct etiquette. Mods, sorry in advance

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •