User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 2 hr ago. Last stored result reached it in 152 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 08 | 0 | 0.0 | 143 ms | 0 |
| Tue 10 | 0 | 0.0 | 211 ms | 0 |
| Tue 12 | 0 | 0.0 | 64 ms | 0 |
| Tue 15 | 0 | 0.0 | 141 ms | 0 |
| Tue 17 | 0 | 0.0 | 125 ms | 0 |
| Tue 19 | 0 | 0.0 | 59 ms | 0 |
| Tue 21 | 0 | 0.0 | 78 ms | 0 |
| Wed 00 | 0 | 0.0 | 231 ms | 0 |
| Wed 02 | 0 | 0.0 | 49 ms | 0 |
| Wed 04 | 0 | 0.0 | 90 ms | 0 |
| Wed 06 | 0 | 0.0 | 147 ms | 0 |
| Wed 09 | 0 | 0.0 | 117 ms | 0 |
| Wed 11 | 0 | 0.0 | 141 ms | 0 |
| Wed 13 | 0 | 0.0 | 140 ms | 0 |
| Wed 15 | 0 | 0.0 | 158 ms | 0 |
| Wed 17 | 0 | 0.0 | 123 ms | 0 |
| Wed 19 | 0 | 0.0 | 146 ms | 0 |
| Wed 22 | 0 | 0.0 | 60 ms | 0 |
| Thu 00 | 0 | 0.0 | 121 ms | 0 |
| Thu 02 | 0 | 0.0 | 183 ms | 0 |
| Thu 04 | 0 | 0.0 | 202 ms | 0 |
| Thu 06 | 0 | 0.0 | 154 ms | 0 |
| Thu 08 | 0 | 0.0 | 141 ms | 0 |
| Thu 10 | 0 | 0.0 | 49 ms | 0 |
| Thu 12 | 0 | 0.0 | 137 ms | 0 |
| Thu 14 | 0 | 0.0 | 166 ms | 0 |
| Thu 16 | 0 | 0.0 | 90 ms | 0 |
| Thu 18 | 0 | 0.0 | 147 ms | 0 |
| Thu 21 | 0 | 0.0 | 121 ms | 0 |
| Thu 23 | 0 | 0.0 | 137 ms | 0 |
| Fri 01 | 0 | 0.0 | 73 ms | 0 |
| Fri 03 | 0 | 0.0 | 116 ms | 0 |
| Fri 05 | 0 | 0.0 | 137 ms | 0 |
| Fri 07 | 0 | 0.0 | 151 ms | 0 |
| Fri 09 | 0 | 0.0 | 87 ms | 0 |
| Fri 10 | 0 | 0.0 | 69 ms | 0 |
| Fri 11 | 0 | 0.0 | 53 ms | 0 |
| Fri 12 | 0 | 0.0 | 153 ms | 0 |
| Fri 14 | 0 | 0.0 | 132 ms | 0 |
| Fri 16 | 0 | 0.0 | 179 ms | 0 |
| Fri 17 | 0 | 0.0 | 167 ms | 0 |
| Fri 19 | 0 | 0.0 | 102 ms | 0 |
| Fri 21 | 0 | 0.0 | 160 ms | 0 |
| Fri 23 | 0 | 0.0 | 74 ms | 0 |
| Sat 01 | 0 | 0.0 | 102 ms | 0 |
| Sat 03 | 0 | 0.0 | 62 ms | 0 |
| Sat 04 | 0 | 0.0 | 185 ms | 0 |
| Sat 06 | 0 | 0.0 | 152 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 FreedomGPT 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 FreedomGPT goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send FreedomGPT alerts to Slack, Discord or a webhook — free.
We track FreedomGPT (freedomgpt.com) as part of the AI group. Explore uncensored AI and multiple models in one app. Start free, compare answers, and check one subscription's model access and usage limits.
FreedomGPT publishes an official status page at status.freedomgpt.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 119 ms average, 53–185 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public FreedomGPT incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
119 ms on average over the last 24 hours (53–185 ms).
Yes, at https://status.freedomgpt.com.
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 FreedomGPT here at once, the problem is on FreedomGPT'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 FreedomGPT. 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.