User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Utilities
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 1019 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 11 | 0 | 0.0 | 229 ms | 0 |
| Mon 13 | 0 | 0.0 | 456 ms | 0 |
| Mon 15 | 0 | 0.0 | 568 ms | 0 |
| Mon 17 | 0 | 0.0 | 620 ms | 0 |
| Mon 19 | 0 | 0.0 | 221 ms | 0 |
| Mon 21 | 0 | 0.0 | 2632 ms | 0 |
| Tue 00 | 0 | 0.0 | 989 ms | 0 |
| Tue 02 | 0 | 0.0 | 1108 ms | 0 |
| Tue 04 | 0 | 0.0 | 238 ms | 0 |
| Tue 06 | 0 | 0.0 | 233 ms | 0 |
| Tue 08 | 0 | 0.0 | 310 ms | 0 |
| Tue 10 | 0 | 0.0 | 463 ms | 0 |
| Tue 12 | 0 | 0.0 | 437 ms | 0 |
| Tue 14 | 0 | 0.0 | 1083 ms | 0 |
| Tue 17 | 0 | 0.0 | 824 ms | 0 |
| Tue 19 | 0 | 0.0 | 203 ms | 0 |
| Tue 21 | 0 | 0.0 | 660 ms | 0 |
| Wed 00 | 0 | 0.0 | 645 ms | 0 |
| Wed 03 | 0 | 0.0 | 237 ms | 0 |
| Wed 05 | 0 | 0.0 | 599 ms | 0 |
| Wed 07 | 0 | 0.0 | 917 ms | 0 |
| Wed 09 | 0 | 0.0 | 361 ms | 0 |
| Wed 12 | 0 | 0.0 | 989 ms | 0 |
| Wed 14 | 0 | 0.0 | 977 ms | 0 |
| Wed 16 | 0 | 0.0 | 294 ms | 0 |
| Wed 18 | 0 | 0.0 | 249 ms | 0 |
| Wed 20 | 0 | 0.0 | 886 ms | 0 |
| Wed 22 | 0 | 0.0 | 1042 ms | 0 |
| Thu 00 | 0 | 0.0 | 265 ms | 0 |
| Thu 03 | 0 | 0.0 | 512 ms | 0 |
| Thu 05 | 0 | 0.0 | 472 ms | 0 |
| Thu 07 | 0 | 0.0 | 1035 ms | 0 |
| Thu 09 | 0 | 0.0 | 790 ms | 0 |
| Thu 11 | 0 | 0.0 | 395 ms | 0 |
| Thu 13 | 0 | 0.0 | 337 ms | 0 |
| Thu 15 | 0 | 0.0 | 771 ms | 0 |
| Thu 17 | 0 | 0.0 | 1018 ms | 0 |
| Thu 19 | 0 | 0.0 | 896 ms | 0 |
| Thu 21 | 0 | 0.0 | 730 ms | 0 |
| Thu 23 | 0 | 0.0 | 703 ms | 0 |
| Fri 01 | 0 | 0.0 | 1003 ms | 0 |
| Fri 03 | 0 | 0.0 | 184 ms | 0 |
| Fri 05 | 0 | 0.0 | 1013 ms | 0 |
| Fri 07 | 0 | 0.0 | 1007 ms | 0 |
| Fri 09 | 0 | 0.0 | 409 ms | 0 |
| Fri 11 | 0 | 0.0 | 653 ms | 0 |
| Fri 13 | 0 | 0.0 | 259 ms | 0 |
| Fri 15 | 0 | 0.0 | 1019 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 Foreca 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 Foreca goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Foreca alerts to Slack, Discord or a webhook — free.
We track Foreca (foreca.com) as part of the Utilities group. Foreca provides you the most accurate local and long-range weather forecasts, radar maps, alerts, and severe weather updates for worldwide locations.
Foreca publishes an official status page at status.foreca.com; when we can read it, its incident level is folded into the status shown here.
Common problems for utilities services: outage maps and bill-pay pages slowing or failing during storms and peak demand, and account 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: 753 ms average, 184–1061 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 Foreca incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
753 ms on average over the last 24 hours (184–1061 ms).
Yes, at https://status.foreca.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For utilities services, watch for outage maps and bill-pay pages slowing or failing during storms and peak demand, and account sign-in problems. If many people report Foreca here at once, the problem is on Foreca'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 Foreca. 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.