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 2 hr ago. Last stored result reached it in 509 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 15:30 | 0 | 0.0 | 663 ms | 0 |
| 17:00 | 0 | 0.0 | 175 ms | 0 |
| 17:30 | 0 | 0.0 | 298 ms | 0 |
| 19:00 | 0 | 0.0 | 825 ms | 0 |
| 20:45 | 0 | 0.0 | 165 ms | 0 |
| 22:30 | 0 | 0.0 | 494 ms | 0 |
| 23:30 | 0 | 0.0 | 545 ms | 0 |
| 01:30 | 0 | 0.0 | 183 ms | 0 |
| 03:30 | 0 | 0.0 | 238 ms | 0 |
| 05:45 | 0 | 0.0 | 497 ms | 0 |
| 07:45 | 0 | 0.0 | 576 ms | 0 |
| 09:45 | 0 | 0.0 | 215 ms | 0 |
| 10:00 | 0 | 0.0 | 523 ms | 0 |
| 12:30 | 0 | 0.0 | 509 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 9 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 438 ms average, 165–839 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 9 days ago.
From our own checks: 100% over 9 days of checks.
438 ms on average over the last 24 hours (165–839 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.