User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
yardstik.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 57 min ago. Last stored result reached it in 457 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 427 ms | 0 |
| Mon 19 | 0 | 0.0 | 193 ms | 0 |
| Mon 22 | 0 | 0.0 | 234 ms | 0 |
| Tue 00 | 0 | 0.0 | 444 ms | 0 |
| Tue 02 | 0 | 0.0 | 401 ms | 0 |
| Tue 04 | 0 | 0.0 | 509 ms | 0 |
| Tue 06 | 0 | 0.0 | 416 ms | 0 |
| Tue 08 | 0 | 0.0 | 374 ms | 0 |
| Tue 10 | 0 | 0.0 | 571 ms | 0 |
| Tue 12 | 0 | 0.0 | 410 ms | 0 |
| Tue 15 | 0 | 0.0 | 342 ms | 0 |
| Tue 17 | 0 | 0.0 | 287 ms | 0 |
| Tue 19 | 0 | 0.0 | 447 ms | 0 |
| Tue 21 | 0 | 0.0 | 422 ms | 0 |
| Tue 23 | 0 | 0.0 | 350 ms | 0 |
| Wed 01 | 0 | 0.0 | 384 ms | 0 |
| Wed 04 | 0 | 0.0 | 440 ms | 0 |
| Wed 05 | 0 | 0.0 | 385 ms | 0 |
| Wed 07 | 0 | 0.0 | 546 ms | 0 |
| Wed 10 | 0 | 0.0 | 275 ms | 0 |
| Wed 12 | 0 | 0.0 | 422 ms | 0 |
| Wed 14 | 0 | 0.0 | 450 ms | 0 |
| Wed 16 | 0 | 0.0 | 459 ms | 0 |
| Wed 18 | 0 | 0.0 | 217 ms | 0 |
| Wed 20 | 0 | 0.0 | 273 ms | 0 |
| Wed 23 | 0 | 0.0 | 422 ms | 0 |
| Thu 01 | 0 | 0.0 | 440 ms | 0 |
| Thu 03 | 0 | 0.0 | 417 ms | 0 |
| Thu 05 | 0 | 0.0 | 529 ms | 0 |
| Thu 07 | 0 | 0.0 | 349 ms | 0 |
| Thu 09 | 0 | 0.0 | 392 ms | 0 |
| Thu 11 | 0 | 0.0 | 458 ms | 0 |
| Thu 13 | 0 | 0.0 | 263 ms | 0 |
| Thu 15 | 0 | 0.0 | 424 ms | 0 |
| Thu 17 | 0 | 0.0 | 227 ms | 0 |
| Thu 20 | 0 | 0.0 | 401 ms | 0 |
| Thu 22 | 0 | 0.0 | 297 ms | 0 |
| Fri 00 | 0 | 0.0 | 400 ms | 0 |
| Fri 02 | 0 | 0.0 | 430 ms | 0 |
| Fri 04 | 0 | 0.0 | 334 ms | 0 |
| Fri 06 | 0 | 0.0 | 415 ms | 0 |
| Fri 08 | 0 | 0.0 | 378 ms | 0 |
| Fri 10 | 0 | 0.0 | 278 ms | 0 |
| Fri 11 | 0 | 0.0 | 418 ms | 0 |
| Fri 13 | 0 | 0.0 | 432 ms | 0 |
| Fri 15 | 0 | 0.0 | 261 ms | 0 |
| Fri 17 | 0 | 0.0 | 440 ms | 0 |
| Fri 19 | 0 | 0.0 | 457 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Yardstik 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 Yardstik goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Yardstik alerts to Slack, Discord or a webhook — free.
We track Yardstik (yardstik.com) as part of the Cloud & developer group. Yardstik is the Human Trust Platform (HTP), a technology platform that makes human credibility into something you can continuously see, measure, and rely on.
Yardstik publishes an official status page at status.yardstik.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 371 ms average, 139–457 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 Yardstik incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
371 ms on average over the last 24 hours (139–457 ms).
Yes, at https://status.yardstik.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 Yardstik here at once, the problem is on Yardstik'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 Yardstik. 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.