Status

Every hour a GitHub Actions job asks the live API for three charts and sends one POST, once each, with no retry, and records whether they came back and how fast.

Not enough data yet.No check has been recorded. The first appears after the probe's next hourly run, and the numbers below need at least 20 checks each.

How this is measured

• One attempt per check, no retry. A check passes when the API answers 200 with a PNG within 10 seconds, so "first-try success" is the share of checks that passed.
• Time is time to first byte, as curl reports it. p50 is the median. p95 is the time 95% of checks beat. Both use passing checks only, so a failed check shows in the success rate, not in the times.
• Each run changes one value inside the chart, so every request is a new render and none comes from the CDN cache. Cached images are faster than these numbers.
• One probe from one GitHub Actions runner, once an hour. GitHub can delay scheduled runs. It does not monitor every region.
• The probe says so in its User-Agent, and the usage counters leave its requests out.