User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is project b down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → project-b.dev—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 227 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 203 ms | 0 |
| Mon 17 | 0 | 0.0 | 225 ms | 0 |
| Mon 18 | 0 | 0.0 | 111 ms | 0 |
| Mon 20 | 0 | 0.0 | 396 ms | 0 |
| Mon 22 | 0 | 0.0 | 265 ms | 0 |
| Tue 00 | 0 | 0.0 | 205 ms | 0 |
| Tue 02 | 0 | 0.0 | 181 ms | 0 |
| Tue 04 | 0 | 0.0 | 187 ms | 0 |
| Tue 06 | 0 | 0.0 | 117 ms | 0 |
| Tue 08 | 0 | 0.0 | 213 ms | 0 |
| Tue 10 | 0 | 0.0 | 237 ms | 0 |
| Tue 12 | 0 | 0.0 | 298 ms | 0 |
| Tue 15 | 0 | 0.0 | 207 ms | 0 |
| Tue 17 | 0 | 0.0 | 259 ms | 0 |
| Tue 19 | 0 | 0.0 | 114 ms | 0 |
| Tue 22 | 0 | 0.0 | 215 ms | 0 |
| Wed 00 | 0 | 0.0 | 292 ms | 0 |
| Wed 02 | 0 | 0.0 | 330 ms | 0 |
| Wed 04 | 0 | 0.0 | 213 ms | 0 |
| Wed 06 | 0 | 0.0 | 207 ms | 0 |
| Wed 09 | 0 | 0.0 | 229 ms | 0 |
| Wed 11 | 0 | 0.0 | 317 ms | 0 |
| Wed 13 | 0 | 0.0 | 233 ms | 0 |
| Wed 15 | 0 | 0.0 | 342 ms | 0 |
| Wed 17 | 0 | 0.0 | 208 ms | 0 |
| Wed 20 | 0 | 0.0 | 283 ms | 0 |
| Wed 22 | 0 | 0.0 | 165 ms | 0 |
| Thu 00 | 0 | 0.0 | 122 ms | 0 |
| Thu 02 | 0 | 0.0 | 222 ms | 0 |
| Thu 04 | 0 | 0.0 | 197 ms | 0 |
| Thu 06 | 0 | 0.0 | 347 ms | 0 |
| Thu 08 | 0 | 0.0 | 192 ms | 0 |
| Thu 10 | 0 | 0.0 | 224 ms | 0 |
| Thu 12 | 0 | 0.0 | 134 ms | 0 |
| Thu 14 | 0 | 0.0 | 212 ms | 0 |
| Thu 17 | 0 | 0.0 | 443 ms | 0 |
| Thu 19 | 0 | 0.0 | 241 ms | 0 |
| Thu 21 | 0 | 0.0 | 319 ms | 0 |
| Thu 23 | 0 | 0.0 | 220 ms | 0 |
| Fri 01 | 0 | 0.0 | 309 ms | 0 |
| Fri 03 | 0 | 0.0 | 151 ms | 0 |
| Fri 05 | 0 | 0.0 | 310 ms | 0 |
| Fri 08 | 0 | 0.0 | 289 ms | 0 |
| Fri 10 | 0 | 0.0 | 241 ms | 0 |
| Fri 11 | 0 | 0.0 | 168 ms | 0 |
| Fri 13 | 0 | 0.0 | 142 ms | 0 |
| Fri 15 | 0 | 0.0 | 479 ms | 0 |
| Fri 17 | 0 | 0.0 | 227 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live project b badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for project b yet. Outages of 10 minutes or more get their own page here.
Having trouble with project b?
One report per service every 10 minutes from this network. No account.
Follow project b
Get an email when project b goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send project b alerts to Slack, Discord or a webhook — free.
About project b
We track project b (project-b.dev) as part of the Productivity group. project b. übernimmt deine Lohnabrechnung oder macht sie effizienter. Digital, zuverlässig und mit echten Lohnprofis. Für Unternehmen, Lohnbüros und Steuerberater.
project b publishes an official status page at status.project-b.dev; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 262 ms average, 142–479 ms range across 13 successful checks.
Questions
Is project b down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was project b last down?
We have not recorded a public project b incident since monitoring began 7 days ago.
What is project b's uptime?
From our own checks: 100% over 7 days of checks.
How fast does project b respond?
262 ms on average over the last 24 hours (142–479 ms).
Does project b have an official status page?
Yes, at https://status.project-b.dev.
project b not working for me but the status is fine. What now?
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 project b here at once, the problem is on project b'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 project b. 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.