Report a service problem? Welcome to the indian support-center, where you will be slowly spoon-fed the next best canned response that may or may not match your problem. Escalating to anyone with half a clue is near impossible.
Need a quote? Wait weeks at a minimum for someone to get back to you.
Oh, did we break your reporting? Of course this is your fault, Akamai doesn't make mistakes. Now talk to the hand.
If you're in the market for a CDN then there's plenty candidates who will sell you a better experience for less money (Level3, EdgeCast, BitGravity, etc.).
Meanwhile none of the other CDNs has given us such a terrible experience. It's almost as if they care, imagine that!
When you consider that the performance differences are at best marginal (the only real differences exist on mobile and in emerging markets, and Akamai is not on top of that) there's really no good reason to put up with the spoiled brats of Akamai in this day and age.
CDN itself is essentially a commodity; it's not too hard to keep multiple CDNs in rotation. There are probably 20+ big CDNs worth consideration and another bunch of resellers. (Amazon CloudFront, BitGravity, Level3, Limelight are probably the first ones I'd think of for smaller sites; Akamai is still the undisputed king for top performance.)
DNS is the thing which is more interesting to me.
I'd probably go with Route53 for cheap good anycast DNS right now; everyone else seems to either be a clown or super expensive (or bundled with other expensive DNS service). Ultimately I guess I'll end up doing internal DNS. (non-anycast DNS is also a total commodity, but good anycast dns not as much) DynECT also looks pretty good. Not sure what other anycast DNS providers there are in the <$500/zone/mo range.
There are also many other CDNs that exist in the massive territory between CloudFlare and Akamai (such as CDNetworks, the company I had mentioned).
> CDN itself is essentially a commodity; it's not too hard to keep multiple CDNs in rotation.
For latency-insensitive use cases in generally centralized territory, I agree that CDNs are "essentially a commodity". The correct strategy would seem to be to call a number of them, and negotiate a good deal, not to assume that the one that has a printed sticker price is somehow the right choice (as some people here seem to have been doing ;P).
However, to make the counter-point to this: the cache hit ratio that is being reported by CloudFlare for evasi0n.com (note: I do not have control over that site's hosting; that's choice was due to planetbeing and pod2g) is 81% <- this is for a static single-page information site. How various CDNs handle caching, whether they cache you on disk or in RAM, what they do with regards to hot connections or pre-fetching... these all have massive performance implications on your website.
Punishing "old-school enterprise sales tactics" which try to keep price from being transparent is a reasonable choice. If you're a big content site, yes, you should go through the effort, but for someone who just wants a small service, buy from people who publish their prices.
CloudFlare isn't the only CDN which publishes pricing -- CloudFront with AWS is very transparent. Rackspace Cloudfiles is transparent. BitGravity is fairly transparent. Cachefly. etc.
Akamai is the worst at this, but Level3, CDNetworks, and Limelight don't publish pricing either.
Offering a free service like CF does is the genius of the freemium model -- even if your service is more expensive or less suitable at the high end, people who start out because it's free and easy will often stick with you as long as you're "good enough" as they grow.
Regardless, if picking up the phone and negotiating with a CDN, someone whose opinion of you is totally irrelevant and where the worst-case outcome is "we won't do business with you", how are you going to handle support on your own product, or court investors of your company?
If you're doing mostly static data which rarely changes, you can probably get very high hit rates on CloudFlare, and it's cheaper than even crappy $750/Gbps/mo colo bandwidth then.
(EDIT: I guess they switched; I haven't kept up with Rackspace)