Frequently Asked Questions
What is QUIC.cloud?Link to question
How do I get started using QUIC.cloud?Link to question
Do I need to register on QUIC.cloud to use the CDN?Link to question
Yes. You must be registered at my.quic.cloud in order to use QUIC.cloud CDN.
Which CMSs does QUIC.cloud support?Link to question
QUIC.cloud was built exclusively for WordPress sites and integrates seamlessly with the LiteSpeed Cache plugin for WordPress.
What web servers are compatible with QUIC.cloud?Link to question
All web servers, including LiteSpeed Web Server, Apache, Nginx, and OpenLiteSpeed, are compatible with QUIC.cloud. QUIC.cloud acts as a CDN only and will not take the place of any web server.
Can I host my website with QUIC.cloud?Link to question
No. QUIC.cloud provides CDN service and does not host your site. If you do not currently have a host for your website, you might like one of these LiteSpeed Partners.
Does QUIC.cloud CDN support HTTP/2 Server Push?Link to question
Not anymore. Server Push is an outdated technology and is no longer supported by many clients including the Chrome browser.
Does QUIC.cloud support HTTP/3?Link to question
Yes. QUIC.cloud is capable of serving requests via HTTP/3 to browsers that also support the protocol. But unlike other CDNs, QUIC.cloud is also capable of making backend HTTP/3 connections! If your site’s origin server supports HTTP/3 (it does if you are running on LiteSpeed Web Server) and your visitor’s browser supports HTTP/3, then QUIC.cloud will serve your content end-to-end via HTTP/3. If either the origin server or the client cannot handle an HTTP/3 connection, QUIC.cloud will connect via HTTP/2 or HTTP/1 as appropriate.
What’s the difference between QUIC and HTTP/3?Link to question
QUIC was originally a Google effort to improve HTTP/2 by transporting it encrypted over UDP (as opposed to TCP). In 2016, the Internet Engineering Task Force (IETF) began working to standardize the protocol. Part of that process involved splitting QUIC into the transport and application protocols. For some time, the application protocol was referred to as HTTP-over-QUIC, but in November of 2018, the IETF announced that HTTP-over-QUIC would be called HTTP/3.
How do I verify that my site is using QUIC or HTTP/3?Link to question
Can I bypass the CDN?Link to question
Yes, you can easily bypass the CDN if you need to. In your QUIC.cloud dashboard, navigate to the domain you want to bypass, click on the CDN tab, then select CDN Config in the left hand menu. Toggle Bypass CDN to
How does QUIC.cloud know my domain’s IP address?Link to question
What is a PoP?Link to question
PoP stands for “Points of Presence.” A PoP is a location, referenced by IP address, where we have a CDN node. Our PoPs are located around the world. See the CDN Global Coverage Map for more information.
Is there a list of current PoP IP addresses?Link to question
What should I do if the QUIC.cloud IP list changes?Link to question
You will need to make sure the QUIC.cloud IPs in your firewall’s allowlist are up to date. If you are running LiteSpeed Web Server v5.4.12 or newer, this will be handled automatically. The same goes for Imunify360 and Bitninja. Automation through other means will be added in the future, but until then, if your security solution cannot automatically keep up to date with the IP changes, you will need to manually update the QUIC.cloud IPs in your allowlist. Learn more in our Knowledgebase.
Can I be notified in real time of QUIC.cloud IP list changes?Link to question
Do you plan to add more POPs in the future?Link to question
Where can I learn about other QUIC.cloud services?Link to question
Is DNS verification required, and if so, why?Link to question
Yes and no.
It is required if you are using QUIC.cloud CDN, but it is not required if you are only using the Online Services (Image Optimization, Page Optimization, etc.).
DNS verification is our way of making sure that your DNS is configured correctly for use with QUIC.cloud CDN. During the test, we toggle the DNS to point your site to QUIC.cloud PoPs and then check whether it is indeed pointing to the PoPs. If successful, your site is considered Verified. We will automatically generate an SSL certificate (if you’ve enabled that option), and QUIC.cloud CDN will begin handling your domain’s traffic. If there is a failure at any point in the verification process, the DNS will be reverted back to your origin server. You can then fix your configuration and try again.
How can I tell if my DNS is configured correctly?Link to question
If your domain passed DNS Verification, then your DNS is most likely configured correctly. To be sure, try pinging your site twice:
- First use your site’s domain (for example, site.com or
- Then use the URL that QUIC.cloud provided to you (for example
The IP addresses returned from both pings should match.
Alternatively, visit LSCache Check, enter your URL, and look for the
x-qc-pop response header. If it’s there, it means your site was accessed via a QUIC.cloud PoP, and your DNS is configured correctly.
Do I have to use my root domain with QUIC.cloud?Link to question
It is not required to use the root domain. Subdomains may be used, if you prefer.
How do I use my root domain (such as site.com) for QUIC.cloud?Link to question
To use your root (or apex) domain with QUIC.cloud, your DNS must support CNAME flattening or ANAME/ALIAS records. If your DNS provider does not support CNAME flattening, then the only way to use your root domain with QUIC.cloud is to switch your DNS provider. QUIC.cloud offers a free DNS service if you need one. Our knowledgebase has more information about DNS and QUIC.cloud CDN.
Can I use a CDN subdomain (such as cdn.site.com) instead of pointing my entire domain to QUIC.cloud?Link to question
No. Other CDNs that allow you to use a subdomain are only using it for static content (images and other rarely-changing assets). QUIC.cloud functions as a reverse proxy in front of your entire site, and so the site itself must point to the CDN. This is what allows QUIC.cloud to reliably cache your site’s dynamic content on our global network, and to serve everything from cache in a locale-advantaged manner.
What happens if I have a non-WordPress site at the same domain?Link to question
The simplest answer is that “it’s complicated.” Having multiple web apps at the same domain may or may not be problematic. Because the whole domain must be pointed to QUIC.cloud, the WordPress site will be fine, but any others at that domain could potentially experience caching issues, especially if they are running other web apps that use LSCache, or there are special rules in the .htaccess file that must be followed.
If possible, we recommend putting each site in its own subdomain (for example,
blog.site.com instead of
forum.site.com instead of
site.com/forum). This way, you can point the WordPress site’s subdomain to QUIC.cloud without impacting any of the other sites living at that domain.
Does QUIC.cloud offer any Anti-DDoS features?Link to question
Yes. Under the Standard Plan, the QUIC.cloud dashboard allows you to enable and configure reCAPTCHA & WordPress Brute Force Defense, and you may also restrict XML-RPC requests if you wish. Configurable allow and block lists are provided for access control.
While basic security is included with the Free Plan, this level of configurable DDoS protection is not.
Please see Configuring CDN Security for more information.
Can I generate an SSL certificate without updating my DNS?Link to question
No, you cannot generate an SSL Certificate via QUIC.cloud if you do not set up a CNAME record or switch to QUIC.cloud DNS, as instructed.
Approximately how long will it take to generate an SSL Certificate?Link to question
Can I use my own SSL certificate?Link to question
Yes. QUIC.cloud has the ability to generate an SSL certificate for your site, manage the expiration, and keep it automatically up to date, but you may manage your own SSL if you prefer. Visit your QUIC.cloud Dashboard, and add the Certificate and Private Key in the CDN Config section. If you decide to use QUIC.cloud’s automatic SSL feature, we still strongly recommend that you keep your own certificate up to date on your origin server. This is required if you are using QUIC.cloud’s WordPress optimization services, and it allows end-to-end secure connections for the CDN.
How does using QUIC.cloud speed up my site?Link to question
QUIC.cloud uses servers around the world to reduce the physical distance requests must travel. Additionally, QUIC.cloud can cache dynamic content at the CDN level, unlike other CDNs which must retrieve all dynamic requests from the origin server. CDN-level caching not only improves QUIC.cloud’s overall bandwidth speed, but it also minimizes the number of requests to the origin server.
What content does QUIC.cloud cache?Link to question
Does the LiteSpeed Cache crawler also crawl QUIC.cloud?Link to question
Yes. The crawler included in the LiteSpeed Cache for WordPress plugin will populate the cache at the origin server (but only if it is a LiteSpeed server), and also the cache at the QUIC.cloud PoP closest to the origin server.
Under the current CDN cache policy, pages are stored at a PoP for 24 hours from the last access. So, pages that don’t see much traffic will be removed from the PoP’s cache after about a day, but pages that are accessed at least once daily will remain in CDN cache up to 7 days.
Future plans include tiered regional caching, which will increase the CDN cache hit rate and allow us to cache pages in a nearby node longer term.
Please note: if the Crawler > Site IP option is set in the LSCache plugin, the crawler will directly populate the cache for the server at that IP, essentially bypassing QUIC.cloud. If you wish for the local QUIC.cloud PoP to be included in your site’s cache crawl, then you need to leave Site IP blank.
Can I purge the CDN’s cache?Link to question
Yes, however this should not be necessary under normal circumstances. The CDN cache is managed by the LiteSpeed Cache plugin for WordPress, and is sophisticated enough to know when content has changed and requires purging. That said, if you wish to purge the CDN cache manually, visit your QUIC.cloud Dashboard, and press the Purge All CDN Cache button in the Domain Overview section.
How does Auto Redirect www/non-www work?Link to question
Auto Redirect www/non-www speeds up response time by caching redirect requests.
Here’s how it works:
- The browser sends a request for
www.example.comto QUIC.cloud CDN.
- QUIC.cloud sends the
www.example.comrequest to your origin server.
- The origin server returns a response, indicating that the
www.example.comrequest was redirected to
example.com(the non-www domain).
- QUIC.cloud returns this redirect response to the browser and caches the response at the PoP level.
- The next time a
www.example.comrequest is received, QUIC.cloud automatically redirects to
example.com, saving a round trip to the origin server.
This works if the redirect is in the opposite direction, too (
example.com redirecting to
This cache is subject to the same cache policy as any other content cached at a CDN PoP.
What are the differences between the Free Plan and the Standard PlanLink to question
The Free Plan is a simple, no-cost plan with unlimited bandwidth. It works on a smaller pool of PoPs, and does not include DDoS protection features.
The Standard Plan features advanced DDoS security, and use of QUIC.cloud’s entire global PoP network. Domains are given a certain amount of free bandwidth every month, and additional bandwidth may be purchased as necessary.
See CDN Plans and Pricing for more information.
Note, these plans are CDN plans. To learn more about pricing for Online Services, please see Quota and Credits for Online Services.
How many websites can each QUIC.cloud account support?Link to question
There is currently no limit to how many domains can be connected to each QUIC.cloud account.
How much free bandwidth does QUIC.cloud give me?Link to question
It depends on your plan.
Under the Standard Plan, QUIC.cloud provides free bandwidth quota that resets every month. Beyond that, you are free to purchase additional bandwidth as necessary, without limit. The amount of free bandwidth your site receives is controlled by a Tier System, which depends on the site’s origin server. If you feel that your domain has been assigned an incorrect tier, please follow these steps to reassign it to the correct tier.
Under the Free Plan, all bandwidth is free.
Is QUIC.cloud bandwidth calculated per domain or per server?Link to question
Bandwidth is calculated per domain.
What happens if I use more than the allotted data?Link to question
If you exceed your allotted free bandwidth quota before the end of the month (and you have not purchased PAYG quota), the CDN will be bypassed automatically and visitor requests will be directed to your domain’s origin server. When the quota refreshes at the beginning of the next month CDN service will be restored automatically.
Can I transfer credits from one of my domains to another?Link to question
No. Once credits are allocated to a service for a domain in your account, they cannot be transferred to another of your services or domains. To minimize the need for credit transferring between domains, we recommend you avoid allocating account-level credits to specific services until they are needed. Learn more about this strategy in our Knowlege Base.
I ordered credits, but I don't see them on my account. What should I do?Link to question
When you purchased credits, you should have received an Order is Complete email. Inside that email is a link to view the status of your credits. Click the link. For more detailed instructions, please see Missing Credits After Order.
I ordered credits, but am still seeing a daily limit error. What can I do?Link to question
It’s possible the LiteSpeed Cache plugin is not seeing your purchased credits for some reason. There are two things you can try:
- Refresh your domain key: From your WordPress dashboard, navigate to LiteSpeed Cache > General and press the Refresh Domain Key button.
- Sync your credit allowance: From your WordPress dashboard, navigate to LiteSpeed Cache > Dashboard. Click the Refresh button next to the QUIC.cloud Service Usage Statistics section.
One or both of these measures should solve the problem.
What do I do if I haven’t received the activation email?Link to question
The activation email, entitled Activate Your QUIC.cloud Account is sent immediately, from
firstname.lastname@example.org. If you don’t see it in your inbox, please check your spam folder, and add
email@example.com to your email client’s allow list. You may contact us on Slack or via a ticket if you need further assistance.
Why can't I generate an SSL Certificate?Link to question
QUIC.cloud uses Let’s Encrypt to generate SSL Certificates. Sometimes certificate generation fails if your domain’s new or updated DNS records have not fully propagated yet. Please wait a few minutes and try again. If it continues to fail, please contact us on Slack or via a ticket for further assistance.
How do I handle an Invalid Certificate error?Link to question
If you are using a QUIC.cloud-provided certificate, you can regenerate it. In the CDN Config area of your QUIC.cloud Dashboard, press the Generate Certificate button. If you have supplied an SSL certificate of your own, please ensure that it is valid.
I updated my DNS configuration, so why does QUIC.cloud show a CNAME setup error?Link to question
How can I tell if QUIC.cloud is caching my site?Link to question
The easiest way to check whether QUIC.cloud is caching your site is to use the LSCache Check tool. This tool will indicate whether your site supports LSCache, and then it will tell you whether the page is cached at the origin server via LSCache or whether it’s cached by QUIC.cloud. It will also show you the relevant request headers.
I don’t see an x-qc-cache response for my CSS, JS or Images. Why not?Link to question
- You have set Static Cache to
ONin the CDN Config section of your QUIC.cloud Dashboard.
- The backend server provides an
Why hasn’t my page speed score improved along with my site loading speed? Or vice versa?Link to question
The scores provided by page speed tools have little relation to the actual loading time for a website. These scores are relative and are based on how well you have implemented best practices. Best practices, however, do not guarantee your site is the fastest.
My site doesn’t appear to support a QUIC or HTTP/3 connection. What should I do?Link to question
Sites running on QUIC.cloud should support HTTP/3 connections. Use the HTTP/3 Check tool to see whether it’s supported on your site. If it is not, the most likely explanation is that your DNS configuration changes may not have fully propagated, or your DNS has been configured incorrectly. Verify your DNS is correct, and that it has fully propagated. If your site still does not support QUIC or HTTP/3, please contact us on Slack or via a ticket for further assistance.
Why are pages on my site getting 404, 503, 520, 521, 524, or other errors?Link to question
For help with HTTP response code errors, please see the Troubleshooting section of our Knowledgebase.
Why are my requests for Online Services being rejected?Link to question
If your requests for Page Optimization or other online services are being rejected, there are two possible reasons:
- You have run out of free quota for the month, and have not purchased additional quota.
- You still have free quota, but you have reached a daily limit. (Learn more about daily limits.)
If you’ve completely used up your monthly quota, you can wait until the beginning of next month for your services to begin again.
If you’ve reached your daily limit, simply wait until tomorrow and the online services will automatically begin processing your requests again.
If you wish to resume service immediately, you can add more Pay-as-you-go quota with credits from your credit balance. (If you need to refill your credit balance, you can purchase additional credits in our store.)
See About Quota and Credits to learn more about how quota and credits work together.