User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Shopping
loblaws.ca · Shopping
Is Loblaws down?
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → loblaws.ca—
Your browser → us—
Our checksNot enough checks
Official · ReportsNo status feed · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Our checks
Not enough checks
Last check reached it in 51 ms · 4 min ago.
Official status
No status feed
Loblaws does not publish a status feed we can read.
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 20:30 | 0 | 0.0 | 394 ms | 0 |
| 20:45 | 0 | 0.0 | 221 ms | 0 |
| 21:00 | 0 | 0.0 | 73 ms | 0 |
| 21:15 | 0 | 0.0 | 734 ms | 0 |
| 21:30 | 0 | 0.0 | 179 ms | 0 |
| 21:45 | 0 | 0.0 | 245 ms | 0 |
| 22:00 | 0 | 0.0 | 175 ms | 0 |
| 22:15 | 0 | 0.0 | 320 ms | 0 |
| 22:30 | 0 | 0.0 | 389 ms | 0 |
| 22:45 | 0 | 0.0 | 274 ms | 0 |
| 23:00 | 0 | 0.0 | 228 ms | 0 |
| 23:15 | 0 | 0.0 | 254 ms | 0 |
| 23:30 | 0 | 0.0 | 204 ms | 0 |
| 23:45 | 0 | 0.0 | 309 ms | 0 |
| 00:00 | 0 | 0.0 | 188 ms | 0 |
| 00:15 | 0 | 0.0 | 239 ms | 0 |
| 00:30 | 0 | 0.0 | 51 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 2 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Loblaws badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Loblaws yet. Outages of 10 minutes or more get their own page here.
Having trouble with Loblaws?
One report per service every 10 minutes from this network. No account.
Follow Loblaws
Get an email when Loblaws goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Loblaws alerts to Slack, Discord or a webhook — free.
About Loblaws
Loblaws is listed in our Shopping category and checked at loblaws.ca. Loblaws is Canada's largest grocer, with PC Express online ordering.
Loblaws has no official status feed we can read, so this page relies on our own checks and user reports.
Typical issues with Loblaws: PC Express orders failing, PC Optimum points missing, and app errors.
Measured uptime from our checks: 100% over 2 days of checks. No public incidents logged since monitoring began 2 days ago.
Response time over the last 24 hours: 277 ms average, 40–1356 ms range across 31 successful checks.
Questions
Is Loblaws down right now?
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
When was Loblaws last down?
We have not recorded a public Loblaws incident since monitoring began 2 days ago.
What is Loblaws's uptime?
From our own checks: 100% over 2 days of checks.
How fast does Loblaws respond?
277 ms on average over the last 24 hours (40–1356 ms).
Does Loblaws have an official status page?
Not one we can read. This page uses independent checks of loblaws.ca and user reports.
Loblaws not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For Loblaws, watch for PC Express orders failing, PC Optimum points missing, and app errors. If many people report Loblaws here at once, the problem is on Loblaws's side.