First published

More broken images do not necessarily mean a higher delivery bill.

TechnologyCloudflare Images documented hosted product; posted US dollar rate, not a regional tax or plan quote.As of · Asia/Singapore

What this means

Cloudflare added a dashboard that shows hosted image requests, including ones that failed. But the company bills a hosted delivery only when it succeeds and is bigger than 1,024 bytes. If your site suddenly shows more broken images, compare the same dates in the new chart and your existing delivery usage. Fixing the image problem and explaining the bill are separate decisions. Check storage and transformations separately.

Your next move

Use the same completed dates to check the new hosted image status chart and the existing Images Delivered usage line. Keep image storage and transformation charges separate. Do not generate traffic or change a live setting.

Use this if

You already use Cloudflare Images for hosted images and have access to existing status and billing records.

Wait or stop if

Keep existing reporting if the dates or bill scope do not match. Do not infer a bill change from the counts alone.

Outside this scope

Existing product use, read-only review. No result for a named site, full invoice, bill saving, tax, account change or request generation.

Information cutoff

Read the evidence

The connection

What changed

Cloudflare’s 20 November changelog says a new dashboard shows up to 30 days of hosted image delivery data, including response codes, formats and variants. The launch did not announce a new rate.

Dated baseline

What the dated baseline showed

Cloudflare added sampled transformation analytics on 23 September. Those estimates concern requests to transform images. The 20 November release adds a separate view for hosted image deliveries.

Why this matters

A spike in broken images can cost readers a working page without adding to the specific hosted-delivery fee.

Who is affected

A site operator already using Cloudflare Images for hosted assets, with access to their own existing analytics and billing records.

The connection

A request count includes calls that may never produce an image the reader can see. The fee applies only to successfully delivered, eligible hosted responses.

How it could work

Cloudflare reports request status in the dashboard. The price rule counts certain successful hosted responses, not each request. A not-found response can therefore show a user-facing fault without contributing to this delivery charge. A small but successful response can also be excluded.

Who benefits or bears the cost

A status rise can help a site team decide whether to investigate image errors or a change in the delivery bill first. A reliable comparison uses the same dates and account, not an assumption that every request costs money.

What we don’t know

Exact publication clock, customer entitlements beyond the hosted product context, aggregation and dashboard-to-invoice parity, user impact, billed totals and savings are not verified.

The four evidence checks

What to check

Start with the new hosted image dashboard. Check the response code and the time interval. Then find the separate Images Delivered usage line for that account.

What it supports

Compare two completed periods of equal length for the same account. Identify the hosted asset or variant for diagnosis; use the whole same account when comparing its bill.

What would confirm it

If failures rose but eligible Images Delivered usage did not, report the visible fault separately from the fee change. If charges rose, look for qualifying successful delivery, storage or transformations in the corresponding usage lines.

What would tell you to stop

Stop if dates, account, asset path or charge categories cannot be matched. Do not change a budget based only on a request count.

Next review trigger

On the next completed daily review from 21 November, compare two finished same-length windows. Recheck the next settled invoice before changing a budget.

Emerging data

Emerging data narrative

What changed

September’s original transformation dashboard reports a sampled estimate for image transformations. The 20 November changelog adds a hosted-image view covering up to 30 days of requests. These are different products and costs.

Two analytics views, two underlying jobs
  1. 23 September 2026Cloudflare announced sampled analytics for image transformations.
  2. 20 November 2026New request and status view for hosted images, up to 30 days.
The newer chart does not prove a new price.

A request is not always billed

To count toward the hosted-delivery fee, Cloudflare says a response must succeed with code 200 and be larger than 1,024 bytes. A not-found response is not billed as delivery. That makes the status chart useful for finding trouble, not a total-cost calculator.

Which responses count toward the delivery line?
  • Code 200, over 1,024 bytesEligible hosted delivery.
  • Code 200, 1,024 bytes or smallerNot billed as hosted delivery.
  • Code 404, image not foundNot billed as hosted delivery. Can still show an operational problem.
Cloudflare’s cited rule for this line only; storage and transformations are separate.

Compare completed periods

Use the same finished dates and same account. Keep failed requests, eligible hosted deliveries and separate storage or transformations apart. Check the affected image first, then the bill’s aggregate usage. No new traffic or site change is needed.

Separate the image fault from the bill
  1. MatchSame account and completed dates.
  2. InspectReview image failures by asset or version.
  3. CompareRead the separate metered hosted delivery line.
Read-only comparison, not a customer result.

Consequences and economics

First-order consequence

The new hosted dashboard shows request status and other detail that the older transformation view does not describe.

Second-order consequence

An operator can locate an error peak without assuming it explains a fee increase.

Third-order consequence

Matching dates and billing categories can separate reliability work from cost work.

Fourth-order consequence

Fixing a broken-image problem can improve reliability while leaving the specific delivery charge unchanged, or can increase successful deliveries. The result depends on actual usage.

Fifth-order consequence

Repeated same-account results could encourage teams to track image reliability separately from delivery spend. No saving, customer retention change or staffing effect was observed.

Observed costs and benefits

Cloudflare lists US$1 per 100,000 eligible hosted deliveries. At that rate, 100,000 qualifying deliveries imply US$1 for this line alone. An additional 25,000 not-found responses would add nothing to that line. This is an illustration, not observed activity or a full bill.

Challenge and uncertainty

Disconfirming evidence

Some successful responses are too small to count. A separate storage or transformation increase can also raise a bill without any change in hosted deliveries.

Alternative explanation

If the newer chart cannot match the billing dates and account, keep the current billing review and use the chart only to find affected images.

What would confirm it

A same-scope comparison of existing status data and the corresponding delivery count would show whether they moved together. It is not automatic invoice reconciliation.

What would disprove it

If eligible successful delivery increased for the same window, do not dismiss its role. If periods or scopes cannot be compared, leave the cause open.

Facts, inference and open questions

Claim

  1. Claim or open question

    The 20 November changelog adds up to 30 days of hosted image delivery analytics. Cloudflare hosted image delivery changelog

    Sources for this passage

    Report this passage

    Evidence status

    Observed fact

    Scope and limits

    Issuer-declared availability, not tested in an account.

  2. Claim or open question

    Cloudflare’s hosted delivery rule counts only successful code 200 responses larger than 1,024 bytes. Cloudflare image prices and eligible delivery

    Sources for this passage

    Report this passage

    Evidence status

    Observed fact

    Scope and limits

    Different billing can apply to storage and transformations.

  3. Claim or open question

    The earlier sampled transformation-analytics announcement was dated 23 September. Cloudflare Images changelog

    Sources for this passage

    Report this passage

    Evidence status

    Observed fact

    Scope and limits

    Not the new hosted dashboard.

  4. Claim or open question

    An increase in not-found responses can indicate broken loads without adding to the hosted Images Delivered line. Cloudflare image prices and eligible delivery

    Sources for this passage

    Report this passage

    Evidence status

    Our inference

    Scope and limits

    No measured responses or bill. Compare same-account periods.

  5. Claim or open question

    A rise in eligible success, storage or transformations may separately explain a higher total.

    Evidence status

    Alternative explanation

    Scope and limits

    No cause known for a customer account.

  6. Claim or open question

    No billing parity or actual customer savings were verified.

    Evidence status

    Unknown

    Scope and limits

    Use the actual usage record.

Research layers

Twenty research checks

  1. Research layer

    Money flow

    Layer heading

    01 Money flow

    Research and limitations

    posted rate, no invoice inspected.

    Evidence status

    Unknown

  2. Research layer

    Orders and deposits

    Layer heading

    02 Early orders and deposits

    Research and limitations

    no new plan, upgrade or configuration proposed.

    Evidence status

    Unknown

  3. Research layer

    Bottlenecks

    Layer heading

    03 Supply bottlenecks

    Research and limitations

    distinguish failed requests from qualifying delivered images.

    Evidence status

    Our inference

  4. Research layer

    Other beneficiaries

    Layer heading

    04 Other beneficiaries

    Research and limitations

    operators investigating existing cost or failed image loads.

    Evidence status

    Our inference

  5. Research layer

    Company finances

    Layer heading

    05 Company finances

    Research and limitations

    no Cloudflare revenue or customer savings established.

    Evidence status

    Unknown

  6. Research layer

    Costs and payback

    Layer heading

    06 Costs and payback

    Research and limitations

    100,000 eligible deliveries = US$1 on that delivery line only.

    Evidence status

    Our inference

  7. Research layer

    Ownership and institutions

    Layer heading

    07 Insider and institutional activity

    Research and limitations

    all original sources are Cloudflare; separate evidence roles, not independent customer data.

    Evidence status

    Observed fact

  8. Research layer

    Hiring

    Layer heading

    08 Hiring

    Research and limitations

    no staffing or time saving observed.

    Evidence status

    Unknown

  9. Research layer

    Government and public procurement

    Layer heading

    09 Government budgets

    Research and limitations

    none material.

    Evidence status

    Not applicable

  10. Research layer

    Language and foreign evidence

    Layer heading

    10 Foreign-language evidence

    Research and limitations

    public US-dollar rate; tax, currency and contract terms not inferred.

    Evidence status

    Observed fact

  11. Research layer

    Behaviour and payments

    Layer heading

    11 Behaviour and payments

    Research and limitations

    no reader views or conversions measured.

    Evidence status

    Unknown

  12. Research layer

    Contradictory readings

    Layer heading

    12 Contradictory readings

    Research and limitations

    transformations and storage use different billing lines.

    Evidence status

    Observed fact

  13. Research layer

    Missing evidence

    Layer heading

    13 Missing evidence

    Research and limitations

    account eligibility, matched invoice and dashboard coverage not measured.

    Evidence status

    Unknown

  14. Research layer

    Approvals and commercialisation

    Layer heading

    14 Pilots and approvals

    Research and limitations

    vendor-reported dashboard, not a customer deployment test.

    Evidence status

    Observed fact

  15. Research layer

    Alternatives and competitive weaknesses

    Layer heading

    15 Competitive alternatives

    Research and limitations

    account/time range or response size may cause a count mismatch.

    Evidence status

    Alternative explanation

  16. Research layer

    Geography

    Layer heading

    16 Cross-border consequences

    Research and limitations

    dashboard country filter is diagnostic, not an availability map.

    Evidence status

    Observed fact

  17. Research layer

    Historical comparison

    Layer heading

    17 OTR outcomes and past forecasts

    Research and limitations

    23 Sep 2026 transformation analytics, 20 Nov 2026 hosted delivery view.

    Evidence status

    Observed fact

  18. Research layer

    Awareness and market pricing

    Layer heading

    18 Awareness and market pricing

    Research and limitations

    HTTP 200 and more than 1,024 bytes, not 200 alone.

    Evidence status

    Observed fact

  19. Research layer

    Counter-evidence

    Layer heading

    19 Strongest counter-evidence

    Research and limitations

    same-scope records showing higher eligible delivery volumes justify investigating charges separately; data mismatch stays inconclusive.

    Evidence status

    Our inference

  20. Research layer

    Action and stop rule

    Layer heading

    20 Action clock and stop rule

    Research and limitations

    check the next two attributable completed periods before changing a budget; no production test.

    Evidence status

    Our inference

Evidence and sources

References

  1. Source

    Cloudflare hosted image delivery changelog

    Publisher: Cloudflare

    Original language: English

    published date precision: day

    Source publication date 2026-11-20

    Source retrieval date 2026-11-20T05:15:53.645Z

    Read linked claim · supports

    Coverage and independence

    Original date-only current announcement, new status and variant data for stored hosted assets.

    Evidence translated into English

    No

  2. Source

    Cloudflare image prices and eligible delivery

    Publisher: Cloudflare

    Original language: English

    published date precision: unknown

    Source retrieval date 2026-11-20T05:15:53.645Z

    Read linked claim · supports

    Read linked claim · supports

    Coverage and independence

    Existing pricing and eligibility: US$1 per 100,000 deliveries monthly, HTTP 200 >1,024 bytes; stored images priced separately, remote transformations excluded from hosted delivery.

    Evidence translated into English

    No

  3. Source

    Cloudflare Images changelog

    Publisher: Cloudflare

    Original language: English

    published date precision: unknown

    Source retrieval date 2026-11-20T05:15:53.645Z

    Read linked claim · supports

    Coverage and independence

    The earlier transformation analytics entry is dated 23 September, not November. It describes sampled transformation requests.

    Evidence translated into English

    No

  4. Source

    Cloudflare usage-based billing guidance

    Publisher: Cloudflare

    Original language: English

    published date precision: unknown

    Source retrieval date 2026-11-20T05:15:53.645Z

    Coverage and independence

    Independent-purpose billing workflow reference, expenses and billing intervals, not customer invoices or proof of a matching dashboard count.

    Evidence translated into English

    No

  5. Source

    Cloudflare Images product documentation

    Publisher: Cloudflare

    Original language: English

    published date precision: unknown

    Source retrieval date 2026-11-20T05:15:53.645Z

    Coverage and independence

    Existing product and hosted-variant scope baseline, not a pricing or usage result.

    Evidence translated into English

    No

Gaps in the evidence

The changelog is date-only. All sources are Cloudflare documents with different roles, not independent customer or invoice evidence.

AI powered research