User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
usclimatedata.com · Cloud & developer
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 298 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 04 | 0 | 0.0 | 259 ms | 0 |
| Tue 06 | 0 | 0.0 | 382 ms | 0 |
| Tue 08 | 0 | 0.0 | 388 ms | 0 |
| Tue 10 | 0 | 0.0 | 344 ms | 0 |
| Tue 12 | 0 | 0.0 | 303 ms | 0 |
| Tue 14 | 0 | 0.0 | 368 ms | 0 |
| Tue 17 | 0 | 0.0 | 312 ms | 0 |
| Tue 19 | 0 | 0.0 | 318 ms | 0 |
| Tue 21 | 0 | 0.0 | 306 ms | 0 |
| Wed 00 | 0 | 0.0 | 319 ms | 0 |
| Wed 02 | 0 | 0.0 | 302 ms | 0 |
| Wed 04 | 0 | 0.0 | 335 ms | 0 |
| Wed 06 | 0 | 0.0 | 294 ms | 0 |
| Wed 08 | 0 | 0.0 | 371 ms | 0 |
| Wed 11 | 0 | 0.0 | 206 ms | 0 |
| Wed 13 | 0 | 0.0 | 368 ms | 0 |
| Wed 15 | 0 | 0.0 | 453 ms | 0 |
| Wed 17 | 0 | 0.0 | 215 ms | 0 |
| Wed 19 | 0 | 0.0 | 272 ms | 0 |
| Wed 22 | 0 | 0.0 | 257 ms | 0 |
| Thu 00 | 0 | 0.0 | 425 ms | 0 |
| Thu 02 | 0 | 0.0 | 370 ms | 0 |
| Thu 04 | 0 | 0.0 | 171 ms | 0 |
| Thu 06 | 0 | 0.0 | 396 ms | 0 |
| Thu 08 | 0 | 0.0 | 334 ms | 0 |
| Thu 10 | 0 | 0.0 | 320 ms | 0 |
| Thu 12 | 0 | 0.0 | 337 ms | 0 |
| Thu 14 | 0 | 0.0 | 216 ms | 0 |
| Thu 16 | 0 | 0.0 | 334 ms | 0 |
| Thu 19 | 0 | 0.0 | 362 ms | 0 |
| Thu 21 | 0 | 0.0 | 144 ms | 0 |
| Thu 23 | 0 | 0.0 | 250 ms | 0 |
| Fri 01 | 0 | 0.0 | 301 ms | 0 |
| Fri 03 | 0 | 0.0 | 335 ms | 0 |
| Fri 05 | 0 | 0.0 | 297 ms | 0 |
| Fri 07 | 0 | 0.0 | 224 ms | 0 |
| Fri 08 | 0 | 0.0 | 352 ms | 0 |
| Fri 10 | 0 | 0.0 | 326 ms | 0 |
| Fri 12 | 0 | 0.0 | 311 ms | 0 |
| Fri 14 | 0 | 0.0 | 369 ms | 0 |
| Fri 16 | 0 | 0.0 | 338 ms | 0 |
| Fri 18 | 0 | 0.0 | 342 ms | 0 |
| Fri 20 | 0 | 0.0 | 314 ms | 0 |
| Fri 22 | 0 | 0.0 | 287 ms | 0 |
| Fri 23 | 0 | 0.0 | 348 ms | 0 |
| Sat 01 | 0 | 0.0 | 315 ms | 0 |
| Sat 03 | 0 | 0.0 | 252 ms | 0 |
| Sat 05 | 0 | 0.0 | 298 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 U.S. Climate Data 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 U.S. Climate Data goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send U.S. Climate Data alerts to Slack, Discord or a webhook — free.
U.S. Climate Data is listed in our Cloud & developer category and checked at usclimatedata.com. The climate in the United States. Information regarding the temperature, precipitation and sunshine for more than 5000 cities in the United States.
U.S. Climate Data publishes an official status page at status.usclimatedata.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 317 ms average, 224–369 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public U.S. Climate Data incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
317 ms on average over the last 24 hours (224–369 ms).
Yes, at https://status.usclimatedata.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report U.S. Climate Data here at once, the problem is on U.S. Climate Data'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 U.S. Climate Data. 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.