Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


new CDN.net - does this make sense?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

new CDN.net - does this make sense?

ditlevditlev Member, Top Host, Host Rep
edited October 2015 in General

http://cdn.net/pricing-stats/ << we've been thinking about how CDN's are sold.

When I've used CDN's in the past it's always been to get a lower latency, and I suspect it's top of mind of most people looking for CDN services.

Yet - for some reason it's not what CDN providers are generally selling. They are selling GB's, distributed over a number of pops. They do not present a lot of transparency or actually show you what latency improvements you are paying for.


We've tried to change that here: http://cdn.net/pricing-stats/ - is it clear? Does it make sense? Would you chose the map or the graphs as the initial image? Do you get the 50ms green line? What would you change (apart from making it look better on mobile)?


Thanks for your input!


:)

D

«1

Comments

  • It makes no sense to me. I mean, Worldwide latency avg: 5.94ms. You're telling me that everyone is going to have a (on average) 5.94 ms latency to my website? That's an absurd speed and if you could pull that off, you'd probably just be focusing on the CDN given in what hot demand it'd be in.

  • There is cedexis offering multiple benchmarking metrics and you can compare the major cdn provider's performance.

    http://www.cedexis.com/reports/#?report=cdn_response_time&country=US&date=2015-10-08

  • vfusevfuse Member, Host Rep

    The map makes a lot more sense to me on first impression. With the graph you have to go thru all the colors to make any sense of the data.

  • Does not look like anycast, right?

  • For a CDN company, your site sure does take awhile to load for me... Looks like everything is loading locally off the server in the UK and not via a CDN, so when I ping the URL assets are loading from:

    PING cdn.net (89.238.158.76): 56 data bytes
    64 bytes from 89.238.158.76: icmp_seq=0 ttl=49 time=164.733 ms
    64 bytes from 89.238.158.76: icmp_seq=1 ttl=49 time=162.509 ms
    64 bytes from 89.238.158.76: icmp_seq=2 ttl=49 time=163.426 ms
    64 bytes from 89.238.158.76: icmp_seq=3 ttl=49 time=162.892 ms
    
    --- cdn.net ping statistics ---
    4 packets transmitted, 4 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 162.509/163.390/164.733/0.841 ms

    Kinda rough considering your western US chart is showing <1ms avg latency.

    Thanked by 1GStanley
  • https://pulse.turbobytes.com/results/5618773becbe400bf8001d55/

    You can buy all the domains you want, but it will take some actual knowledge on the product to even be mentioned in the same sentence as Cedexis.

    http://ping.pe/cdn.net

    Oh, HostDime is under 10ms though!

  • Do you have test IPs for the individual services for us to test out ourselves?

    @ditlev ?

    Thanked by 1rafaelscs
  • PING cdn.net results in ~221ms from San Francisco California.

  • NyrNyr Community Contributor, Veteran
    edited October 2015

    Not sure about the website, but the CDN itself sucks, sorry.

    traceroute to 762920777.r.worldcdn.net (159.122.70.41), 64 hops max, 52 byte packets
     1  10.8.0.1 (10.8.0.1)  82.921 ms
     2  94.242.57.1 (94.242.57.1)  93.460 ms
     3  bg.rnet.ru (94.242.0.1)  84.247 ms
     4  109.239.138.33 (109.239.138.33)  82.492 ms
     5  spb-sth-40g-gw3.gblnet.ru (94.124.182.137)  116.183 ms
     6  ams-par-gw.gblnet.ru (94.124.182.230)  114.751 ms
     7  bbr01.eq01.ams01.networklayer.com (80.249.210.82)  128.958 ms
     8  ae0.bbr02.xn01.fra01.networklayer.com (50.97.18.217)  123.899 ms
     9  ae6.dar01.fra02.networklayer.com (50.97.19.145)  122.125 ms
    10  po1.fcr01b.fra02.networklayer.com (159.122.118.135)  125.301 ms
    11  159.122.70.41-static.reverse.softlayer.com (159.122.70.41)  122.419 ms
    

    RU -> NL -> DE. Okay, maybe just bad luck?

    Let's see from Spain:

    traceroute to test.latency.network (176.67.175.155), 30 hops max, 60 byte packets
     1  ali1-ovz1.ginernet.com (185.47.128.11)  0.048 ms  0.016 ms  0.014 ms
     2  78.136.105.33 (78.136.105.33)  0.803 ms  0.776 ms  0.744 ms
     3  * * *
     4  xe-2-3-0-108.mad50.ip4.gtt.net (77.67.74.113)  12.898 ms  7.895 ms  12.835 ms
     5  xe-11-2-0.lon10.ip4.gtt.net (89.149.185.74)  35.397 ms  35.975 ms  40.476 ms
     6  92.60.249.46 (92.60.249.46)  41.282 ms  41.142 ms  41.135 ms
     7  83.170.70.238 (83.170.70.238)  36.371 ms 83.170.70.230 (83.170.70.230)  36.060 ms  36.018 ms
     8  176.67.175.155 (176.67.175.155)  35.809 ms  30.790 ms *
    

    Routed to London. I don't need a CDN for that.

    Okay, okay, maybe I was just trying with small ISPs and it was just a coincidence. Let's try i3D in The Netherlands then:

    traceroute to test.latency.network (209.95.50.232), 30 hops max, 60 byte packets
     1  95.46.198.1 (95.46.198.1)  8.915 ms  8.918 ms  8.973 ms
     2  80ge.cr1-br2-br3.smartdc.rtd.i3d.net (188.122.95.81)  11.919 ms 80ge.cr0-br2-br3.smartdc.rtd.i3d.net (188.122.95.89)  3.314 ms 80ge.cr1-br2-br3.smartdc.rtd.i3d.net (188.122.95.81)  0.724 ms
     3  be4395.nr11.b025461-0.rtm01.atlas.cogentco.com (149.6.110.21)  9.363 ms  9.409 ms be4396.nr12.b025461-0.rtm01.atlas.cogentco.com (149.14.14.29)  3.073 ms
     4  te0-0-1-1.rcr21.rtm01.atlas.cogentco.com (154.25.7.17)  9.313 ms be2580.rcr21.rtm01.atlas.cogentco.com (154.25.7.49)  9.317 ms te0-0-1-1.rcr21.rtm01.atlas.cogentco.com (154.25.7.17)  9.302 ms
     5  be2638.ccr42.lon13.atlas.cogentco.com (130.117.3.65)  8.806 ms  8.804 ms  8.789 ms
     6  be2391.ccr21.lpl01.atlas.cogentco.com (154.54.39.150)  82.402 ms  81.861 ms  81.740 ms
     7  be2061.ccr21.jfk05.atlas.cogentco.com (154.54.3.70)  79.152 ms  80.557 ms  80.983 ms
     8  be2669.rcr13.b007023-2.jfk05.atlas.cogentco.com (154.54.42.166)  80.525 ms be2668.rcr13.b007023-2.jfk05.atlas.cogentco.com (154.54.40.74)  80.741 ms be2657.ccr42.dca01.atlas.cogentco.com (154.54.31.109)  90.077 ms
     9  38.104.74.46 (38.104.74.46)  77.296 ms be2359.ccr42.jfk02.atlas.cogentco.com (154.54.43.110)  83.957 ms 38.104.74.46 (38.104.74.46)  78.594 ms
    10  d15f32e8.setaptr.net (209.95.50.232)  78.893 ms  78.908 ms  77.689 ms
    

    Routed to f***ing New York City.

    Thanked by 2GStanley Infinity
  • Indonesia/Asia

    where's your test IP ??

    let's test their own website

    PING cdn.net (89.238.158.76) 56(84) bytes of data.
    64 bytes from 89.238.158.76: icmp_seq=1 ttl=46 time=209 ms
    64 bytes from 89.238.158.76: icmp_seq=2 ttl=46 time=209 ms
    64 bytes from 89.238.158.76: icmp_seq=3 ttl=46 time=210 ms
    64 bytes from 89.238.158.76: icmp_seq=4 ttl=46 time=209 ms
    64 bytes from 89.238.158.76: icmp_seq=5 ttl=46 time=209 ms
    64 bytes from 89.238.158.76: icmp_seq=6 ttl=46 time=209 ms
    
    --- cdn.net ping statistics ---
    6 packets transmitted, 6 received, 0% packet loss, time 5004ms
    rtt min/avg/max/mdev = 209.323/209.696/210.040/0.519 ms
    

    traceroute

     4  180.252.1.165 (180.252.1.165)  4.974 ms  4.944 ms  4.481 ms
     5  61.94.171.69 (61.94.171.69)  5.409 ms  6.923 ms  4.864 ms
     6  180.240.193.42 (180.240.193.42)  27.586 ms  33.719 ms  33.661 ms
     7  * * *
     8  180.240.204.22 (180.240.204.22)  25.977 ms  29.499 ms  23.260 ms
     9  180.240.204.22 (180.240.204.22)  23.121 ms  23.010 ms 180.240.204.6 (180.240.204.6)  29.467 ms
    10  snge-b2-link.telia.net (80.239.128.141)  24.378 ms  47.775 ms  26.614 ms
    11  prs-bb2-link.telia.net (62.115.134.128)  202.521 ms prs-bb3-link.telia.net (80.91.247.64)  203.619 ms prs-bb3-link.telia.net (62.115.114.36)  200.565 ms
    12  ldn-bb2-link.telia.net (80.91.246.176)  309.370 ms ldn-bb2-link.telia.net (62.115.114.230)  212.638 ms ldn-bb2-link.telia.net (80.91.246.176)  286.538 ms
    13  ldn-b1-link.telia.net (62.115.113.221)  205.324 ms ldn-b1-link.telia.net (62.115.142.235)  215.982 ms ldn-b1-link.telia.net (62.115.114.137)  208.463 ms
    14  m247-ic-313694-ldn-b1.c.telia.net (213.248.104.150)  201.069 ms  206.422 ms  201.859 ms
    15  te-1-5-11.bb1.man1.uk.m247.com (77.243.179.65)  220.022 ms  215.762 ms  215.586 ms
    16  te-12-3-0.core-dc1.man4.uk.m247.com (77.243.179.229)  224.235 ms  213.721 ms  217.422 ms
    17  te-7-5-0.core-dc2.man4.uk.m247.com (77.243.176.106)  211.543 ms  214.390 ms  210.246 ms
    18  te-5-4-0.bg2.man.m247.com (77.243.179.214)  223.822 ms  216.475 ms  219.739 ms
    19  89.238.158.76 (89.238.158.76)  212.592 ms !X  211.366 ms !X  212.591 ms !X
    

    LOW LATENCY CDN!!!

  • Yeah that's absolutely crazy, I thought CDN.net was pretty decent - as they're probably the most popular.

    Shocking results.

  • Try akamai.com.

  • Using Akamai through XCDN (by Exceda)

    Seemed shady at first to go through a reseller, but within 24 hours they setup a full proper Akamai setup w/ custom domain. I pay $8 USD per month for every CDN location Akamai has and never have gone beyond overages.

    Just works and makes sense. Also, I would love to see you throw some Mainland China into your averages, HK and JP are a cakewalk. Even India isn't a struggle.

    And 100ms to AU, pathetic. Please learn BGP / Anycast. And then return when you have a SYD / Brazil PoP online if be asking for $100/mo.

  • @Nyr said:
    Not sure about the website, but the CDN itself sucks, sorry.

    > traceroute to 762920777.r.worldcdn.net (159.122.70.41)

    Didn't realize his sig, it's the standard OnApp CDN.. which KeyCDN outperforms at less than half the cost (from my experience/testing).

  • @GStanley said:
    I pay $8 USD per month for every CDN location Akamai has and never have gone beyond overages.

    Is that $8 per zone? (ie. can you have multiple zones on those plans)

  • mikeyur said: Is that $8 per zone? (ie. can you have multiple zones on those plans)

    $8/mo to Exceda. Multiple zones / vanity CNAMEs that resolve to akamai.net rDNS. Not a cheap sub-plan type setup or less premium.

    Keep it under 100GB and it'll only be $8, otherwise 9 cents per GB over.

  • @GStanley said:
    $8/mo to Exceda. Multiple zones / vanity CNAMEs that resolve to akamai.net rDNS. Not a cheap sub-plan type setup or less premium.

    >

    Keep it under 100GB and it'll only be $8, otherwise 9 cents per GB over.

    Yeah, that's fine. I'm just handling small-ish site assets, I think I'm around 40GB/mo right now across multiple low to moderately trafficked sites. Just gets pricey at $8/mo if I can only use 1 zone per plan - but if I can spread that account across 5-10 domains/zones then it'd be perfect. Killer pricing for Akamai quality.

  • singsingsingsing Member
    edited October 2015

    GStanley said: $8/mo to Exceda. Multiple zones / vanity CNAMEs that resolve to akamai.net rDNS. Not a cheap sub-plan type setup or less premium.

    Hmm, Akamai still chooses the PoP to serve from based on where the DNS resolver is, right? Has anything been done to fix nameserver 8.8.8.8 / Akamai interoperability?

    Ah, found the answer to this https://www.quora.com/OpenDNS/Why-doesnt-Akamai-support-the-EDNS-client-subnet-extension (despite the article title it -is- currently supported for Google's DNS servers, and possibly others that have signed an agreement with Akamai, but it is not supported by default for all resolvers).

  • eLohkCalbeLohkCalb Member
    edited October 2015

    GStanley said: Using Akamai through XCDN (by Exceda)

    "XCDN is not currently available in your region."

    OK... :)

  • @mikeyur said:
    Killer pricing for Akamai quality.

    So bad, no SSL suppprt...

  • wow such premium route - AT to NL even though my ISP has heavy DECIX peering which is 20ms more near...

    [email protected] :: ~/Downloads# traceroute 762920777.r.worldcdn.net
    traceroute: Warning: 762920777.r.worldcdn.net has multiple addresses; using 81.95.151.210
    traceroute to 762920777.r.worldcdn.net (81.95.151.210), 64 hops max, 52 byte packets
     1  atlas (10.250.0.1)  0.299 ms  0.258 ms  0.148 ms
     2  192.168.3.1 (192.168.3.1)  0.528 ms  0.492 ms  0.350 ms
     3  172.16.22.38 (172.16.22.38)  28.245 ms  49.693 ms  37.987 ms
     4  172.16.25.17 (172.16.25.17)  53.331 ms  43.552 ms  43.886 ms
     5  213.94.72.44 (213.94.72.44)  27.818 ms  55.972 ms  26.285 ms
     6  213.94.72.5 (213.94.72.5)  33.482 ms  19.318 ms  48.736 ms
     7  92.60.6.245 (92.60.6.245)  35.644 ms  46.941 ms  38.573 ms
     8  ae7-997.r06.inx.vie.at.nextlayer.net (92.60.3.161)  35.073 ms  20.306 ms
        ae6-996.r06.inx.vie.at.nextlayer.net (92.60.2.161)  42.147 ms
     9  ae7-997.r06.uni.vie.at.nextlayer.net (92.60.3.193)  38.745 ms  69.709 ms  18.348 ms
    10  bbr01.eq01.ams01.networklayer.com (80.249.210.82)  104.028 ms  65.628 ms  50.006 ms
    11  ae5.dar01.sr01.ams01.networklayer.com (50.97.18.237)  58.873 ms
        ae5.dar02.sr01.ams01.networklayer.com (50.97.18.239)  53.053 ms
        ae5.dar01.sr01.ams01.networklayer.com (50.97.18.237)  73.754 ms
    12  159.253.158.149-static.reverse.softlayer.com (159.253.158.149)  82.857 ms
        159.253.158.151-static.reverse.softlayer.com (159.253.158.151)  73.348 ms  63.563 ms
    13  81.95.151.210-static.reverse.softlayer.com (81.95.151.210)  63.603 ms  60.613 ms  54.538 ms
    
  • ditlevditlev Member, Top Host, Host Rep

    Thanks for all your feedback.

    Ive upped some speedtest files here: http://www.latency.network/ just did this myself, so no fancy design or features.

    My point with the post was more around the actual order process, to see if it made sense to you guys to sell at a fixed price with different levels of transfer incl. And if the overview of the ping times in the different packages made sense as well.

    Thanks anyway guys!

    :)

    D

  • @ditlev said:

    From New Jersey, I'm getting 20 - 25 ms. So, I just don't see where you're pulling your numbers from? I think that's the problem. You're putting up 1 ms average, but where are you getting that from? That's not really a feasible average latency.

  • ditlevditlev Member, Top Host, Host Rep

    @Steven_F said:
    From New Jersey, I'm getting 20 - 25 ms. So, I just don't see where you're pulling your numbers from? I think that's the problem. You're putting up 1 ms average, but where are you getting that from? That's not really a feasible average latency.

    we use the APIs and monitor from http://www.monitis.com to test the locations constantly and generate the graphs based on their data.

  • @ditlev said:

    -.- You're testing from datacenter to datacenter, which isn't really fair, since most people don't live in datacenters.

    Thanked by 1mrTom
  • ditlevditlev Member, Top Host, Host Rep

    @Steven_F said:
    -.- You're testing from datacenter to datacenter, which isn't really fair, since most people don't live in datacenters.

    True, fair comment - not sure how else I could automate this though...

  • @ditlev said:

    For real world numbers, you can't. The only thing you could do is try and get a bunch of people to run the tests and then use those numbers.

  • ditlevditlev Member, Top Host, Host Rep

    @Steven_F said:
    For real world numbers, you can't. The only thing you could do is try and get a bunch of people to run the tests and then use those numbers.

    yup, but those would always be biased, and performance tend to change over time. Here I provide a realtime view on how the traffic is NOW.
    I guess I could set it up as an index number and show the different packages as an index value rather than in ms?

  • @ditlev said:

    The problem with the providing speed in terms ms is that no one will actually see that performance. You're going to get hit with a lot of complaints and refund requests. You're promising 1 ms, but sites won't get that.

  • InfinityInfinity Member, Host Rep

    CDN-X, CDN-EXEC & CDN-LUX; someone's been using Uber in London I see.

This discussion has been closed.