Results 1 to 6 of 6
  1. #1
    Join Date
    Mar 2008
    Posts
    75

    Joesdatacenter vs CoreNetworks

    These two companies seem to be the most popular in the budget dedicated markets and I was wondering if anyone had any thoughts on their networks.

    Joes AFAIK is mostly cogent, anyone know what providers corenetworks uses?

  2. #2
    Join Date
    May 2008
    Posts
    858
    I was seeing a lot of he.net and alter.net in tracerts when I used them.

  3. #3
    Join Date
    Mar 2009
    Location
    Here Today - Gone to Maui
    Posts
    6,262
    Some more info on CoreNetworks on robtex.
    ProlimeHost- Dedicated Server Hosting & KVM SSD VPS
    Three Datacenter Locations: Los Angeles, Denver & Singapore
    SuperMicro Hardware | Multiple Bandwidth Providers | 24/7 On Site Engineers

  4. #4
    Join Date
    Mar 2007
    Location
    Buffalo, NY
    Posts
    188
    Quote Originally Posted by tr0gd0r View Post
    These two companies seem to be the most popular in the budget dedicated markets and I was wondering if anyone had any thoughts on their networks.

    Joes AFAIK is mostly cogent, anyone know what providers corenetworks uses?
    I've had a server at CoreNetworks for several years (the bottom of the line, it was $25/m when I bought it, now there's a slightly better one for $30/m). I haven't had any problems. Once and a while there is a drop in connections (I use it for an IRCd server), but nothing major.

    A few weeks ago, I requested an IPKVM (no charge of course ), and it was set up in 6 minutes from me requesting it. I would say that their response times are much better than one would expect.

    But that aside, if you are running something mission critical where a few minutes of downtime (and I have never had downtime longer than a few minutes) would be a major problem, you probably shouldn't be looking for a budget provider.

    Here's some traceroutes if you were wondering about the routing. If you have any other addresses you want me to trace, feel free to ask.

    Code:
    traceroute to google.com (74.125.53.100), 30 hops max, 40 byte packets
     1  64.85.160.1 (64.85.160.1)  0.857 ms  1.104 ms  1.238 ms
     2  ae0-105.cr1.ord1.us.nlayer.net (69.31.111.17)  8.449 ms  8.491 ms  8.535 ms
     3  core1-2-2-0.ord.net.google.com (206.223.119.21)  8.900 ms  8.689 ms  9.139 ms
     4  209.85.250.239 (209.85.250.239)  9.185 ms 216.239.48.154 (216.239.48.154)  9.535 ms 209.85.250.239 (209.85.250.239)  9.654 ms
     5  216.239.43.80 (216.239.43.80)  70.339 ms  68.888 ms 72.14.233.116 (72.14.233.116)  70.867 ms
     6  72.14.239.12 (72.14.239.12)  71.093 ms 209.85.250.126 (209.85.250.126)  66.736 ms 72.14.239.12 (72.14.239.12)  70.099 ms
     7  216.239.48.34 (216.239.48.34)  68.543 ms 209.85.250.146 (209.85.250.146)  72.501 ms 216.239.48.32 (216.239.48.32)  113.853 ms
     8  216.239.48.165 (216.239.48.165)  72.112 ms 64.233.174.129 (64.233.174.129)  71.689 ms  72.133 ms
     9  72.14.232.70 (72.14.232.70)  79.459 ms  79.445 ms 72.14.232.6 (72.14.232.6)  79.481 ms
    10  pw-in-f100.1e100.net (74.125.53.100)  72.180 ms  70.686 ms  72.049 ms
    
     1  64.85.160.1 (64.85.160.1)  0.961 ms  0.960 ms  0.988 ms
     2  ae0-105.cr1.ord1.us.nlayer.net (69.31.111.17)  7.781 ms  8.201 ms  8.243 ms
     3  core1-2-2-0.ord.net.google.com (206.223.119.21)  8.771 ms  8.986 ms  9.179 ms
     4  216.239.48.154 (216.239.48.154)  9.502 ms  9.540 ms  9.584 ms
     5  216.239.46.15 (216.239.46.15)  31.630 ms 209.85.240.225 (209.85.240.225)  10.083 ms 216.239.46.15 (216.239.46.15)  31.710 ms
     6  209.85.251.232 (209.85.251.232)  31.118 ms  29.896 ms  33.988 ms
     7  216.239.43.123 (216.239.43.123)  117.176 ms 209.85.250.55 (209.85.250.55)  111.517 ms 216.239.43.123 (216.239.43.123)  118.150 ms
     8  66.249.95.130 (66.249.95.130)  102.185 ms  105.494 ms 216.239.43.193 (216.239.43.193)  104.145 ms
     9  216.239.43.123 (216.239.43.123)  117.085 ms  116.818 ms  118.380 ms
    10  72.14.239.197 (72.14.239.197)  127.094 ms  127.492 ms 72.14.239.199 (72.14.239.199)  119.149 ms
    11  209.85.255.98 (209.85.255.98)  118.344 ms 209.85.255.110 (209.85.255.110)  129.860 ms 209.85.255.98 (209.85.255.98)  118.501 ms
    12  ew-in-f104.1e100.net (74.125.77.104)  121.460 ms  120.080 ms  120.098 ms
    
     1  64.85.160.1 (64.85.160.1)  1.007 ms  1.004 ms  1.033 ms
     2  ae0-105.cr1.ord1.us.nlayer.net (69.31.111.17)  7.930 ms  8.039 ms  8.077 ms
     3  core1-2-2-0.ord.net.google.com (206.223.119.21)  8.617 ms  8.659 ms  8.717 ms
     4  209.85.250.239 (209.85.250.239)  9.325 ms 216.239.48.154 (216.239.48.154)  8.803 ms 209.85.250.239 (209.85.250.239)  9.482 ms
     5  209.85.242.215 (209.85.242.215)  37.291 ms 72.14.236.26 (72.14.236.26)  36.633 ms 209.85.242.215 (209.85.242.215)  37.060 ms
     6  209.85.254.226 (209.85.254.226)  36.857 ms  36.235 ms  36.849 ms
     7  209.85.254.239 (209.85.254.239)  36.131 ms  36.882 ms  36.245 ms
     8  209.85.240.25 (209.85.240.25)  38.710 ms  38.698 ms  38.731 ms
     9  qy-in-f104.google.com (74.125.91.104)  36.814 ms  36.864 ms  37.663 ms
    
    traceroute to webhostingtalk.com (69.20.37.49), 30 hops max, 40 byte packets
     1  64.85.160.1 (64.85.160.1)  0.930 ms  1.019 ms  1.061 ms
     2  ae0-105.cr1.ord1.us.nlayer.net (69.31.111.17)  8.034 ms  8.084 ms  8.195 ms
     3  mpr1.ord7.us (206.223.119.86)  14.075 ms  14.266 ms  14.505 ms
     4  ge-2-1-0.mpr1.ord2.above.net (64.125.26.249)  24.031 ms  24.163 ms  24.294 ms
     5  ge-2-0-0.mpr1.ord2.us.above.net (64.125.25.105)  15.000 ms  15.313 ms  14.615 ms
     6  so-1-1-0.mpr1.lga5.us.above.net (64.125.27.170)  38.636 ms  38.080 ms  37.795 ms
     7  so-1-2-0.mpr1.dca2.us.above.net (64.125.26.101)  40.283 ms  40.240 ms  40.295 ms
     8  * * xe-0-1-0.er1.dca2.us.above.net (64.125.27.25)  40.491 ms
     9  xe-1-1-0.er1.iad10.above.net (64.125.26.238)  39.912 ms  40.050 ms  40.182 ms
    10  209.249.11.37.available.above.net (209.249.11.37)  43.692 ms  44.233 ms  44.517 ms
    11  vlan903.core3.iad1.rackspace.com (69.20.1.40)  152.415 ms  152.462 ms  152.506 ms
    12  aggr104a.iad1.rackspace.com (69.20.3.19)  49.724 ms  49.811 ms  49.953 ms
    Mots seems to be using nlayer.

  5. #5
    Join Date
    Apr 2009
    Location
    Adelaide, Australia
    Posts
    83
    I have a server at Joe's Datacenter and I think it's great. The uptime is great, the support times are average or better than average and the prices are, obviously, awesome.

    I haven't used Corenetworks so I can't compare the 2 but I'm definitely happy with Joe's.
    AdelaideHost - providing shared and VPS hosting.
    Reliability and professionalism at prices that don't hurt your wallet!

  6. #6
    I have never heard of both of them but I suppose if you do the search for their domain name here you will be able to get some information to review and make decision

Similar Threads

  1. VPS from joesdatacenter
    By concador in forum VPS Hosting
    Replies: 10
    Last Post: 09-27-2009, 02:31 PM
  2. Joesdatacenter.com Outage?
    By PEAK-Bobby in forum Providers and Network Outages and Updates
    Replies: 9
    Last Post: 09-18-2009, 05:56 PM
  3. JoesDatacenter Issues
    By pixeldawn in forum Providers and Network Outages and Updates
    Replies: 4
    Last Post: 09-03-2009, 12:43 PM
  4. corenetworks
    By splicesite in forum Dedicated Server
    Replies: 1
    Last Post: 04-06-2009, 03:08 PM
  5. Corenetworks
    By TheChemist in forum Dedicated Server
    Replies: 7
    Last Post: 06-19-2008, 08:58 AM

Posting Permissions

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