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 27 min ago. Last stored result reached it in 184 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 147 ms | 0 |
| Mon 20 | 0 | 0.0 | 39 ms | 0 |
| Mon 22 | 0 | 0.0 | 262 ms | 0 |
| Tue 00 | 0 | 0.0 | 192 ms | 0 |
| Tue 02 | 0 | 0.0 | 155 ms | 0 |
| Tue 04 | 0 | 0.0 | 191 ms | 0 |
| Tue 06 | 0 | 0.0 | 175 ms | 0 |
| Tue 08 | 0 | 0.0 | 35 ms | 0 |
| Tue 10 | 0 | 0.0 | 238 ms | 0 |
| Tue 13 | 0 | 0.0 | 115 ms | 0 |
| Tue 15 | 0 | 0.0 | 148 ms | 0 |
| Tue 17 | 0 | 0.0 | 137 ms | 0 |
| Tue 19 | 0 | 0.0 | 333 ms | 0 |
| Tue 22 | 0 | 0.0 | 200 ms | 0 |
| Wed 00 | 0 | 0.0 | 202 ms | 0 |
| Wed 02 | 0 | 0.0 | 315 ms | 0 |
| Wed 04 | 0 | 0.0 | 317 ms | 0 |
| Wed 06 | 0 | 0.0 | 401 ms | 0 |
| Wed 09 | 0 | 0.0 | 133 ms | 0 |
| Wed 11 | 0 | 0.0 | 273 ms | 0 |
| Wed 13 | 0 | 0.0 | 186 ms | 0 |
| Wed 15 | 0 | 0.0 | 145 ms | 0 |
| Wed 17 | 0 | 0.0 | 109 ms | 0 |
| Wed 19 | 0 | 0.0 | 131 ms | 0 |
| Wed 21 | 0 | 0.0 | 138 ms | 0 |
| Thu 00 | 0 | 0.0 | 200 ms | 0 |
| Thu 02 | 0 | 0.0 | 181 ms | 0 |
| Thu 04 | 0 | 0.0 | 110 ms | 0 |
| Thu 06 | 0 | 0.0 | 205 ms | 0 |
| Thu 08 | 0 | 0.0 | 105 ms | 0 |
| Thu 10 | 0 | 0.0 | 149 ms | 0 |
| Thu 12 | 0 | 0.0 | 162 ms | 0 |
| Thu 14 | 0 | 0.0 | 120 ms | 0 |
| Thu 16 | 0 | 0.0 | 192 ms | 0 |
| Thu 18 | 0 | 0.0 | 155 ms | 0 |
| Thu 20 | 0 | 0.0 | 33 ms | 0 |
| Thu 22 | 0 | 0.0 | 212 ms | 0 |
| Thu 23 | 0 | 0.0 | 70 ms | 0 |
| Fri 01 | 0 | 0.0 | 177 ms | 0 |
| Fri 03 | 0 | 0.0 | 148 ms | 0 |
| Fri 05 | 0 | 0.0 | 132 ms | 0 |
| Fri 07 | 0 | 0.0 | 176 ms | 0 |
| Fri 09 | 0 | 0.0 | 257 ms | 0 |
| Fri 10 | 0 | 0.0 | 101 ms | 0 |
| Fri 11 | 0 | 0.0 | 86 ms | 0 |
| Fri 12 | 0 | 0.0 | 173 ms | 0 |
| Fri 14 | 0 | 0.0 | 130 ms | 0 |
| Fri 16 | 0 | 0.0 | 184 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Fernand 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 Fernand goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Fernand alerts to Slack, Discord or a webhook — free.
Fernand is listed in our AI category and checked at getfernand.com. Respond on every channel, build a knowledge base, and put your AI Agent on the front line. Sync with your team, close the loop with customers, and ship a product people love.
Fernand publishes an official status page at status.getfernand.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 149 ms average, 33–257 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Fernand incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
149 ms on average over the last 24 hours (33–257 ms).
Yes, at https://status.getfernand.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 Fernand here at once, the problem is on Fernand'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 Fernand. 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.