Comments on: CGN vs. CDN

By: mike

mike — Fri, 01 May 2009 01:38:18 +0000

Nice to see the support for CloudFront.

By: rajakay

rajakay — Tue, 28 Apr 2009 21:46:32 +0000

You know? amazon’s recent acquisition? check it here..
http://www.gizmosforgeeks.com/2009/04/28/amazoncom-acquires-lexcycle-maker-of-e-book-app-stanza/

By: Brian Dickerson

Brian Dickerson — Wed, 08 Apr 2009 16:15:40 +0000

Cool post! I’ll bookmark this page and wish to share it to all my friends and clients.

By: Rene Glembotzky

Rene Glembotzky — Tue, 07 Apr 2009 18:26:20 +0000

From Hannover, Germany:

PING d2onuwnge3cit8.sea4.cloudfront.net (216.137.35.222): 56 data bytes
64 bytes from 216.137.35.222: icmp_seq=0 ttl=56 time=194.120 ms
64 bytes from 216.137.35.222: icmp_seq=1 ttl=56 time=196.527 ms
64 bytes from 216.137.35.222: icmp_seq=2 ttl=56 time=194.190 ms
64 bytes from 216.137.35.222: icmp_seq=3 ttl=56 time=194.271 ms
64 bytes from 216.137.35.222: icmp_seq=4 ttl=56 time=194.638 ms

By: tatil

tatil — Tue, 07 Apr 2009 15:09:24 +0000

You should host the images on this blog on CloudFront and see how it goes

By: Bedava indir

Bedava indir — Sun, 05 Apr 2009 09:33:17 +0000

You should host the images on this blog on CloudFront and see how it goes

By: Stephen

Stephen — Thu, 02 Apr 2009 01:41:53 +0000

Jim Thorpe, Pennsylvania (PenTeleData Network)

$ ping images.groo.com
ping: cannot resolve images.groo.com: Unknown host

By: makaveli-mk

makaveli-mk — Wed, 01 Apr 2009 09:35:42 +0000

Also, does CloudFront support either ETAGs or Last-Modified header!

By: Lint

Lint — Sun, 29 Mar 2009 12:21:37 +0000

Host not found

By: Francisco

Francisco — Sat, 21 Mar 2009 17:09:50 +0000

From Vancouver BC, Canada
ISP: Shaw Cable
DNS Servers: OpenDNS.org
(I noticed that all subnet masks submissions started with 216.137.x.x but not mine)

Envoi d’une requête ‘ping’ sur d2onuwnge3cit8.cloudfront.net [67.215.65.132] ave
c 32 octets de données :

Réponse de 67.215.65.132 : octets=32 temps=179 ms TTL=58
Réponse de 67.215.65.132 : octets=32 temps=179 ms TTL=58
Réponse de 67.215.65.132 : octets=32 temps=181 ms TTL=58
Réponse de 67.215.65.132 : octets=32 temps=178 ms TTL=58

Statistiques Ping pour 67.215.65.132:
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 178ms, Maximum = 181ms, Moyenne = 179ms