User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
franklincovey.com · Cloud & developer
Is FranklinCovey 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 → franklincovey.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 484 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 |
|---|---|---|---|---|
| Wed 03 | 0 | 0.0 | 631 ms | 0 |
| Wed 05 | 0 | 0.0 | 554 ms | 0 |
| Wed 08 | 0 | 0.0 | 538 ms | 0 |
| Wed 10 | 0 | 0.0 | 762 ms | 0 |
| Wed 12 | 0 | 0.0 | 590 ms | 0 |
| Wed 14 | 0 | 0.0 | 611 ms | 0 |
| Wed 16 | 0 | 0.0 | 606 ms | 0 |
| Wed 18 | 0 | 0.0 | 650 ms | 0 |
| Wed 21 | 0 | 0.0 | 526 ms | 0 |
| Wed 23 | 0 | 0.0 | 614 ms | 0 |
| Thu 01 | 0 | 0.0 | 689 ms | 0 |
| Thu 03 | 0 | 0.0 | 609 ms | 0 |
| Thu 05 | 0 | 0.0 | 676 ms | 0 |
| Thu 07 | 0 | 0.0 | 570 ms | 0 |
| Thu 09 | 0 | 0.0 | 493 ms | 0 |
| Thu 11 | 0 | 0.0 | 624 ms | 0 |
| Thu 13 | 0 | 0.0 | 579 ms | 0 |
| Thu 15 | 0 | 0.0 | 661 ms | 0 |
| Thu 17 | 0 | 0.0 | 481 ms | 0 |
| Thu 18 | 0 | 0.0 | 553 ms | 0 |
| Thu 21 | 0 | 0.0 | 865 ms | 0 |
| Thu 22 | 0 | 0.0 | 685 ms | 0 |
| Fri 00 | 0 | 0.0 | 638 ms | 0 |
| Fri 03 | 0 | 0.0 | 538 ms | 0 |
| Fri 05 | 0 | 0.0 | 939 ms | 0 |
| Fri 07 | 0 | 0.0 | 706 ms | 0 |
| Fri 09 | 0 | 0.0 | 662 ms | 0 |
| Fri 10 | 0 | 0.0 | 570 ms | 0 |
| Fri 12 | 0 | 0.0 | 524 ms | 0 |
| Fri 14 | 0 | 0.0 | 638 ms | 0 |
| Fri 16 | 0 | 0.0 | 592 ms | 0 |
| Fri 18 | 0 | 0.0 | 682 ms | 0 |
| Fri 20 | 0 | 0.0 | 735 ms | 0 |
| Fri 22 | 0 | 0.0 | 816 ms | 0 |
| Sat 00 | 0 | 0.0 | 573 ms | 0 |
| Sat 02 | 0 | 0.0 | 485 ms | 0 |
| Sat 04 | 0 | 0.0 | 564 ms | 0 |
| Sat 06 | 0 | 0.0 | 755 ms | 0 |
| Sat 07 | 0 | 0.0 | 705 ms | 0 |
| Sat 10 | 0 | 0.0 | 571 ms | 0 |
| Sat 12 | 0 | 0.0 | 736 ms | 0 |
| Sat 14 | 0 | 0.0 | 847 ms | 0 |
| Sat 17 | 0 | 0.0 | 831 ms | 0 |
| Sat 19 | 0 | 0.0 | 623 ms | 0 |
| Sat 21 | 0 | 0.0 | 618 ms | 0 |
| Sat 22 | 0 | 0.0 | 542 ms | 0 |
| Sun 00 | 0 | 0.0 | 573 ms | 0 |
| Sun 02 | 0 | 0.0 | 484 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 10 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live FranklinCovey 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 FranklinCovey yet. Outages of 10 minutes or more get their own page here.
Having trouble with FranklinCovey?
One report per service every 10 minutes from this network. No account.
Follow FranklinCovey
Get an email when FranklinCovey goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
About FranklinCovey
We track FranklinCovey (franklincovey.com) as part of the Cloud & developer group. FranklinCovey is a global leadership and organizational performance partner. We give strategy the human edge™ and help organizations develop exceptional leaders at every level, build high‑trust, winning cultures, and execute as united teams to achieve breakthrough business results in more than 160 countries.
FranklinCovey publishes an official status page at status.franklincovey.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 10 days of checks. No public incidents logged since monitoring began 10 days ago.
Response time over the last 24 hours: 676 ms average, 484–987 ms range across 12 successful checks.
Questions
Is FranklinCovey down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was FranklinCovey last down?
We have not recorded a public FranklinCovey incident since monitoring began 10 days ago.
What is FranklinCovey's uptime?
From our own checks: 100% over 10 days of checks.
How fast does FranklinCovey respond?
676 ms on average over the last 24 hours (484–987 ms).
Does FranklinCovey have an official status page?
Yes, at https://status.franklincovey.com.
FranklinCovey 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 FranklinCovey here at once, the problem is on FranklinCovey'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 FranklinCovey. 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.