User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / News
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 24 min ago. Last stored result reached it in 60 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 09 | 0 | 0.0 | 160 ms | 0 |
| Tue 12 | 0 | 0.0 | 104 ms | 0 |
| Tue 14 | 0 | 0.0 | 196 ms | 0 |
| Tue 16 | 0 | 0.0 | 132 ms | 0 |
| Tue 18 | 0 | 0.0 | 159 ms | 0 |
| Tue 21 | 0 | 0.0 | 193 ms | 0 |
| Tue 23 | 0 | 0.0 | 128 ms | 0 |
| Wed 01 | 0 | 0.0 | 174 ms | 0 |
| Wed 03 | 0 | 0.0 | 105 ms | 0 |
| Wed 06 | 0 | 0.0 | 68 ms | 0 |
| Wed 08 | 0 | 0.0 | 69 ms | 0 |
| Wed 10 | 0 | 0.0 | 79 ms | 0 |
| Wed 12 | 0 | 0.0 | 89 ms | 0 |
| Wed 14 | 0 | 0.0 | 69 ms | 0 |
| Wed 16 | 0 | 0.0 | 165 ms | 0 |
| Wed 19 | 0 | 0.0 | 74 ms | 0 |
| Wed 21 | 0 | 0.0 | 248 ms | 0 |
| Wed 23 | 0 | 0.0 | 129 ms | 0 |
| Thu 01 | 0 | 0.0 | 136 ms | 0 |
| Thu 03 | 0 | 0.0 | 110 ms | 0 |
| Thu 05 | 0 | 0.0 | 148 ms | 0 |
| Thu 07 | 0 | 0.0 | 97 ms | 0 |
| Thu 10 | 0 | 0.0 | 125 ms | 0 |
| Thu 12 | 0 | 0.0 | 143 ms | 0 |
| Thu 14 | 0 | 0.0 | 116 ms | 0 |
| Thu 16 | 0 | 0.0 | 61 ms | 0 |
| Thu 18 | 0 | 0.0 | 101 ms | 0 |
| Thu 20 | 0 | 0.0 | 91 ms | 0 |
| Thu 22 | 0 | 0.0 | 105 ms | 0 |
| Fri 00 | 0 | 0.0 | 124 ms | 0 |
| Fri 02 | 0 | 0.0 | 277 ms | 0 |
| Fri 04 | 0 | 0.0 | 168 ms | 0 |
| Fri 06 | 0 | 0.0 | 59 ms | 0 |
| Fri 07 | 0 | 0.0 | 123 ms | 0 |
| Fri 09 | 0 | 0.0 | 101 ms | 0 |
| Fri 10 | 0 | 0.0 | 62 ms | 0 |
| Fri 12 | 0 | 0.0 | 83 ms | 0 |
| Fri 14 | 0 | 0.0 | 110 ms | 0 |
| Fri 16 | 0 | 0.0 | 145 ms | 0 |
| Fri 18 | 0 | 0.0 | 167 ms | 0 |
| Fri 19 | 0 | 0.0 | 184 ms | 0 |
| Fri 20 | 0 | 0.0 | 131 ms | 0 |
| Fri 22 | 0 | 0.0 | 190 ms | 0 |
| Sat 00 | 0 | 0.0 | 140 ms | 0 |
| Sat 02 | 0 | 0.0 | 136 ms | 0 |
| Sat 05 | 0 | 0.0 | 104 ms | 0 |
| Sat 07 | 0 | 0.0 | 138 ms | 0 |
| Sat 09 | 0 | 0.0 | 60 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for NeoForged 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 NeoForged goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send NeoForged alerts to Slack, Discord or a webhook — free.
We track NeoForged (neoforged.net) as part of the News group. Files, news and information from the NeoForged Project
NeoForged publishes an official status page at status.neoforged.net; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with news services: news sites and live streams slowing under breaking-news traffic, and weather alerts and radar pages failing during storms.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 127 ms average, 60–190 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 NeoForged incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
127 ms on average over the last 24 hours (60–190 ms).
Yes, at https://status.neoforged.net.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For news services, watch for news sites and live streams slowing under breaking-news traffic, and weather alerts and radar pages failing during storms. If many people report NeoForged here at once, the problem is on NeoForged'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 NeoForged. 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.