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 18 min ago. Last stored result reached it in 92 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 156 ms | 0 |
| Mon 15 | 0 | 0.0 | 96 ms | 0 |
| Mon 17 | 0 | 0.0 | 164 ms | 0 |
| Mon 19 | 0 | 0.0 | 150 ms | 0 |
| Mon 22 | 0 | 0.0 | 206 ms | 0 |
| Tue 00 | 0 | 0.0 | 187 ms | 0 |
| Tue 02 | 0 | 0.0 | 161 ms | 0 |
| Tue 04 | 0 | 0.0 | 122 ms | 0 |
| Tue 06 | 0 | 0.0 | 111 ms | 0 |
| Tue 08 | 0 | 0.0 | 79 ms | 0 |
| Tue 10 | 0 | 0.0 | 228 ms | 0 |
| Tue 12 | 0 | 0.0 | 133 ms | 0 |
| Tue 15 | 0 | 0.0 | 165 ms | 0 |
| Tue 17 | 0 | 0.0 | 82 ms | 0 |
| Tue 19 | 0 | 0.0 | 74 ms | 0 |
| Tue 21 | 0 | 0.0 | 214 ms | 0 |
| Wed 00 | 0 | 0.0 | 116 ms | 0 |
| Wed 02 | 0 | 0.0 | 141 ms | 0 |
| Wed 04 | 0 | 0.0 | 198 ms | 0 |
| Wed 06 | 0 | 0.0 | 96 ms | 0 |
| Wed 09 | 0 | 0.0 | 140 ms | 0 |
| Wed 11 | 0 | 0.0 | 87 ms | 0 |
| Wed 13 | 0 | 0.0 | 180 ms | 0 |
| Wed 15 | 0 | 0.0 | 63 ms | 0 |
| Wed 17 | 0 | 0.0 | 143 ms | 0 |
| Wed 19 | 0 | 0.0 | 109 ms | 0 |
| Wed 22 | 0 | 0.0 | 129 ms | 0 |
| Thu 00 | 0 | 0.0 | 113 ms | 0 |
| Thu 02 | 0 | 0.0 | 295 ms | 0 |
| Thu 04 | 0 | 0.0 | 165 ms | 0 |
| Thu 06 | 0 | 0.0 | 151 ms | 0 |
| Thu 08 | 0 | 0.0 | 270 ms | 0 |
| Thu 10 | 0 | 0.0 | 145 ms | 0 |
| Thu 12 | 0 | 0.0 | 139 ms | 0 |
| Thu 14 | 0 | 0.0 | 148 ms | 0 |
| Thu 16 | 0 | 0.0 | 111 ms | 0 |
| Thu 18 | 0 | 0.0 | 110 ms | 0 |
| Thu 20 | 0 | 0.0 | 76 ms | 0 |
| Thu 22 | 0 | 0.0 | 180 ms | 0 |
| Fri 00 | 0 | 0.0 | 91 ms | 0 |
| Fri 03 | 0 | 0.0 | 100 ms | 0 |
| Fri 05 | 0 | 0.0 | 128 ms | 0 |
| Fri 07 | 0 | 0.0 | 53 ms | 0 |
| Fri 09 | 0 | 0.0 | 75 ms | 0 |
| Fri 10 | 0 | 0.0 | 138 ms | 0 |
| Fri 11 | 0 | 0.0 | 111 ms | 0 |
| Fri 13 | 0 | 0.0 | 80 ms | 0 |
| Fri 15 | 0 | 0.0 | 92 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 Featurebase 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 Featurebase goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Featurebase alerts to Slack, Discord or a webhook — free.
Featurebase is listed in our AI category and checked at featurebase.app. Support customers from live chat, email, Slack, and more. Let AI resolve repetitive questions and surface the product & customer signals for your team to act on.
Featurebase publishes an official status page at status.featurebase.app; 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: 104 ms average, 53–180 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Featurebase incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
104 ms on average over the last 24 hours (53–180 ms).
Yes, at https://status.featurebase.app.
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 Featurebase here at once, the problem is on Featurebase'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 Featurebase. 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.