User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / News
kare11.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 201 ms · 9 min ago.
No status feed
KARE 11 does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 13:15 | 0 | 0.0 | 454 ms | 0 |
| 13:30 | 0 | 0.0 | 367 ms | 0 |
| 13:45 | 0 | 0.0 | 250 ms | 0 |
| 14:00 | 0 | 0.0 | 359 ms | 0 |
| 14:15 | 0 | 0.0 | 333 ms | 0 |
| 14:30 | 0 | 0.0 | 219 ms | 0 |
| 14:45 | 0 | 0.0 | 405 ms | 0 |
| 15:00 | 0 | 0.0 | 498 ms | 0 |
| 15:15 | 0 | 0.0 | 395 ms | 0 |
| 15:30 | 0 | 0.0 | 265 ms | 0 |
| 15:45 | 0 | 0.0 | 376 ms | 0 |
| 16:00 | 0 | 0.0 | 234 ms | 0 |
| 16:15 | 0 | 0.0 | 423 ms | 0 |
| 16:30 | 0 | 0.0 | 303 ms | 0 |
| 16:45 | 0 | 0.0 | 454 ms | 0 |
| 17:00 | 0 | 0.0 | 374 ms | 0 |
| 17:15 | 0 | 0.0 | 307 ms | 0 |
| 17:30 | 0 | 0.0 | 346 ms | 0 |
| 17:45 | 0 | 0.0 | 512 ms | 0 |
| 18:00 | 0 | 0.0 | 234 ms | 0 |
| 18:15 | 0 | 0.0 | 257 ms | 0 |
| 18:30 | 0 | 0.0 | 271 ms | 0 |
| 18:45 | 0 | 0.0 | 379 ms | 0 |
| 19:00 | 0 | 0.0 | 244 ms | 0 |
| 19:15 | 0 | 0.0 | 284 ms | 0 |
| 19:30 | 0 | 0.0 | 474 ms | 0 |
| 19:45 | 0 | 0.0 | 537 ms | 0 |
| 20:00 | 0 | 0.0 | 427 ms | 0 |
| 20:15 | 0 | 0.0 | 684 ms | 0 |
| 20:30 | 0 | 0.0 | 533 ms | 0 |
| 20:45 | 0 | 0.0 | 250 ms | 0 |
| 21:00 | 0 | 0.0 | 319 ms | 0 |
| 21:15 | 0 | 0.0 | 323 ms | 0 |
| 21:30 | 0 | 0.0 | 341 ms | 0 |
| 21:45 | 0 | 0.0 | 218 ms | 0 |
| 22:00 | 0 | 0.0 | 219 ms | 0 |
| 22:15 | 0 | 0.0 | 327 ms | 0 |
| 22:30 | 0 | 0.0 | 303 ms | 0 |
| 22:45 | 0 | 0.0 | 356 ms | 0 |
| 23:00 | 0 | 0.0 | 216 ms | 0 |
| 23:15 | 0 | 0.0 | 231 ms | 0 |
| 23:30 | 0 | 0.0 | 251 ms | 0 |
| 23:45 | 0 | 0.0 | 201 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 KARE 11 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 KARE 11 goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send KARE 11 alerts to Slack, Discord or a webhook — free.
We track KARE 11 (kare11.com) as part of the News group. Live checks and user reports.
KARE 11 has no official status feed we can read, so this page relies on our own checks and user reports.
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 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 345 ms average, 120–1064 ms range across 80 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public KARE 11 incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
345 ms on average over the last 24 hours (120–1064 ms).
Not one we can read. This page uses independent checks of kare11.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 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 KARE 11 here at once, the problem is on KARE 11's side.