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 2 hr ago. Last stored result reached it in 550 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 431 ms | 0 |
| Nov 7 | 0 | 0.0 | 343 ms | 0 |
| Nov 7 | 0 | 0.0 | 414 ms | 0 |
| Nov 7 | 0 | 0.0 | 499 ms | 0 |
| Nov 7 | 0 | 0.0 | 502 ms | 0 |
| Nov 8 | 0 | 0.0 | 412 ms | 0 |
| Nov 8 | 0 | 0.0 | 425 ms | 0 |
| Nov 8 | 0 | 0.0 | 434 ms | 0 |
| Nov 8 | 0 | 0.0 | 322 ms | 0 |
| Nov 9 | 0 | 0.0 | 394 ms | 0 |
| Nov 9 | 0 | 0.0 | 470 ms | 0 |
| Nov 9 | 0 | 0.0 | 459 ms | 0 |
| Nov 9 | 0 | 0.0 | 441 ms | 0 |
| Nov 10 | 0 | 0.0 | 379 ms | 0 |
| Nov 10 | 0 | 0.0 | 461 ms | 0 |
| Nov 10 | 0 | 0.0 | 485 ms | 0 |
| Nov 10 | 0 | 0.0 | 446 ms | 0 |
| Nov 11 | 0 | 0.0 | 2047 ms | 0 |
| Nov 11 | 0 | 0.0 | 351 ms | 0 |
| Nov 11 | 0 | 0.0 | 466 ms | 0 |
| Nov 11 | 0 | 0.0 | 400 ms | 0 |
| Nov 12 | 0 | 0.0 | 469 ms | 0 |
| Nov 12 | 0 | 0.0 | 383 ms | 0 |
| Nov 12 | 0 | 0.0 | 386 ms | 0 |
| Nov 12 | 0 | 0.0 | 474 ms | 0 |
| Nov 13 | 0 | 0.0 | 438 ms | 0 |
| Nov 13 | 0 | 0.0 | 410 ms | 0 |
| Nov 13 | 0 | 0.0 | 463 ms | 0 |
| Nov 13 | 0 | 0.0 | 470 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 FUTNext 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 FUTNext goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send FUTNext alerts to Slack, Discord or a webhook — free.
FUTNext, at futnext.com, is one of the Productivity services we monitor. Everything for your EA FC 27 Ultimate Team club — cheapest SBC solutions, live prices, pack odds and evolutions, updated the moment EA drops content.
FUTNext publishes an official status page at status.futnext.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: 468 ms average, 362–714 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 FUTNext incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
468 ms on average over the last 24 hours (362–714 ms).
Yes, at https://status.futnext.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 FUTNext here at once, the problem is on FUTNext'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 FUTNext. 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.