What do you dislike about KeyCDN?
On my first day of using KeyCDN, I sent a link to a potential game publisher, with the game files linked to keyCDN. I confirmed the files exists, the publisher was sent the game link about 8 hours later.
They had issues downloading the game, and after trying for 90 minutes, eventually got it to download.
The evening before my game's launch day, I uploaded the files to KeyCDN, confirmed they were all there, tested the game, and everything looked great.
The following day, I wanted to do a final test, and found the files on the CDN were suddenly giving a CORS error, even though the CORS option on the Zone was enabled.
I confirmed with my web hosts technical team, who did some investigation and confirmed the issue was definately on the CDN side, not my website. The fact that my game may have gone live, on the front page of a very popular game's website, and then overnight suddenly developed CORS errors after a few hours would have been disastrous for my game launch!
I emailed KeyCDN about this, and got a response 6 hours later, with their response from previous support requests being typically a day, which is not bad. Still, for something as critical for myself as a game developer, I would have much preferred a live chat support option, being a paying customer.
Many other CDN providers offer this; I signed up with another CDN provider, gone through the config and setup and deployed my files, and got everything up and running before KeyCDN got back to me. Review collected by and hosted on G2.com.
