User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
fieldclock.com · Cloud & developer
Is FieldClock down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → fieldclock.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 2 hr ago. Last stored result reached it in 25 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 39 ms | 0 |
| Mon 16 | 0 | 0.0 | 81 ms | 0 |
| Mon 18 | 0 | 0.0 | 79 ms | 0 |
| Mon 21 | 0 | 0.0 | 152 ms | 0 |
| Mon 23 | 0 | 0.0 | 52 ms | 0 |
| Tue 01 | 0 | 0.0 | 151 ms | 0 |
| Tue 03 | 0 | 0.0 | 140 ms | 0 |
| Tue 05 | 0 | 0.0 | 43 ms | 0 |
| Tue 07 | 0 | 0.0 | 23 ms | 0 |
| Tue 09 | 0 | 0.0 | 224 ms | 0 |
| Tue 11 | 0 | 0.0 | 120 ms | 0 |
| Tue 14 | 0 | 0.0 | 62 ms | 0 |
| Tue 16 | 0 | 0.0 | 45 ms | 0 |
| Tue 18 | 0 | 0.0 | 81 ms | 0 |
| Tue 20 | 0 | 0.0 | 134 ms | 0 |
| Tue 23 | 0 | 0.0 | 102 ms | 0 |
| Wed 01 | 0 | 0.0 | 173 ms | 0 |
| Wed 03 | 0 | 0.0 | 92 ms | 0 |
| Wed 05 | 0 | 0.0 | 129 ms | 0 |
| Wed 07 | 0 | 0.0 | 92 ms | 0 |
| Wed 08 | 0 | 0.0 | 104 ms | 0 |
| Wed 10 | 0 | 0.0 | 38 ms | 0 |
| Wed 12 | 0 | 0.0 | 40 ms | 0 |
| Wed 14 | 0 | 0.0 | 81 ms | 0 |
| Wed 16 | 0 | 0.0 | 83 ms | 0 |
| Wed 18 | 0 | 0.0 | 75 ms | 0 |
| Wed 21 | 0 | 0.0 | 55 ms | 0 |
| Wed 23 | 0 | 0.0 | 76 ms | 0 |
| Thu 01 | 0 | 0.0 | 97 ms | 0 |
| Thu 03 | 0 | 0.0 | 101 ms | 0 |
| Thu 05 | 0 | 0.0 | 261 ms | 0 |
| Thu 07 | 0 | 0.0 | 42 ms | 0 |
| Thu 09 | 0 | 0.0 | 128 ms | 0 |
| Thu 11 | 0 | 0.0 | 74 ms | 0 |
| Thu 13 | 0 | 0.0 | 30 ms | 0 |
| Thu 15 | 0 | 0.0 | 63 ms | 0 |
| Thu 17 | 0 | 0.0 | 121 ms | 0 |
| Thu 19 | 0 | 0.0 | 77 ms | 0 |
| Thu 21 | 0 | 0.0 | 70 ms | 0 |
| Fri 00 | 0 | 0.0 | 40 ms | 0 |
| Fri 02 | 0 | 0.0 | 76 ms | 0 |
| Fri 04 | 0 | 0.0 | 34 ms | 0 |
| Fri 06 | 0 | 0.0 | 88 ms | 0 |
| Fri 08 | 0 | 0.0 | 50 ms | 0 |
| Fri 10 | 0 | 0.0 | 28 ms | 0 |
| Fri 11 | 0 | 0.0 | 51 ms | 0 |
| Fri 13 | 0 | 0.0 | 102 ms | 0 |
| Fri 15 | 0 | 0.0 | 25 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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 6 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live FieldClock badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for FieldClock yet. Outages of 10 minutes or more get their own page here.
Having trouble with FieldClock?
One report per service every 10 minutes from this network. No account.
Follow FieldClock
Get an email when FieldClock goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send FieldClock alerts to Slack, Discord or a webhook — free.
About FieldClock
We track FieldClock (fieldclock.com) as part of the Cloud & developer group. FieldClock is the best app for farm labor management. Farm labor is expensive and you need modern tools to make real-time decisions. Save money today.
FieldClock publishes an official status page at status.fieldclock.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 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 59 ms average, 12–121 ms range across 16 successful checks.
Questions
Is FieldClock down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was FieldClock last down?
We have not recorded a public FieldClock incident since monitoring began 6 days ago.
What is FieldClock's uptime?
From our own checks: 100% over 6 days of checks.
How fast does FieldClock respond?
59 ms on average over the last 24 hours (12–121 ms).
Does FieldClock have an official status page?
Yes, at https://status.fieldclock.com.
FieldClock not working for me but the status is fine. What now?
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 FieldClock here at once, the problem is on FieldClock'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 FieldClock. 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.