{{>header}} {{>nav}}

Usage and performance

The public instance of the polyfill service is hosted by the Financial Times, with the generous support of Fastly, who provide CDN distribution. View Fastly network map

{{#if requestsData}}

Traffic volume

This shows the number of requests we have served per day, over the last 180 days, measured by Fastly:

{{#requestsData}} {{/requestsData}}
DateRequests
{{prettifyDate date}}{{requests}}

Response time

Mean global response time, ms, from Pingdom:

{{#respTimes}} {{/respTimes}}
DateResponse time (ms)
{{prettifyDate date}}{{respTime}}

Caching

Hit ratio, last 7 days, from Fastly:

Cache resultRequests
Hits{{hitCount}}
Misses{{missCount}}

Availability

Total downtime, according to Pingdom:

Last 30 days{{prettifyDuration downtime.30d}}
Last 3 months{{prettifyDuration downtime.3m}}
Last 12 months{{prettifyDuration downtime.12m}}

Caching responses that vary by User-Agent is very hard to do with good cache performance. We use a custom Fastly VCL configuration that separates the UA normalisation from the polyfill bundle.

Network performance in detail

95th percentile resource timing metrics, broken down by Fastly edge point of presence, measured using the resource timing API from live polyfill service requests that opted in to anonymously report performance data. Last 30 days, showing only POPs that have served more than 10 requests.

{{#rumPerfData}} {{/rumPerfData}}
PoP Reqs Per connection phase Overall
{{data_center}} {{number_format count}}
{{number_format perf_total_95}}ms
{{else}}

Usage stats cannot be shown, probably because you need to configure the environment variables needed to get data from the Fastly and Pingdom APIs. The specific error thrown by the service is shown below:

Service: {{service}}
Error:   {{msg}}
{{/if}}
{{>footer}}