User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is Fullview 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 → fullview.io—
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 44 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 12 | 0 | 0.0 | 49 ms | 0 |
| Mon 14 | 0 | 0.0 | 67 ms | 0 |
| Mon 17 | 0 | 0.0 | 63 ms | 0 |
| Mon 19 | 0 | 0.0 | 70 ms | 0 |
| Mon 21 | 0 | 0.0 | 40 ms | 0 |
| Mon 23 | 0 | 0.0 | 80 ms | 0 |
| Tue 01 | 0 | 0.0 | 79 ms | 0 |
| Tue 03 | 0 | 0.0 | 56 ms | 0 |
| Tue 05 | 0 | 0.0 | 72 ms | 0 |
| Tue 07 | 0 | 0.0 | 59 ms | 0 |
| Tue 09 | 0 | 0.0 | 56 ms | 0 |
| Tue 12 | 0 | 0.0 | 76 ms | 0 |
| Tue 14 | 0 | 0.0 | 50 ms | 0 |
| Tue 16 | 0 | 0.0 | 43 ms | 0 |
| Tue 18 | 0 | 0.0 | 74 ms | 0 |
| Tue 21 | 0 | 0.0 | 30 ms | 0 |
| Tue 23 | 0 | 0.0 | 72 ms | 0 |
| Wed 01 | 0 | 0.0 | 76 ms | 0 |
| Wed 03 | 0 | 0.0 | 59 ms | 0 |
| Wed 05 | 0 | 0.0 | 93 ms | 0 |
| Wed 08 | 0 | 0.0 | 31 ms | 0 |
| Wed 10 | 0 | 0.0 | 107 ms | 0 |
| Wed 12 | 0 | 0.0 | 56 ms | 0 |
| Wed 14 | 0 | 0.0 | 34 ms | 0 |
| Wed 16 | 0 | 0.0 | 133 ms | 0 |
| Wed 18 | 0 | 0.0 | 153 ms | 0 |
| Wed 21 | 0 | 0.0 | 99 ms | 0 |
| Wed 23 | 0 | 0.0 | 50 ms | 0 |
| Thu 01 | 0 | 0.0 | 152 ms | 0 |
| Thu 03 | 0 | 0.0 | 91 ms | 0 |
| Thu 05 | 0 | 0.0 | 128 ms | 0 |
| Thu 07 | 0 | 0.0 | 57 ms | 0 |
| Thu 09 | 0 | 0.0 | 67 ms | 0 |
| Thu 11 | 0 | 0.0 | 64 ms | 0 |
| Thu 13 | 0 | 0.0 | 115 ms | 0 |
| Thu 15 | 0 | 0.0 | 62 ms | 0 |
| Thu 18 | 0 | 0.0 | 175 ms | 0 |
| Thu 19 | 0 | 0.0 | 46 ms | 0 |
| Thu 21 | 0 | 0.0 | 68 ms | 0 |
| Thu 23 | 0 | 0.0 | 88 ms | 0 |
| Fri 01 | 0 | 0.0 | 74 ms | 0 |
| Fri 03 | 0 | 0.0 | 59 ms | 0 |
| Fri 05 | 0 | 0.0 | 190 ms | 0 |
| Fri 07 | 0 | 0.0 | 47 ms | 0 |
| Fri 09 | 0 | 0.0 | 147 ms | 0 |
| Fri 11 | 0 | 0.0 | 80 ms | 0 |
| Fri 13 | 0 | 0.0 | 44 ms | 0 |
| Fri 15 | 0 | 0.0 | 44 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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Fullview 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 Fullview yet. Outages of 10 minutes or more get their own page here.
Having trouble with Fullview?
One report per service every 10 minutes from this network. No account.
Follow Fullview
Get an email when Fullview goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Fullview alerts to Slack, Discord or a webhook — free.
About Fullview
We track Fullview (fullview.io) as part of the Productivity group. See what your customers see. Fullview combines one-click cobrowsing and session replays so support teams can diagnose faster, resolve in fewer touches, and stop asking customers to explain.
Fullview publishes an official status page at status.fullview.io; 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: 85 ms average, 42–190 ms range across 13 successful checks.
Questions
Is Fullview down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Fullview last down?
We have not recorded a public Fullview incident since monitoring began 8 days ago.
What is Fullview's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Fullview respond?
85 ms on average over the last 24 hours (42–190 ms).
Does Fullview have an official status page?
Yes, at https://status.fullview.io.
Fullview 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 Fullview here at once, the problem is on Fullview'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 Fullview. 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.