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 15 min ago. Last stored result reached it in 78 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 186 ms | 0 |
| Tue 01 | 0 | 0.0 | 154 ms | 0 |
| Tue 03 | 0 | 0.0 | 141 ms | 0 |
| Tue 05 | 0 | 0.0 | 105 ms | 0 |
| Tue 07 | 0 | 0.0 | 114 ms | 0 |
| Tue 09 | 0 | 0.0 | 189 ms | 0 |
| Tue 11 | 0 | 0.0 | 132 ms | 0 |
| Tue 13 | 0 | 0.0 | 182 ms | 0 |
| Tue 16 | 0 | 0.0 | 125 ms | 0 |
| Tue 18 | 0 | 0.0 | 138 ms | 0 |
| Tue 20 | 0 | 0.0 | 203 ms | 0 |
| Tue 22 | 0 | 0.0 | 180 ms | 0 |
| Wed 01 | 0 | 0.0 | 92 ms | 0 |
| Wed 03 | 0 | 0.0 | 152 ms | 0 |
| Wed 05 | 0 | 0.0 | 101 ms | 0 |
| Wed 07 | 0 | 0.0 | 131 ms | 0 |
| Wed 10 | 0 | 0.0 | 206 ms | 0 |
| Wed 12 | 0 | 0.0 | 329 ms | 0 |
| Wed 14 | 0 | 0.0 | 203 ms | 0 |
| Wed 16 | 0 | 0.0 | 207 ms | 0 |
| Wed 18 | 0 | 0.0 | 161 ms | 0 |
| Wed 20 | 0 | 0.0 | 109 ms | 0 |
| Wed 23 | 0 | 0.0 | 202 ms | 0 |
| Thu 01 | 0 | 0.0 | 153 ms | 0 |
| Thu 03 | 0 | 0.0 | 218 ms | 0 |
| Thu 05 | 0 | 0.0 | 238 ms | 0 |
| Thu 07 | 0 | 0.0 | 137 ms | 0 |
| Thu 09 | 0 | 0.0 | 138 ms | 0 |
| Thu 11 | 0 | 0.0 | 123 ms | 0 |
| Thu 13 | 0 | 0.0 | 334 ms | 0 |
| Thu 15 | 0 | 0.0 | 328 ms | 0 |
| Thu 17 | 0 | 0.0 | 266 ms | 0 |
| Thu 18 | 0 | 0.0 | 113 ms | 0 |
| Thu 20 | 0 | 0.0 | 342 ms | 0 |
| Thu 22 | 0 | 0.0 | 119 ms | 0 |
| Fri 00 | 0 | 0.0 | 241 ms | 0 |
| Fri 02 | 0 | 0.0 | 174 ms | 0 |
| Fri 04 | 0 | 0.0 | 135 ms | 0 |
| Fri 07 | 0 | 0.0 | 115 ms | 0 |
| Fri 09 | 0 | 0.0 | 334 ms | 0 |
| Fri 10 | 0 | 0.0 | 109 ms | 0 |
| Fri 11 | 0 | 0.0 | 151 ms | 0 |
| Fri 13 | 0 | 0.0 | 136 ms | 0 |
| Fri 15 | 0 | 0.0 | 181 ms | 0 |
| Fri 17 | 0 | 0.0 | 268 ms | 0 |
| Fri 19 | 0 | 0.0 | 152 ms | 0 |
| Fri 20 | 0 | 0.0 | 117 ms | 0 |
| Fri 21 | 0 | 0.0 | 257 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 Birdeye 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 Birdeye goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Birdeye alerts to Slack, Discord or a webhook — free.
Birdeye is listed in our AI category and checked at birdeye.com. Birdeye builds AI coworkers for multi-location brands. Jay, Myna and Robin win AI visibility, convert demand and keep experience consistent at every location.
Birdeye publishes an official status page at status.birdeye.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: 180 ms average, 78–373 ms range across 18 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Birdeye incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
180 ms on average over the last 24 hours (78–373 ms).
Yes, at https://status.birdeye.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 Birdeye here at once, the problem is on Birdeye'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 Birdeye. 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.