Using Tencent EdgeOne as a CDN for two days left me with mixed feelings. The speed is genuinely impressive, the interface is spotless, but I ran into a pit that ended with me asking for a refund.
Setting it up is smoother than most CDNs
The workflow from adding a domain to configuring the CDN is remarkably clean. Every step is self-explanatory—no digging through documentation to figure out what to click next. Anyone who has used certain other CDNs knows the feeling of opening a console and being greeted by a wall of options with no obvious starting point. EdgeOne deserves credit here.
I went with NS delegation to get the full product experience. The whole setup ran without a hitch, and once the domain went live, I ran a speed test and was pleased with the results. Edge nodes are spread across the globe, and latency was solid. The personal tier cuts out a fair number of features, but what's left is still fairly comprehensive, and the logic flows naturally—very little left me confused or hunting for a setting.
Two things that kept me uneasy: protection and billing
On the personal plan, the web protection strategy doesn't let you set a disposition. Everything defaults to "observe" mode, which means logs get recorded but attacks don't get blocked. In other words, you can watch someone hit you and do nothing about it.
The documentation seems to say that only clean traffic after scrubbing counts toward billing. I ran into a burst of CC attacks and still ended up with an outstanding charge—a little over one yuan, but still annoying.
More importantly, there's no spending cap. Once your plan's resources run out, billing switches to pay-as-you-go. For enterprise users that's a feature—it keeps service stable and uninterrupted. For individuals, it means losing sleep, because you never know when someone with nothing better to do will decide to flood your domain. Customer support said they're looking into a cap mechanism and expect to ship it later. But they also noted that CDN billing has inherent delays: at the moment the cap triggers, actual traffic will already have exceeded the limit, and it's still unclear whether that overage will be waived or counted as owed. We'll have to wait for the feature to land.
The pit that made me give up
Even after getting hit for that extra yuan or so, I wasn't ready to walk away—I figured not that many people would bother targeting me. But to be safe, I planned to split DNS resolution by region, routing overseas traffic to Cloudflare. I looked at EdgeOne's origin groups and rule engine: you can configure regional origin fetching, but there's no guarantee it won't still consume traffic. So I decided to move DNS back to DNSPod and switch to CNAME access for EdgeOne.
Since I couldn't change the access method directly, I deleted the domain's NS delegation first, then went to add CNAME access. That's when things got weird—I was told I had no plan and needed to buy a new one.
At first I assumed it was data lag, since I'd just deleted the domain. Ten minutes later, same message. I asked customer support and learned that deleting a domain also deletes the plan, and it can't be restored.
That logic still bothers me. The plan hadn't expired—was it really impossible to just switch the domain? Delete the domain and the plan vanishes with it. Call it a bug if you like, but I hope it gets fixed.
Since the plan couldn't be restored, I went ahead and requested a refund. And that was the end of my two-day EdgeOne trial.
The product has plenty going for it: great speed, a clean interface, and a personal tier that's more complete than you'd expect. It also has real shortcomings, especially around plan and billing rules, which aren't friendly to individual users. I'll keep an eye on future updates, and if the mechanics improve, I'll probably come back—because the speed really is that good.