Skip to content

[Changelog] Origin Analytics #30650

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
codyanthony850 wants to merge 4 commits into
base: production
Choose a base branch
from
Draft

[Changelog] Origin Analytics #30650

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ffef9d1
[Changelog] Origin Analytics
codyanthony850 May 6, 2026
0bd7630
Drop support ticket framing from description
codyanthony850 May 6, 2026
6c5443b
Consolidate intro paragraphs
codyanthony850 May 6, 2026
b31e505
Rewrite bullets as outcome-oriented
codyanthony850 May 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions src/content/changelog/speed/2026-05-18-origin-analytics.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
title: Diagnose origin server issues with Origin Analytics
description: Origin Analytics shows how your origin responds to Cloudflare, helping you identify slow endpoints and diagnose errors.
products:
- speed
date: 2026-05-18
---

You can now see how your origin server responds to Cloudflare using **Origin Analytics**, a new tab under **Speed**. Origin Analytics shows what your origin returned alongside what Cloudflare served to the end user, so you can tell whether an issue is your origin, the network path, or Cloudflare. No agent or origin-side setup is required.

Origin Analytics helps you:

- **Spot slowdowns before they cause timeouts.** Track origin response times at P50, P95, and P99 against your zone's configured timeout threshold.
- **Understand what your origin actually returned.** When your users see a `520`, Origin Analytics shows whether your origin returned a `200` with malformed headers, a `503`, or no response at all.
- **Narrow down which endpoint is the problem.** Sort request paths by response time, error rate, or TCP failure rate to isolate the source.

To get started, go to **Speed** > **Origin Analytics** in the [Cloudflare dashboard](https://dash.cloudflare.com/). For more information, refer to [Origin Analytics](/speed/origin-analytics/).
Loading