User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Food
sweetgreen.com · Food
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 328 ms · 4 min ago.
No status feed
Sweetgreen does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 13:15 | 0 | 0.0 | 753 ms | 0 |
| 13:30 | 0 | 0.0 | 576 ms | 0 |
| 13:45 | 0 | 0.0 | 742 ms | 0 |
| 14:00 | 0 | 0.0 | 1093 ms | 0 |
| 14:15 | 0 | 0.0 | 588 ms | 0 |
| 14:30 | 0 | 0.0 | 561 ms | 0 |
| 14:45 | 0 | 0.0 | 336 ms | 0 |
| 15:00 | 0 | 0.0 | 607 ms | 0 |
| 15:15 | 0 | 0.0 | 817 ms | 0 |
| 15:30 | 0 | 0.0 | 677 ms | 0 |
| 15:45 | 0 | 0.0 | 1093 ms | 0 |
| 16:00 | 0 | 0.0 | 793 ms | 0 |
| 16:15 | 0 | 0.0 | 323 ms | 0 |
| 16:30 | 0 | 0.0 | 960 ms | 0 |
| 16:45 | 0 | 0.0 | 506 ms | 0 |
| 17:00 | 0 | 0.0 | 994 ms | 0 |
| 17:15 | 0 | 0.0 | 343 ms | 0 |
| 17:30 | 0 | 0.0 | 610 ms | 0 |
| 17:45 | 0 | 0.0 | 1005 ms | 0 |
| 18:00 | 0 | 0.0 | 1017 ms | 0 |
| 18:15 | 0 | 0.0 | 280 ms | 0 |
| 18:30 | 0 | 0.0 | 938 ms | 0 |
| 18:45 | 0 | 0.0 | 361 ms | 0 |
| 19:00 | 0 | 0.0 | 388 ms | 0 |
| 19:15 | 0 | 0.0 | 560 ms | 0 |
| 19:30 | 0 | 0.0 | 689 ms | 0 |
| 19:45 | 0 | 0.0 | 1090 ms | 0 |
| 20:00 | 0 | 0.0 | 987 ms | 0 |
| 20:15 | 0 | 0.0 | 968 ms | 0 |
| 20:30 | 0 | 0.0 | 1035 ms | 0 |
| 20:45 | 0 | 0.0 | 907 ms | 0 |
| 21:00 | 0 | 0.0 | 955 ms | 0 |
| 21:15 | 0 | 0.0 | 1058 ms | 0 |
| 21:30 | 0 | 0.0 | 425 ms | 0 |
| 21:45 | 0 | 0.0 | 692 ms | 0 |
| 22:00 | 0 | 0.0 | 1293 ms | 0 |
| 22:15 | 0 | 0.0 | 862 ms | 0 |
| 22:30 | 0 | 0.0 | 775 ms | 0 |
| 22:45 | 0 | 0.0 | 767 ms | 0 |
| 23:00 | 0 | 0.0 | 1027 ms | 0 |
| 23:15 | 0 | 0.0 | 1496 ms | 0 |
| 23:30 | 0 | 0.0 | 328 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 Sweetgreen 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 Sweetgreen goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Sweetgreen alerts to Slack, Discord or a webhook — free.
We track Sweetgreen (sweetgreen.com) as part of the Food group. Live checks and user reports.
Sweetgreen has no official status feed we can read, so this page relies on our own checks and user reports.
What usually goes wrong with food services: ordering and checkout failures, delivery tracking stalling, and restaurant menus not loading at peak meal times.
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: 784 ms average, 253–1950 ms range across 79 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public Sweetgreen incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
784 ms on average over the last 24 hours (253–1950 ms).
Not one we can read. This page uses independent checks of sweetgreen.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 food services, watch for ordering and checkout failures, delivery tracking stalling, and restaurant menus not loading at peak meal times. If many people report Sweetgreen here at once, the problem is on Sweetgreen's side.