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 81 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 60 ms | 0 |
| Mon 15 | 0 | 0.0 | 107 ms | 0 |
| Mon 18 | 0 | 0.0 | 134 ms | 0 |
| Mon 20 | 0 | 0.0 | 100 ms | 0 |
| Mon 22 | 0 | 0.0 | 142 ms | 0 |
| Tue 00 | 0 | 0.0 | 89 ms | 0 |
| Tue 02 | 0 | 0.0 | 102 ms | 0 |
| Tue 04 | 0 | 0.0 | 53 ms | 0 |
| Tue 06 | 0 | 0.0 | 45 ms | 0 |
| Tue 08 | 0 | 0.0 | 30 ms | 0 |
| Tue 10 | 0 | 0.0 | 38 ms | 0 |
| Tue 13 | 0 | 0.0 | 60 ms | 0 |
| Tue 15 | 0 | 0.0 | 73 ms | 0 |
| Tue 17 | 0 | 0.0 | 43 ms | 0 |
| Tue 19 | 0 | 0.0 | 109 ms | 0 |
| Tue 22 | 0 | 0.0 | 52 ms | 0 |
| Wed 00 | 0 | 0.0 | 61 ms | 0 |
| Wed 02 | 0 | 0.0 | 172 ms | 0 |
| Wed 04 | 0 | 0.0 | 41 ms | 0 |
| Wed 07 | 0 | 0.0 | 77 ms | 0 |
| Wed 09 | 0 | 0.0 | 58 ms | 0 |
| Wed 11 | 0 | 0.0 | 88 ms | 0 |
| Wed 13 | 0 | 0.0 | 58 ms | 0 |
| Wed 15 | 0 | 0.0 | 48 ms | 0 |
| Wed 17 | 0 | 0.0 | 34 ms | 0 |
| Wed 20 | 0 | 0.0 | 78 ms | 0 |
| Wed 22 | 0 | 0.0 | 82 ms | 0 |
| Thu 00 | 0 | 0.0 | 103 ms | 0 |
| Thu 02 | 0 | 0.0 | 102 ms | 0 |
| Thu 04 | 0 | 0.0 | 108 ms | 0 |
| Thu 06 | 0 | 0.0 | 66 ms | 0 |
| Thu 08 | 0 | 0.0 | 99 ms | 0 |
| Thu 10 | 0 | 0.0 | 41 ms | 0 |
| Thu 12 | 0 | 0.0 | 77 ms | 0 |
| Thu 15 | 0 | 0.0 | 143 ms | 0 |
| Thu 17 | 0 | 0.0 | 78 ms | 0 |
| Thu 19 | 0 | 0.0 | 31 ms | 0 |
| Thu 21 | 0 | 0.0 | 103 ms | 0 |
| Thu 23 | 0 | 0.0 | 57 ms | 0 |
| Fri 01 | 0 | 0.0 | 76 ms | 0 |
| Fri 03 | 0 | 0.0 | 459 ms | 0 |
| Fri 05 | 0 | 0.0 | 51 ms | 0 |
| Fri 07 | 0 | 0.0 | 42 ms | 0 |
| Fri 09 | 0 | 0.0 | 74 ms | 0 |
| Fri 11 | 0 | 0.0 | 69 ms | 0 |
| Fri 13 | 0 | 0.0 | 71 ms | 0 |
| Fri 15 | 0 | 0.0 | 38 ms | 0 |
| Fri 17 | 0 | 0.0 | 81 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 Surfe 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 Surfe goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Surfe alerts to Slack, Discord or a webhook — free.
Surfe is listed in our Productivity category and checked at surfe.com. Surfe is the Pipeline Generation Platform for revenue teams: find and enrich verified B2B contacts, act on buying signals, and sync to your CRM. Start free.
Surfe publishes an official status page at status.surfe.com; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 94 ms average, 20–459 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Surfe incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
94 ms on average over the last 24 hours (20–459 ms).
Yes, at https://status.surfe.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 Surfe here at once, the problem is on Surfe'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 Surfe. 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.