What changed in December 2024
The December 2024 changelog has the full details.
Metrics v2 API
A new metrics API is available under
/v2/organizations/{org}/projects/{project}/metrics. You can request traffic, cache, response status and origin status metrics at minute, day, month or total granularity over a time range you choose. Results are broken down per domain, and a companionmetrics/availableendpoint lists the metrics and granularities you can query.URL purges cover every letter case
When you purge a path, Quant now clears the cached copies of that path whatever letter case visitors used to request it. A purge of
/aboutalso clears responses cached for/Aboutor/ABOUT, so mixed-case links no longer serve stale content after a purge.Longer failover origin timeout
The maximum time-to-first-byte for a failover origin is now 60 seconds, up from 15 seconds. Slower failover origins get more time to respond before a request is abandoned.
Also from October 2024
The October 2024 changelog has the full details.
Long URLs and video streaming
Quant now serves the correct asset more reliably for very long URLs, including URLs with query strings. Range requests for video and other large assets now return the correct content-range information, so playback and seeking work when you stream media through the CDN.
Also from September 2024
The September 2024 changelog has the full details.
Cache purge API
A new endpoint in the v2 API,
/v2/organizations/{org}/projects/{project}/purge, clears cached content programmatically. You can purge by cache key and set the scope: this project only or, if your project supports it, the whole organisation. The purge form in the dashboard now makes it clearer what you select to purge.
Who it is for
Platform and ops teams
Request traffic, cache and status metrics for each domain through the v2 API, at the granularity you need.
Content teams
Purge a path once to clear it in every letter case, so mixed-case links no longer serve stale content.
Failover origin owners
Give a slower failover origin up to 60 seconds to send its first byte before the request is abandoned.
How it works
The v2 API has a CDN metrics endpoint, new in December, and a cache purge endpoint, added in September. Both take your organisation and project in the path:
/v2/organizations/{org}/projects/{project}/metrics
/v2/organizations/{org}/projects/{project}/purgeFor a metrics request, you choose the metrics, the granularity and the time range. The metrics are traffic, cache, response status and origin status. The granularity is minute, day, month or total. The results are broken down per domain. If you do not know which metrics and granularities you can query, call the metrics/available endpoint first.
Purges also changed in December. A path purge now ignores letter case. Before, a purge of /about did not clear copies that visitors had requested as /About or /ABOUT, so those links kept serving stale content. Now one purge clears all of them.
Since September, the cache purge API lets you choose the scope of a cache key purge. It can clear the key in this project only or, if your project supports it, in the whole organisation.
For failover origins, the maximum time-to-first-byte is now 60 seconds, up from 15 seconds. If your failover origin is slow to start a response, it has more time before the request is abandoned.
The cache purge API from September and the delivery fixes from October are in the list above, with their months.
Get started
Query the metrics API
Request metrics under
/v2/organizations/{org}/projects/{project}/metrics.List what you can query
Call the
metrics/availableendpoint to see the metrics and granularities.Purge by cache key
Send a cache key to the v2 purge endpoint, and choose the scope of the purge.
Purge a path once
Purge a path in one letter case. Quant clears the cached copies in every case.
Related: Explore Global CDN · December 2024 changelog
Ready to try it on Quant?
Use the global CDN on your own project, or talk to our team first.