User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
cfbenchmarks.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 407 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 05:15 | 0 | 0.0 | 453 ms | 0 |
| 07:15 | 0 | 0.0 | 19 ms | 0 |
| 09:15 | 0 | 0.0 | 367 ms | 0 |
| 11:15 | 0 | 0.0 | 335 ms | 0 |
| 13:30 | 0 | 0.0 | 58 ms | 0 |
| 15:30 | 0 | 0.0 | 445 ms | 0 |
| 17:30 | 0 | 0.0 | 74 ms | 0 |
| 19:30 | 0 | 0.0 | 58 ms | 0 |
| 21:45 | 0 | 0.0 | 47 ms | 0 |
| 23:45 | 0 | 0.0 | 384 ms | 0 |
| 01:45 | 0 | 0.0 | 46 ms | 0 |
| 03:45 | 0 | 0.0 | 407 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Scheduled Systems Update
We will be undergoing scheduled maintenance during this time. We do not expect any downtime. Websockets may be disconnected with immediate reconnection during the deployment period.
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for CF Benchmarks yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when CF Benchmarks goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CF Benchmarks alerts to Slack, Discord or a webhook — free.
We track CF Benchmarks (cfbenchmarks.com) as part of the Cloud & developer group. We believe that robust indices of high integrity are essential to the development of the cryptocurrency asset class and its continued adoption by ever more individual and institutional investors. Our indices power a wide range of financial products including derivative contracts, investment funds and structured products. Combining indexing techniques that have been tried and tested in traditional asset classes with concepts unique to cryptocurrencies, furthering adoption of the asset class.
CF Benchmarks publishes an official status page at status.cfbenchmarks.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 211 ms average, 18–453 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public CF Benchmarks incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
211 ms on average over the last 24 hours (18–453 ms).
Yes, at https://status.cfbenchmarks.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report CF Benchmarks here at once, the problem is on CF Benchmarks's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with CF Benchmarks. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.