Logpush now available on all plans with usage-based pricing
Logpush is now available across all Cloudflare plans (Free, Pro, Business, Enterprise) with usage-based pricing. Each account receives monthly included usage before charges apply, with rates of $0.03 per GB for internal exports and $0.10 per GB for external exports after the included 25 GB monthly allocation.
Cloudflare Logpush is now available on Free, Pro, Business, and Enterprise plans with usage-based pricing. Free, Pro, and Business customers can enable Logpush through self-service. Enterprise customers continue to work with their account team. Logpush Transformers are also now generally available.
Each account receives included monthly usage before charges apply:
- Internal exports: 25 GB per month, then $0.03 per additional GB.
- External exports: 25 GB per month, then $0.10 per additional GB.
- Transformations: 1 GB per month, then $0.04 per additional GB.
R2 and Pipelines use the internal destination rate. All other destinations use the external destination rate.
Existing Enterprise contracts retain their current Logpush pricing through renewal. Workers Logpush for Workers Trace Events retains request-based pricing, and OpenTelemetry destinations retain event-based Workers Observability pricing.
For complete rates, measurement details, and billing examples, refer to Logpush pricing.
Source: original entry ↗
More from Cloudflare
Follow Cloudflare to get its new changes in your feed and email digest.
Cloudflare API MCP server now serves Cloudflare skills
The Cloudflare API MCP server now integrates with the Skills over MCP extension, allowing MCP clients to discover and access Cloudflare skills. Users can add the MCP server endpoint to compatible MCP clients to access these skills.
WAF failed detections field now available in Rules
A new cf.appsec.request.failed_detections field lets you control how rules handle requests when security detections fail. This array of detection IDs covers content scanning, WAF attack scoring, attack signatures, leaked credentials, and AI-based PII/prompt injection/custom topic detection failures, and works across custom rules, rate limiting rules, and request header transform rules.
Markdown for Agents: More efficient in-process streaming conversion
Markdown for Agents now uses an in-process streaming engine at the edge to convert HTML, reducing overhead and memory use. The conversion limit increased from 2 MiB to 6 MiB, and token count headers are no longer generated.