User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is FUTNext 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 → futnext.com—
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 2 hr ago. Last stored result reached it in 392 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 16 | 0 | 0.0 | 520 ms | 0 |
| Mon 19 | 0 | 0.0 | 489 ms | 0 |
| Mon 21 | 0 | 0.0 | 438 ms | 0 |
| Mon 23 | 0 | 0.0 | 441 ms | 0 |
| Tue 01 | 0 | 0.0 | 347 ms | 0 |
| Tue 03 | 0 | 0.0 | 400 ms | 0 |
| Tue 05 | 0 | 0.0 | 379 ms | 0 |
| Tue 07 | 0 | 0.0 | 491 ms | 0 |
| Tue 09 | 0 | 0.0 | 368 ms | 0 |
| Tue 11 | 0 | 0.0 | 461 ms | 0 |
| Tue 14 | 0 | 0.0 | 499 ms | 0 |
| Tue 16 | 0 | 0.0 | 471 ms | 0 |
| Tue 18 | 0 | 0.0 | 507 ms | 0 |
| Tue 20 | 0 | 0.0 | 444 ms | 0 |
| Tue 23 | 0 | 0.0 | 446 ms | 0 |
| Wed 01 | 0 | 0.0 | 2047 ms | 0 |
| Wed 03 | 0 | 0.0 | 2074 ms | 0 |
| Wed 05 | 0 | 0.0 | 347 ms | 0 |
| Wed 08 | 0 | 0.0 | 341 ms | 0 |
| Wed 10 | 0 | 0.0 | 361 ms | 0 |
| Wed 12 | 0 | 0.0 | 530 ms | 0 |
| Wed 14 | 0 | 0.0 | 466 ms | 0 |
| Wed 16 | 0 | 0.0 | 351 ms | 0 |
| Wed 18 | 0 | 0.0 | 400 ms | 0 |
| Wed 21 | 0 | 0.0 | 417 ms | 0 |
| Wed 23 | 0 | 0.0 | 374 ms | 0 |
| Thu 01 | 0 | 0.0 | 344 ms | 0 |
| Thu 03 | 0 | 0.0 | 642 ms | 0 |
| Thu 05 | 0 | 0.0 | 469 ms | 0 |
| Thu 07 | 0 | 0.0 | 337 ms | 0 |
| Thu 09 | 0 | 0.0 | 383 ms | 0 |
| Thu 11 | 0 | 0.0 | 537 ms | 0 |
| Thu 13 | 0 | 0.0 | 766 ms | 0 |
| Thu 15 | 0 | 0.0 | 318 ms | 0 |
| Thu 17 | 0 | 0.0 | 386 ms | 0 |
| Thu 19 | 0 | 0.0 | 402 ms | 0 |
| Thu 21 | 0 | 0.0 | 520 ms | 0 |
| Thu 23 | 0 | 0.0 | 474 ms | 0 |
| Fri 01 | 0 | 0.0 | 362 ms | 0 |
| Fri 03 | 0 | 0.0 | 438 ms | 0 |
| Fri 05 | 0 | 0.0 | 714 ms | 0 |
| Fri 07 | 0 | 0.0 | 380 ms | 0 |
| Fri 09 | 0 | 0.0 | 410 ms | 0 |
| Fri 10 | 0 | 0.0 | 571 ms | 0 |
| Fri 12 | 0 | 0.0 | 398 ms | 0 |
| Fri 14 | 0 | 0.0 | 463 ms | 0 |
| Fri 16 | 0 | 0.0 | 463 ms | 0 |
| Fri 18 | 0 | 0.0 | 392 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 FUTNext 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 FUTNext yet. Outages of 10 minutes or more get their own page here.
Having trouble with FUTNext?
One report per service every 10 minutes from this network. No account.
Follow FUTNext
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.
About FUTNext
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: 465 ms average, 362–714 ms range across 12 successful checks.
Questions
Is FUTNext down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was FUTNext last down?
We have not recorded a public FUTNext incident since monitoring began 8 days ago.
What is FUTNext's uptime?
From our own checks: 100% over 8 days of checks.
How fast does FUTNext respond?
465 ms on average over the last 24 hours (362–714 ms).
Does FUTNext have an official status page?
Yes, at https://status.futnext.com.
FUTNext 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 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.