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 1 hr ago. Last stored result reached it in 1133 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 22 | 0 | 0.0 | 591 ms | 0 |
| Wed 00 | 0 | 0.0 | 586 ms | 0 |
| Wed 02 | 0 | 0.0 | 638 ms | 0 |
| Wed 04 | 0 | 0.0 | 546 ms | 0 |
| Wed 07 | 0 | 0.0 | 639 ms | 0 |
| Wed 09 | 0 | 0.0 | 626 ms | 0 |
| Wed 11 | 0 | 0.0 | 570 ms | 0 |
| Wed 13 | 0 | 0.0 | 564 ms | 0 |
| Wed 15 | 0 | 0.0 | 549 ms | 0 |
| Wed 18 | 0 | 0.0 | 621 ms | 0 |
| Wed 20 | 0 | 0.0 | 536 ms | 0 |
| Wed 22 | 0 | 0.0 | 577 ms | 0 |
| Thu 00 | 0 | 0.0 | 600 ms | 0 |
| Thu 02 | 0 | 0.0 | 656 ms | 0 |
| Thu 04 | 0 | 0.0 | 698 ms | 0 |
| Thu 06 | 0 | 0.0 | 607 ms | 0 |
| Thu 08 | 0 | 0.0 | 558 ms | 0 |
| Thu 11 | 0 | 0.0 | 576 ms | 0 |
| Thu 13 | 0 | 0.0 | 589 ms | 0 |
| Thu 15 | 0 | 0.0 | 582 ms | 0 |
| Thu 17 | 0 | 0.0 | 1106 ms | 0 |
| Thu 19 | 0 | 0.0 | 609 ms | 0 |
| Thu 21 | 0 | 0.0 | 1000 ms | 0 |
| Thu 23 | 0 | 0.0 | 570 ms | 0 |
| Fri 01 | 0 | 0.0 | 609 ms | 0 |
| Fri 03 | 0 | 0.0 | 607 ms | 0 |
| Fri 05 | 0 | 0.0 | 630 ms | 0 |
| Fri 07 | 0 | 0.0 | 575 ms | 0 |
| Fri 08 | 0 | 0.0 | 629 ms | 0 |
| Fri 10 | 0 | 0.0 | 659 ms | 0 |
| Fri 11 | 0 | 0.0 | 1301 ms | 0 |
| Fri 13 | 0 | 0.0 | 464 ms | 0 |
| Fri 15 | 0 | 0.0 | 530 ms | 0 |
| Fri 17 | 0 | 0.0 | 584 ms | 0 |
| Fri 19 | 0 | 0.0 | 652 ms | 0 |
| Fri 21 | 0 | 0.0 | 570 ms | 0 |
| Fri 23 | 0 | 0.0 | 587 ms | 0 |
| Sat 01 | 0 | 0.0 | 552 ms | 0 |
| Sat 03 | 0 | 0.0 | 516 ms | 0 |
| Sat 06 | 0 | 0.0 | 601 ms | 0 |
| Sat 08 | 0 | 0.0 | 589 ms | 0 |
| Sat 10 | 0 | 0.0 | 555 ms | 0 |
| Sat 12 | 0 | 0.0 | 611 ms | 0 |
| Sat 14 | 0 | 0.0 | 574 ms | 0 |
| Sat 17 | 0 | 0.0 | 522 ms | 0 |
| Sat 19 | 0 | 0.0 | 1129 ms | 0 |
| Sat 21 | 0 | 0.0 | 496 ms | 0 |
| Sun 00 | 0 | 0.0 | 1133 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 10 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Woodpecker.co 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 Woodpecker.co goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
We track Woodpecker.co (woodpecker.co) as part of the Productivity group. For businesses that do outbound. All you need for cold email and LinkedIn outreach in one place.
Woodpecker.co publishes an official status page at status.woodpecker.co; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 10 days of checks. No public incidents logged since monitoring began 10 days ago.
Response time over the last 24 hours: 646 ms average, 496–1133 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 Woodpecker.co incident since monitoring began 10 days ago.
From our own checks: 100% over 10 days of checks.
646 ms on average over the last 24 hours (496–1133 ms).
Yes, at https://status.woodpecker.co.
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 Woodpecker.co here at once, the problem is on Woodpecker.co'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 Woodpecker.co. 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.