User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Shopping
walgreens.com · Shopping
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests walgreens.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 162 ms · 3 min ago.
No status feed
Walgreens does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 11:30 | 0 | 0.0 | 136 ms | 0 |
| 11:45 | 0 | 0.0 | 197 ms | 0 |
| 12:00 | 0 | 0.0 | 147 ms | 0 |
| 12:15 | 0 | 0.0 | 334 ms | 0 |
| 12:30 | 0 | 0.0 | 241 ms | 0 |
| 12:45 | 0 | 0.0 | 113 ms | 0 |
| 13:00 | 0 | 0.0 | 183 ms | 0 |
| 13:15 | 0 | 0.0 | 198 ms | 0 |
| 13:30 | 0 | 0.0 | 100 ms | 0 |
| 13:45 | 0 | 0.0 | 94 ms | 0 |
| 14:00 | 0 | 0.0 | 108 ms | 0 |
| 14:15 | 0 | 0.0 | 127 ms | 0 |
| 14:30 | 0 | 0.0 | 109 ms | 0 |
| 14:45 | 0 | 0.0 | 149 ms | 0 |
| 15:00 | 0 | 0.0 | 383 ms | 0 |
| 15:15 | 0 | 0.0 | 176 ms | 0 |
| 15:30 | 0 | 0.0 | 91 ms | 0 |
| 15:45 | 0 | 0.0 | 125 ms | 0 |
| 16:00 | 0 | 0.0 | 319 ms | 0 |
| 16:15 | 0 | 0.0 | 192 ms | 0 |
| 16:30 | 0 | 0.0 | 212 ms | 0 |
| 16:45 | 0 | 0.0 | 239 ms | 0 |
| 17:00 | 0 | 0.0 | 178 ms | 0 |
| 17:15 | 0 | 0.0 | 151 ms | 0 |
| 17:30 | 0 | 0.0 | 260 ms | 0 |
| 17:45 | 0 | 0.0 | 161 ms | 0 |
| 18:00 | 0 | 0.0 | 112 ms | 0 |
| 18:15 | 0 | 0.0 | 256 ms | 0 |
| 18:30 | 0 | 0.0 | 236 ms | 0 |
| 18:45 | 0 | 0.0 | 229 ms | 0 |
| 19:00 | 0 | 0.0 | 150 ms | 0 |
| 19:15 | 0 | 0.0 | 134 ms | 0 |
| 19:30 | 0 | 0.0 | 269 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.
Embed this status badge · JSON
No outages on record for Walgreens 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 Walgreens goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Checks are succeeding and user reports are near the baseline.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.