User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 718 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 550 ms | 0 |
| Mon 14 | 0 | 0.0 | 721 ms | 0 |
| Mon 17 | 0 | 0.0 | 309 ms | 0 |
| Mon 19 | 0 | 0.0 | 291 ms | 0 |
| Mon 21 | 0 | 0.0 | 252 ms | 0 |
| Mon 23 | 0 | 0.0 | 517 ms | 0 |
| Tue 01 | 0 | 0.0 | 380 ms | 0 |
| Tue 03 | 0 | 0.0 | 628 ms | 0 |
| Tue 05 | 0 | 0.0 | 323 ms | 0 |
| Tue 07 | 0 | 0.0 | 296 ms | 0 |
| Tue 09 | 0 | 0.0 | 483 ms | 0 |
| Tue 12 | 0 | 0.0 | 542 ms | 0 |
| Tue 14 | 0 | 0.0 | 857 ms | 0 |
| Tue 16 | 0 | 0.0 | 457 ms | 0 |
| Tue 18 | 0 | 0.0 | 191 ms | 0 |
| Tue 20 | 0 | 0.0 | 499 ms | 0 |
| Tue 23 | 0 | 0.0 | 416 ms | 0 |
| Wed 01 | 0 | 0.0 | 400 ms | 0 |
| Wed 03 | 0 | 0.0 | 446 ms | 0 |
| Wed 05 | 0 | 0.0 | 396 ms | 0 |
| Wed 08 | 0 | 0.0 | 467 ms | 0 |
| Wed 10 | 0 | 0.0 | 498 ms | 0 |
| Wed 12 | 0 | 0.0 | 186 ms | 0 |
| Wed 14 | 0 | 0.0 | 760 ms | 0 |
| Wed 16 | 0 | 0.0 | 239 ms | 0 |
| Wed 18 | 0 | 0.0 | 609 ms | 0 |
| Wed 21 | 0 | 0.0 | 540 ms | 0 |
| Wed 23 | 0 | 0.0 | 501 ms | 0 |
| Thu 01 | 0 | 0.0 | 410 ms | 0 |
| Thu 03 | 0 | 0.0 | 436 ms | 0 |
| Thu 05 | 0 | 0.0 | 511 ms | 0 |
| Thu 07 | 0 | 0.0 | 365 ms | 0 |
| Thu 09 | 0 | 0.0 | 636 ms | 0 |
| Thu 11 | 0 | 0.0 | 710 ms | 0 |
| Thu 13 | 0 | 0.0 | 296 ms | 0 |
| Thu 15 | 0 | 0.0 | 332 ms | 0 |
| Thu 17 | 0 | 0.0 | 205 ms | 0 |
| Thu 20 | 0 | 0.0 | 464 ms | 0 |
| Thu 22 | 0 | 0.0 | 419 ms | 0 |
| Fri 00 | 0 | 0.0 | 727 ms | 0 |
| Fri 02 | 0 | 0.0 | 629 ms | 0 |
| Fri 05 | 0 | 0.0 | 332 ms | 0 |
| Fri 07 | 0 | 0.0 | 450 ms | 0 |
| Fri 09 | 0 | 0.0 | 350 ms | 0 |
| Fri 11 | 0 | 0.0 | 364 ms | 0 |
| Fri 13 | 0 | 0.0 | 416 ms | 0 |
| Fri 15 | 0 | 0.0 | 520 ms | 0 |
| Fri 16 | 0 | 0.0 | 718 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.
No outages on record for Figure yet. Outages of 10 minutes or more get their own page here.
Historical breaches, not a live security alert. This does not indicate a current outage.
Data from Have I Been Pwned · CC BY 4.0
Breach date: · 967,178 accounts
Data exposed: Dates of birth, Email addresses, Names, Phone numbers, Physical addresses
One report per service every 10 minutes from this network. No account.
Get an email when Figure goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Figure alerts to Slack, Discord or a webhook — free.
Figure is listed in our Productivity category and checked at figure.com. See how a Home Equity Line of Credit with Figure can help you plan a home renovation project, consolidate high-interest debt, or fund your dream vacation!
Figure publishes an official status page at status.figure.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
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: 486 ms average, 205–846 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 Figure incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
486 ms on average over the last 24 hours (205–846 ms).
Yes, at https://status.figure.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Figure here at once, the problem is on Figure'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 Figure. 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.