User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 14 min ago. Last stored result reached it in 183 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 241 ms | 0 |
| Tue 02 | 0 | 0.0 | 451 ms | 0 |
| Tue 05 | 0 | 0.0 | 332 ms | 0 |
| Tue 07 | 0 | 0.0 | 204 ms | 0 |
| Tue 09 | 0 | 0.0 | 397 ms | 0 |
| Tue 11 | 0 | 0.0 | 160 ms | 0 |
| Tue 13 | 0 | 0.0 | 570 ms | 0 |
| Tue 15 | 0 | 0.0 | 372 ms | 0 |
| Tue 18 | 0 | 0.0 | 540 ms | 0 |
| Tue 20 | 0 | 0.0 | 574 ms | 0 |
| Tue 22 | 0 | 0.0 | 264 ms | 0 |
| Wed 00 | 0 | 0.0 | 487 ms | 0 |
| Wed 03 | 0 | 0.0 | 197 ms | 0 |
| Wed 05 | 0 | 0.0 | 527 ms | 0 |
| Wed 07 | 0 | 0.0 | 178 ms | 0 |
| Wed 09 | 0 | 0.0 | 746 ms | 0 |
| Wed 12 | 0 | 0.0 | 501 ms | 0 |
| Wed 14 | 0 | 0.0 | 480 ms | 0 |
| Wed 16 | 0 | 0.0 | 577 ms | 0 |
| Wed 18 | 0 | 0.0 | 575 ms | 0 |
| Wed 20 | 0 | 0.0 | 193 ms | 0 |
| Wed 22 | 0 | 0.0 | 395 ms | 0 |
| Thu 00 | 0 | 0.0 | 483 ms | 0 |
| Thu 03 | 0 | 0.0 | 547 ms | 0 |
| Thu 05 | 0 | 0.0 | 315 ms | 0 |
| Thu 07 | 0 | 0.0 | 531 ms | 0 |
| Thu 09 | 0 | 0.0 | 495 ms | 0 |
| Thu 11 | 0 | 0.0 | 194 ms | 0 |
| Thu 13 | 0 | 0.0 | 489 ms | 0 |
| Thu 15 | 0 | 0.0 | 262 ms | 0 |
| Thu 17 | 0 | 0.0 | 266 ms | 0 |
| Thu 19 | 0 | 0.0 | 219 ms | 0 |
| Thu 21 | 0 | 0.0 | 459 ms | 0 |
| Thu 23 | 0 | 0.0 | 481 ms | 0 |
| Fri 01 | 0 | 0.0 | 198 ms | 0 |
| Fri 03 | 0 | 0.0 | 582 ms | 0 |
| Fri 05 | 0 | 0.0 | 221 ms | 0 |
| Fri 07 | 0 | 0.0 | 482 ms | 0 |
| Fri 09 | 0 | 0.0 | 215 ms | 0 |
| Fri 11 | 0 | 0.0 | 879 ms | 0 |
| Fri 13 | 0 | 0.0 | 796 ms | 0 |
| Fri 15 | 0 | 0.0 | 663 ms | 0 |
| Fri 17 | 0 | 0.0 | 237 ms | 0 |
| Fri 19 | 0 | 0.0 | 825 ms | 0 |
| Fri 20 | 0 | 0.0 | 165 ms | 0 |
| Fri 22 | 0 | 0.0 | 494 ms | 0 |
| Fri 23 | 0 | 0.0 | 545 ms | 0 |
| Sat 01 | 0 | 0.0 | 183 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 Birdie 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 Birdie goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Birdie alerts to Slack, Discord or a webhook — free.
Birdie is listed in our Productivity category and checked at birdie.so. Ask customers to show you the issue. Birdie captures screen recordings with repro steps, console logs and network data, straight into your helpdesk.
Birdie publishes an official status page at status.birdie.so; when we can read it, its incident level is folded into the status shown here.
Typical issues with productivity services: files not syncing, editors not loading, and sign-in problems.
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: 479 ms average, 165–879 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 Birdie incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
479 ms on average over the last 24 hours (165–879 ms).
Yes, at https://status.birdie.so.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Birdie here at once, the problem is on Birdie'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 Birdie. 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.