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 18 min ago. Last stored result reached it in 120 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 388 ms | 0 |
| Mon 22 | 0 | 0.0 | 92 ms | 0 |
| Tue 00 | 0 | 0.0 | 188 ms | 0 |
| Tue 02 | 0 | 0.0 | 352 ms | 0 |
| Tue 04 | 0 | 0.0 | 248 ms | 0 |
| Tue 06 | 0 | 0.0 | 224 ms | 0 |
| Tue 08 | 0 | 0.0 | 136 ms | 0 |
| Tue 10 | 0 | 0.0 | 96 ms | 0 |
| Tue 13 | 0 | 0.0 | 127 ms | 0 |
| Tue 15 | 0 | 0.0 | 372 ms | 0 |
| Tue 17 | 0 | 0.0 | 167 ms | 0 |
| Tue 19 | 0 | 0.0 | 115 ms | 0 |
| Tue 22 | 0 | 0.0 | 124 ms | 0 |
| Wed 00 | 0 | 0.0 | 101 ms | 0 |
| Wed 02 | 0 | 0.0 | 88 ms | 0 |
| Wed 04 | 0 | 0.0 | 308 ms | 0 |
| Wed 07 | 0 | 0.0 | 153 ms | 0 |
| Wed 09 | 0 | 0.0 | 70 ms | 0 |
| Wed 11 | 0 | 0.0 | 315 ms | 0 |
| Wed 13 | 0 | 0.0 | 92 ms | 0 |
| Wed 15 | 0 | 0.0 | 94 ms | 0 |
| Wed 17 | 0 | 0.0 | 257 ms | 0 |
| Wed 20 | 0 | 0.0 | 352 ms | 0 |
| Wed 22 | 0 | 0.0 | 74 ms | 0 |
| Thu 00 | 0 | 0.0 | 107 ms | 0 |
| Thu 02 | 0 | 0.0 | 245 ms | 0 |
| Thu 04 | 0 | 0.0 | 106 ms | 0 |
| Thu 06 | 0 | 0.0 | 120 ms | 0 |
| Thu 08 | 0 | 0.0 | 115 ms | 0 |
| Thu 10 | 0 | 0.0 | 237 ms | 0 |
| Thu 13 | 0 | 0.0 | 141 ms | 0 |
| Thu 15 | 0 | 0.0 | 94 ms | 0 |
| Thu 17 | 0 | 0.0 | 209 ms | 0 |
| Thu 19 | 0 | 0.0 | 109 ms | 0 |
| Thu 21 | 0 | 0.0 | 113 ms | 0 |
| Thu 23 | 0 | 0.0 | 90 ms | 0 |
| Fri 01 | 0 | 0.0 | 101 ms | 0 |
| Fri 02 | 0 | 0.0 | 109 ms | 0 |
| Fri 04 | 0 | 0.0 | 196 ms | 0 |
| Fri 06 | 0 | 0.0 | 246 ms | 0 |
| Fri 08 | 0 | 0.0 | 91 ms | 0 |
| Fri 10 | 0 | 0.0 | 213 ms | 0 |
| Fri 11 | 0 | 0.0 | 83 ms | 0 |
| Fri 13 | 0 | 0.0 | 98 ms | 0 |
| Fri 15 | 0 | 0.0 | 83 ms | 0 |
| Fri 17 | 0 | 0.0 | 133 ms | 0 |
| Fri 18 | 0 | 0.0 | 91 ms | 0 |
| Fri 19 | 0 | 0.0 | 120 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 Trofeo 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 Trofeo goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Trofeo alerts to Slack, Discord or a webhook — free.
Trofeo is listed in our Productivity category and checked at trofeo.io. trofēo is an ad tech company powering Victory Marketing, an all-new player-first ad experience driving incremental global ad monetization revenue for developers.
Trofeo publishes an official status page at status.trofeo.io; 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: 126 ms average, 83–246 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 Trofeo incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
126 ms on average over the last 24 hours (83–246 ms).
Yes, at https://status.trofeo.io.
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 Trofeo here at once, the problem is on Trofeo'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 Trofeo. 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.