User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / News
nytimes.com · News
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 109 ms · 9 min ago.
No status feed
Wordle does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 20:30 | 0 | 0.0 | 167 ms | 0 |
| 20:45 | 0 | 0.0 | 324 ms | 0 |
| 21:00 | 0 | 0.0 | 159 ms | 0 |
| 21:15 | 0 | 0.0 | 100 ms | 0 |
| 21:30 | 0 | 0.0 | 113 ms | 0 |
| 21:45 | 0 | 0.0 | 66 ms | 0 |
| 22:00 | 0 | 0.0 | 115 ms | 0 |
| 22:15 | 0 | 0.0 | 106 ms | 0 |
| 22:30 | 0 | 0.0 | 109 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Wordle 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 Wordle goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Wordle alerts to Slack, Discord or a webhook — free.
Runs on: Fastly
Wordle, at nytimes.com, is one of the News services we monitor. Wordle is the New York Times' daily five-letter word game.
Wordle has no official status feed we can read, so this page relies on our own checks and user reports.
Typical issues with Wordle: the puzzle not loading, streaks resetting, and stats not syncing.
Response time over the last 24 hours: 142 ms average, 63–530 ms range across 15 successful checks.
Checks are succeeding and user reports are near the baseline.
142 ms on average over the last 24 hours (63–530 ms).
Not one we can read. This page uses independent checks of nytimes.com and user reports.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For Wordle, watch for the puzzle not loading, streaks resetting, and stats not syncing. If many people report Wordle here at once, the problem is on Wordle's side.