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 44 min ago. Last stored result reached it in 217 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 296 ms | 0 |
| Mon 23 | 0 | 0.0 | 188 ms | 0 |
| Tue 01 | 0 | 0.0 | 156 ms | 0 |
| Tue 03 | 0 | 0.0 | 204 ms | 0 |
| Tue 05 | 0 | 0.0 | 196 ms | 0 |
| Tue 08 | 0 | 0.0 | 330 ms | 0 |
| Tue 10 | 0 | 0.0 | 174 ms | 0 |
| Tue 12 | 0 | 0.0 | 324 ms | 0 |
| Tue 14 | 0 | 0.0 | 230 ms | 0 |
| Tue 16 | 0 | 0.0 | 217 ms | 0 |
| Tue 18 | 0 | 0.0 | 185 ms | 0 |
| Tue 21 | 0 | 0.0 | 184 ms | 0 |
| Tue 23 | 0 | 0.0 | 291 ms | 0 |
| Wed 01 | 0 | 0.0 | 191 ms | 0 |
| Wed 03 | 0 | 0.0 | 189 ms | 0 |
| Wed 06 | 0 | 0.0 | 163 ms | 0 |
| Wed 08 | 0 | 0.0 | 212 ms | 0 |
| Wed 10 | 0 | 0.0 | 207 ms | 0 |
| Wed 12 | 0 | 0.0 | 208 ms | 0 |
| Wed 14 | 0 | 0.0 | 209 ms | 0 |
| Wed 16 | 0 | 0.0 | 238 ms | 0 |
| Wed 19 | 0 | 0.0 | 360 ms | 0 |
| Wed 21 | 0 | 0.0 | 233 ms | 0 |
| Wed 23 | 0 | 0.0 | 244 ms | 0 |
| Thu 01 | 0 | 0.0 | 216 ms | 0 |
| Thu 03 | 0 | 0.0 | 191 ms | 0 |
| Thu 04 | 0 | 0.0 | 195 ms | 0 |
| Thu 06 | 0 | 0.0 | 217 ms | 0 |
| Thu 08 | 0 | 0.0 | 237 ms | 0 |
| Thu 10 | 0 | 0.0 | 197 ms | 0 |
| Thu 12 | 0 | 0.0 | 185 ms | 0 |
| Thu 14 | 0 | 0.0 | 207 ms | 0 |
| Thu 16 | 0 | 0.0 | 171 ms | 0 |
| Thu 18 | 0 | 0.0 | 204 ms | 0 |
| Thu 20 | 0 | 0.0 | 213 ms | 0 |
| Thu 22 | 0 | 0.0 | 208 ms | 0 |
| Fri 00 | 0 | 0.0 | 194 ms | 0 |
| Fri 02 | 0 | 0.0 | 236 ms | 0 |
| Fri 04 | 0 | 0.0 | 202 ms | 0 |
| Fri 06 | 0 | 0.0 | 170 ms | 0 |
| Fri 08 | 0 | 0.0 | 184 ms | 0 |
| Fri 11 | 0 | 0.0 | 200 ms | 0 |
| Fri 13 | 0 | 0.0 | 182 ms | 0 |
| Fri 15 | 0 | 0.0 | 196 ms | 0 |
| Fri 17 | 0 | 0.0 | 246 ms | 0 |
| Fri 19 | 0 | 0.0 | 212 ms | 0 |
| Fri 21 | 0 | 0.0 | 212 ms | 0 |
| Fri 23 | 0 | 0.0 | 253 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for FPL Team 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 FPL Team goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send FPL Team alerts to Slack, Discord or a webhook — free.
FPL Team, at fpl.team, is one of the Productivity services we monitor. Your Fantasy Premier League home for transfer planning, live rank tracking, player predictions, and squad analysis — all in one place.
FPL Team publishes an official status page at status.fpl.team; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 208 ms average, 164–288 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public FPL Team incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
208 ms on average over the last 24 hours (164–288 ms).
Yes, at https://status.fpl.team.
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 FPL Team here at once, the problem is on FPL Team'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 FPL Team. 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.