Contact us

Questions about pricing, migration, or a workload from 5 TB a month upwards? Write to us directly or use the form, and an engineer will reply within 3 business hours.

Write to the right inbox

Sales and Partnerships: sales@blazingcdn.com

Technical Support: support@blazingcdn.com

Abuse reports: abuse@blazingcdn.com

General Inquiries: marketing@blazingcdn.com

Quick Assistance and FAQs

Before contacting us, please visit our Help Center for immediate solutions to common questions.

Ivan Vovk, COO at BlazingCDN
Who answers
Ivan Vovk
COO, BlazingCDN

Moving 100 TB or more a month? Ivan reads every enterprise request himself and replies within 1 business day. No sales sequence in between.

Feedback

Already a customer? Rate us on G2 or Product Hunt. Reviews help other teams decide. G2, Product Hunt

Offices & legal

Headquarters Address:
ADVANCED ADMINISTRATIONS Sp. z o.o.
Niepodległości Avenue, 18, floor 4, 02-653 Warsaw, Poland

Technical partner company: BCDN LTD, Aliakmonos 12, 1st floor, office 101/102, Germasogeia, 4043, Limassol, Cyprus.

Questions buyers ask about contacting BlazingCDN

BlazingCDN answers sales and technical questions by email or through the contact form, and an engineer replies within 3 business hours. Send your monthly terabytes and content type to get a written price without a discovery call. Enterprise requests from 100 TB a month are read personally, and new projects start with a 14-day testing period.

BlazingCDN replies to sales and technical questions within 3 business hours, and the reply comes from an engineer rather than an automated sequence. The 24/7 helpdesk accepts requests at any hour, so a message sent overnight is first in the queue for the next business window. Enterprise requests from 100 TB a month are read personally and answered within the same 3 business hours.

The contact page lists four inboxes. Sales and partnerships handles pricing, capacity and migrations. Technical support handles configuration and delivery problems on live zones. Abuse reports and general inquiries each have their own address. Writing to the right inbox skips one internal hand-off. For example, a question about moving 200 TB of video a month belongs in the sales inbox, while a cache rule that stopped working belongs with technical support. Every reply is written by a person who can read your configuration.

BlazingCDN needs four facts to price a workload: monthly terabytes, content type, main regions and current provider; for example, 50 TB of video a month costs $215 on the published tiers (as of October 2026). Pricing is progressive: $5 per TB for the first 5 TB, $4.50 up to 25 TB, then $4.00 up to 100 TB. One rate applies in the US, Europe and Asia, so regions change routing advice, not the price.

Average file size helps too, because a 50 GB installer and a 20 KB icon need different cache rules. Peak traffic matters for live events. A written price usually comes back the same day by email. There is no setup fee and no request fee. Workloads from 100 TB a month can get enterprise terms, and a quote never raises the published price.

BlazingCDN accepts small projects, but the $25 monthly minimum covers the first 5 TB, so a site moving 2 TB a month still pays $25 (as of October 2026). The contact page is written for workloads from 5 TB a month upwards, where pricing questions start to matter. Smaller projects can usually find answers in the Help Center and on the pricing page without a sales conversation.

The network is built for high-volume static traffic: video on demand, live HLS and DASH, software updates, game patches and large files. Some workloads are not a fit at any size. BlazingCDN does not offer HTTP/3, edge compute, WebSockets or transcoding. A team that needs code running at the edge should say so in the first message. An engineer answers honestly within 3 business hours, including when another product fits better.

BlazingCDN offers calls with an engineer, and onboarding itself takes about one hour with that engineer on the line. Most questions are settled by email first, so the call is spent on configuration rather than discovery. Ask for a call in the contact form or in your email, and suggest a time window that suits your team.

A typical migration starts small. BlazingCDN can run as a second CDN behind DNS with a weighted traffic split, for example 10% of traffic on the new zone while the current provider carries the rest. The share grows once the numbers look right. A KYC check runs before production traffic, so send company details early to avoid a delay. Every follow-up question during the move goes to an engineer who replies within 3 business hours.

BlazingCDN gives new projects a 14-day testing period on real production traffic, billed at the published rate from $5 per TB (as of October 2026). The testing period is not a sandbox. Real users fetch real files, so the measurements reflect your audience rather than a lab. A KYC check comes first, and onboarding with an engineer takes about one hour.

During the 14 days, watch three numbers: cache hit ratio, latency per region and origin traffic. The network averages a 96%+ cache hit ratio, and real-time statistics plus Prometheus metrics show your own figure. For example, a team sending 5 TB through a test zone pays the $25 monthly minimum. No long-term contract follows. If the results do not justify a move, set the DNS weight back and stop. Questions during testing reach an engineer within 3 business hours.