User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Fulcrum 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 → fulcrumapp.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 22 min ago. Last stored result reached it in 5 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 |
|---|---|---|---|---|
| Tue 11 | 0 | 0.0 | 64 ms | 0 |
| Tue 13 | 0 | 0.0 | 591 ms | 0 |
| Tue 15 | 0 | 0.0 | 366 ms | 0 |
| Tue 17 | 0 | 0.0 | 170 ms | 0 |
| Tue 20 | 0 | 0.0 | 487 ms | 0 |
| Tue 22 | 0 | 0.0 | 136 ms | 0 |
| Wed 00 | 0 | 0.0 | 176 ms | 0 |
| Wed 02 | 0 | 0.0 | 211 ms | 0 |
| Wed 05 | 0 | 0.0 | 266 ms | 0 |
| Wed 07 | 0 | 0.0 | 272 ms | 0 |
| Wed 09 | 0 | 0.0 | 139 ms | 0 |
| Wed 11 | 0 | 0.0 | 57 ms | 0 |
| Wed 13 | 0 | 0.0 | 401 ms | 0 |
| Wed 15 | 0 | 0.0 | 309 ms | 0 |
| Wed 18 | 0 | 0.0 | 161 ms | 0 |
| Wed 20 | 0 | 0.0 | 358 ms | 0 |
| Wed 22 | 0 | 0.0 | 230 ms | 0 |
| Thu 00 | 0 | 0.0 | 458 ms | 0 |
| Thu 02 | 0 | 0.0 | 302 ms | 0 |
| Thu 04 | 0 | 0.0 | 287 ms | 0 |
| Thu 06 | 0 | 0.0 | 63 ms | 0 |
| Thu 08 | 0 | 0.0 | 356 ms | 0 |
| Thu 11 | 0 | 0.0 | 141 ms | 0 |
| Thu 13 | 0 | 0.0 | 241 ms | 0 |
| Thu 15 | 0 | 0.0 | 632 ms | 0 |
| Thu 17 | 0 | 0.0 | 291 ms | 0 |
| Thu 19 | 0 | 0.0 | 144 ms | 0 |
| Thu 21 | 0 | 0.0 | 714 ms | 0 |
| Thu 23 | 0 | 0.0 | 190 ms | 0 |
| Fri 00 | 0 | 0.0 | 243 ms | 0 |
| Fri 02 | 0 | 0.0 | 628 ms | 0 |
| Fri 04 | 0 | 0.0 | 123 ms | 0 |
| Fri 06 | 0 | 0.0 | 205 ms | 0 |
| Fri 08 | 0 | 0.0 | 144 ms | 0 |
| Fri 10 | 0 | 0.0 | 150 ms | 0 |
| Fri 11 | 0 | 0.0 | 349 ms | 0 |
| Fri 12 | 0 | 0.0 | 346 ms | 0 |
| Fri 14 | 0 | 0.0 | 319 ms | 0 |
| Fri 16 | 0 | 0.0 | 146 ms | 0 |
| Fri 18 | 0 | 0.0 | 413 ms | 0 |
| Fri 19 | 0 | 0.0 | 761 ms | 0 |
| Fri 21 | 0 | 0.0 | 281 ms | 0 |
| Fri 23 | 0 | 0.0 | 90 ms | 0 |
| Sat 01 | 0 | 0.0 | 729 ms | 0 |
| Sat 03 | 0 | 0.0 | 148 ms | 0 |
| Sat 06 | 0 | 0.0 | 297 ms | 0 |
| Sat 07 | 0 | 0.0 | 78 ms | 0 |
| Sat 09 | 0 | 0.0 | 65 ms | 0 |
Reliability
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 9 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Fulcrum 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 Fulcrum yet. Outages of 10 minutes or more get their own page here.
Having trouble with Fulcrum?
One report per service every 10 minutes from this network. No account.
Follow Fulcrum
Get an email when Fulcrum goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Fulcrum alerts to Slack, Discord or a webhook — free.
About Fulcrum
We track Fulcrum (fulcrumapp.com) as part of the AI group. Revolutionize your field operations with AI-native Fulcrum Field Operations Management and field data collection platform.
Fulcrum publishes an official status page at status.fulcrumapp.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 282 ms average, 5–761 ms range across 17 successful checks.
Questions
Is Fulcrum down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Fulcrum last down?
We have not recorded a public Fulcrum incident since monitoring began 9 days ago.
What is Fulcrum's uptime?
From our own checks: 100% over 9 days of checks.
How fast does Fulcrum respond?
282 ms on average over the last 24 hours (5–761 ms).
Does Fulcrum have an official status page?
Yes, at https://status.fulcrumapp.com.
Fulcrum 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 AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Fulcrum here at once, the problem is on Fulcrum'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 Fulcrum. 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.