Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- 85% measures the number of DNS records used against the applicable allowance, rather than traffic, bandwidth, or DNS query volume.
- A zone quota measures one zone. Enterprise account quotas combine zones, with public and internal zones counted separately.
- The default Free allowance depends on when the zone was created, with a cutoff of September 1, 2024 at 00:00:00 UTC. It is not always 200 records.
- Records created by services such as Email Routing also count. Check actual usage before adding records instead of counting only manual additions.
What does the 85% warning tell you?
Cloudflare’s October 6, 2026 announcement says the DNS records page displays a warning once 85% of the applicable record quota has been used. The quota limits how many DNS records you can create. A record holds address information or other service information for a domain; the number of records is a different measure from traffic or queries per second.
Establish the counting scope before calculating headroom. In a hypothetical zone with an actual allowance of 200 records and 170 records in use, usage is 85% and the arithmetic remainder is 30 records. This is a planning example. Later additions by another administrator or service change that remainder, so the example cannot guarantee that a batch import will succeed.
This capacity warning alone cannot establish that a website’s DNS resolution has failed. If access problems occur at the same time, check capacity information and actual DNS responses separately, keeping the time and observed error. A record count does not replace a check of the particular domain’s resolution result.
Which default limit applies to an individual zone?
A zone is a domain area whose DNS you manage in Cloudflare. The documentation says quotas apply per zone or per account, depending on the plan; both limits are not applied together. Establish which applies before comparing an account total against an individual zone’s allowance.
Under the default per-zone limits, Free zones created before September 1, 2024 at 00:00:00 UTC have an allowance of 1,000 records. Free zones created at or after that instant have 200. The cutoff concerns the zone’s creation time in UTC, rather than the domain purchase date, today’s local date, or the most recent sign-in.
Pro and Business each have a default per-zone limit of 3,500 records. Enterprise uses an account quota without a separate per-zone limit. These are published defaults: verify your current allowance and usage before making capacity decisions. The documentation links to an API for a zone’s current quota, where applicable, and its usage. This guide does not assume your account uses the default allowance.
Why must Enterprise administrators count other zones?
An Enterprise account quota covers the total DNS records across all zones in the account instead of imposing individual zone limits. Cloudflare says this distribution is available regardless of each zone’s plan. A low record count in the current zone therefore cannot establish how much capacity remains across the account.
Public zones and internal zones are counted separately, each with a default account allowance of 1,000,000 records. Keep those two groups separate when checking capacity; do not combine them against a single one-million-record limit. The current account allowance and usage can also be retrieved through the API linked in the official documentation. Its counting scope differs from a record list for just one zone.
Cloudflare directs Enterprise customers who need a higher account quota to their account team. Confirm the allowance and terms for your account. A product statement that Cloudflare can support millions of records does not establish that your account has already received that capacity.
Why can usage rise without your manual additions?
DNS records created on your behalf by other Cloudflare services count toward the quota too. The documentation gives the TXT and MX records added by Email Routing as examples. Counting only records you added manually can therefore miss part of the usage. Start by establishing which service owns each record.
When planning records for domain verification, email, or an application, compare the number of new records with current headroom and consider other administrators or services that may write records at the same time. The documentation explicitly says that a zone must still be within its record limit for you to create new records yourself through the dashboard or API.
Avoid deleting an unfamiliar record merely to reduce the count. Ask the service owner to confirm its purpose and dependencies, then use the existing change process. An individual email or verification record may serve a separate purpose. These checks do not require changing records, switching proxy status, or submitting private configuration.
Check capacity, then plan the next step
First, confirm the account and zone you are viewing. Note the warning’s counting scope, actual allowance, current usage, and observation time. For a Free zone, check its creation time against the UTC cutoff. For Enterprise, check the account totals for public and internal zones separately.
Second, list the purposes of existing and planned records, including those created by services. Compare the required additions with headroom at the correct scope. A nearly empty zone is not evidence that the whole account has enough capacity.
Third, take a capacity shortfall to an authorized account administrator. Enterprise customers needing more records can contact their account team through the documented route. Keep separate observations if resolution or record creation also fails. This guide reflects public documentation checked on November 6, 2026 and does not replace your account terms.
Sources
Frequently Asked Questions
Why can a zone occasionally contain slightly more records than its limit?
Cloudflare documents a small enforcement buffer for records created by its other services to avoid disrupting those services. A zone can therefore occasionally sit slightly above its usual limit. This does not grant extra capacity for manual additions: records you create through the dashboard or API remain subject to the documented record limit.
Does the 85% warning automatically increase capacity or introduce charges?
The announcement describes a capacity warning and its counting scope. It does not announce automatic quota increases or a new charging rule. Any allowance change and applicable plan or contract terms require your account’s current information and formal confirmation from Cloudflare; the warning alone does not establish a billing or expansion outcome.