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 232 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 194 ms | 0 |
| Mon 20 | 0 | 0.0 | 117 ms | 0 |
| Mon 22 | 0 | 0.0 | 221 ms | 0 |
| Tue 00 | 0 | 0.0 | 207 ms | 0 |
| Tue 02 | 0 | 0.0 | 184 ms | 0 |
| Tue 04 | 0 | 0.0 | 242 ms | 0 |
| Tue 06 | 0 | 0.0 | 230 ms | 0 |
| Tue 08 | 0 | 0.0 | 126 ms | 0 |
| Tue 11 | 0 | 0.0 | 232 ms | 0 |
| Tue 13 | 0 | 0.0 | 126 ms | 0 |
| Tue 15 | 0 | 0.0 | 189 ms | 0 |
| Tue 17 | 0 | 0.0 | 375 ms | 0 |
| Tue 19 | 0 | 0.0 | 217 ms | 0 |
| Tue 22 | 0 | 0.0 | 155 ms | 0 |
| Wed 00 | 0 | 0.0 | 130 ms | 0 |
| Wed 02 | 0 | 0.0 | 196 ms | 0 |
| Wed 04 | 0 | 0.0 | 260 ms | 0 |
| Wed 07 | 0 | 0.0 | 211 ms | 0 |
| Wed 09 | 0 | 0.0 | 154 ms | 0 |
| Wed 11 | 0 | 0.0 | 212 ms | 0 |
| Wed 13 | 0 | 0.0 | 229 ms | 0 |
| Wed 15 | 0 | 0.0 | 199 ms | 0 |
| Wed 17 | 0 | 0.0 | 184 ms | 0 |
| Wed 20 | 0 | 0.0 | 298 ms | 0 |
| Wed 22 | 0 | 0.0 | 382 ms | 0 |
| Thu 00 | 0 | 0.0 | 320 ms | 0 |
| Thu 02 | 0 | 0.0 | 284 ms | 0 |
| Thu 04 | 0 | 0.0 | 190 ms | 0 |
| Thu 06 | 0 | 0.0 | 223 ms | 0 |
| Thu 08 | 0 | 0.0 | 282 ms | 0 |
| Thu 10 | 0 | 0.0 | 124 ms | 0 |
| Thu 12 | 0 | 0.0 | 195 ms | 0 |
| Thu 14 | 0 | 0.0 | 280 ms | 0 |
| Thu 16 | 0 | 0.0 | 206 ms | 0 |
| Thu 19 | 0 | 0.0 | 240 ms | 0 |
| Thu 21 | 0 | 0.0 | 125 ms | 0 |
| Thu 23 | 0 | 0.0 | 237 ms | 0 |
| Fri 01 | 0 | 0.0 | 432 ms | 0 |
| Fri 03 | 0 | 0.0 | 177 ms | 0 |
| Fri 05 | 0 | 0.0 | 128 ms | 0 |
| Fri 07 | 0 | 0.0 | 312 ms | 0 |
| Fri 09 | 0 | 0.0 | 129 ms | 0 |
| Fri 10 | 0 | 0.0 | 154 ms | 0 |
| Fri 11 | 0 | 0.0 | 90 ms | 0 |
| Fri 12 | 0 | 0.0 | 122 ms | 0 |
| Fri 14 | 0 | 0.0 | 129 ms | 0 |
| Fri 16 | 0 | 0.0 | 257 ms | 0 |
| Fri 17 | 0 | 0.0 | 232 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 Crossbeam 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 Crossbeam goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Crossbeam alerts to Slack, Discord or a webhook — free.
We track Crossbeam (crossbeam.com) as part of the Productivity group. Discover how Crossbeam's Ecosystem Revenue Platform empowers sales, marketing, and partnerships to unlock new growth opportunities, close deals faster, and drive revenue with actionable ecosystem insights.
Crossbeam publishes an official status page at status.crossbeam.com; when we can read it, its incident level is folded into the status shown here.
Common problems for 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: 197 ms average, 90–432 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 Crossbeam incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
197 ms on average over the last 24 hours (90–432 ms).
Yes, at https://status.crossbeam.com.
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 Crossbeam here at once, the problem is on Crossbeam'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 Crossbeam. 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.