BlazingCDN is a Warsaw based company that claims to offer top notch CDN service at an extremely affordable price.
The official feature list looks reasonable. For example, the network only has 20 locations, but the company says they are Tier 4 data centers (as best they can), with world-leading providers and access to Tier 1 networks.
Push and pull zones are supported, with video and HTTP streaming available. Free Let’s Encrypt SSL is just a click away. Gzip and HTTP / 2 optimize performance. You get instant cache clearing (full or url) plus support for origin protection, IP support for blacklisting and hotlinking.
You run into problems and blazing CDNs Knowledge base is available immediately. Will it help anyway? Maybe not.
For example, when we saw an article titled “Managing Pull Zone Settings,” we expected a detailed explanation of the various settings. Instead it usually only contains a few words for each of the options. For example, if you’re wondering what activating the CORS header does, the article just says: “Ability to share resources between different origins.”
If you are amazed at the site, there is real live support available 24/7 via email and ticket (however there is no live chat).
BlazingCDN claims to offer “the best CDN services at the best prices” and while we’re not entirely sure about the “best service” part, there is no doubt that it is seriously cheap.
For example, the company’s Pay-As-You-Go plan costs $ 0.005 per GB worldwide (there are no costly regional differences).
That means 6TB of monthly traffic is only $ 30. Bunny’s standard plan can range from $ 60 to $ 360 depending on traffic. CDN77 charges $ 199, and Fastly may charge $ 720 to $ 1,680 with additional requests.
Not impressed? Amazingly, Pay-As-You-Go is BlazingCDN’s most expensive option, and you can save even more with a monthly plan.
There are several tiers, but to take just one example: 25TB of monthly traffic costs $ 125 for the Pay-As-You-Go program, but drops to $ 106.25 if you opt for the monthly Payment sign in, a tiny $ 0.00425 per GB.
Creating a BlazingCDN account looked easy. In an opening field, only our email address and password were requested. After we got that over with, the website also asked for our name, phone number and address, while business users are also required to enter their company name, position and a tax ID.
Although this is a free trial, you will be asked to enter your credit card information. That seemed strange as the website claims in several places that you can pay through PayPal, but we didn’t see a PayPal option when signing up.
The company says they won’t charge you until you use paid services. However, it is more difficult to take control of it when you have submitted credit card details rather than entering into a PayPal agreement.
We thought we might be able to delete our credit card information from the dashboard, but no. The dashboard doesn’t even show the details of the map you provided, let alone allow you to change it.
This is a problem because BlazingCDN will, by default, bill you for the monthly starter plan once the 7-day trial expires. The company warns you upfront, but there aren’t any of the other options we’d expect: no way to turn off auto-billing from the dashboard, no “cancel plan” option, and no knowledge base article letting you know how do you do that.
Okay, there is an option to change the pricing plan. What if we switched to the Pay-As-You-Go plan and deleted our zones? If we didn’t use traffic, we wouldn’t be billed. It seemed like a solid plan, but there was one problem: the dashboard only allowed us to switch between monthly plans. Pay-as-you-go wasn’t an option.
We gave up and put up a ticket and asked some of the questions we had raised here. How could we pay through PayPal? How can we manage or delete the credit card details we have provided? How can we switch to a Pay-As-You-Go plan if the option is not available in the dashboard?
The next morning we checked our BlazingCDN account. It was now a pay-as-you-go plan, but our ticket was gone, leaving our other questions unanswered. A mistake? We tried creating a different ticket with a different product query and this time we got a response within hours so you can get help if needed.
In a final attempt to figure out BlazingCDN’s payment policy, we went over the policy Terms and Conditions. There were some strange issues, not the least of which was that it appeared to be written for a web hosting company. However, you will still sign up when you hand over your funds. So we were amazed to read this in the Price and Payments section:
‘You agree not to declare any payment in favor of the provider to be unauthorized without a legitimate reason. You agree that for an unjustified statement of this nature, you will pay the provider the appropriate amount or obligation with an additional amount of $ 100 as an administrative cost to the provider related to your false statement. ‘
If you claim that BlazingCDN received the payment without authorization and does not agree, does it reserve the right to fine you? It’s hard to imagine how that would ever happen, or any court would confirm it, but we don’t remember ever seeing any other company threaten their customers in this way.
None of this means that BlazingCDN will bill you or ever do so to anyone without permission or course. We assume that it’s more about being negligent than malicious. The company used an old web hosting terms and conditions template as it didn’t say anything else and supported PayPal, but no longer did that and it just forgot to update the website.
However, this makes a very bad impression and makes BlazingCDN look extremely unprofessional and certainly not like a company that we would entrust our website to.
Sort out any plan or payment issues and BlazingCDN presents its features and options in a familiar web dashboard.
If you’ve used a CDN before, you’ll understand the basics right away. We selected the Anycast CDN option, entered a pull zone name and the URL of our origin server and created it with one click. (We could have referred the service to BlazingCDN’s cloud storage as well.)
The Settings section contains a small number of basic settings. You can enable an origin shield that allows CDN nodes to get their contents from a specific CDN node rather than your server, thereby reducing the load.
A Time to Live value indicates the maximum lifetime of an object in BlazingCDN’s cache. The minimum is one hour, and you can only set values in whole hours, which is a bit inflexible (most CDNs support TTLs of minutes, some allow seconds to be used).
An HTTPS section includes HTTP / 2 support, an option to redirect to HTTPS, and the ability to use SSL (shared, free Let’s Encrypt or your own certificate).
There are a small number of slightly more technical improvements. GET parameters can be removed from queries to improve the likelihood of cache hits. In addition, you can set a minimum number of file requirements before an object is cached, which may reduce the use of cloud storage. In addition, CORS is supported and gzipped content is cached separately.
The site has a few other pull zone settings, but they are no longer inspiring. ‘Hotlink protection’ offers you a whitelist for domains that are allowed to allow hotlink files, but no longer. A cache section allows the cache to be cleared completely or by path and that’s it.
This can be quite enough if your project is simple and you want something to pinpoint and forget. If you want to spend time tailoring the service exactly to your needs, this may not be the product for you.
BlazingCDN is very, very, very cheap, but it doesn’t have many features, and billing questions and some nasty surprises in the fine print make a recommendation impossible.
Source link : https://www.techradar.com/reviews/blazingcdn/