User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Shopping
acquia.com · Shopping
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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 106 ms · 7 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 08:00 | 0 | 0.0 | 116 ms | 0 |
| 08:15 | 0 | 0.0 | 104 ms | 0 |
| 08:30 | 0 | 0.0 | 204 ms | 0 |
| 08:45 | 0 | 0.0 | 166 ms | 0 |
| 09:00 | 0 | 0.0 | 156 ms | 0 |
| 09:15 | 0 | 0.0 | 85 ms | 0 |
| 09:30 | 0 | 0.0 | 165 ms | 0 |
| 09:45 | 0 | 0.0 | 189 ms | 0 |
| 10:00 | 0 | 0.0 | 110 ms | 0 |
| 10:15 | 0 | 0.0 | 118 ms | 0 |
| 10:30 | 0 | 0.0 | 107 ms | 0 |
| 10:45 | 0 | 0.0 | 64 ms | 0 |
| 11:00 | 0 | 0.0 | 140 ms | 0 |
| 11:15 | 0 | 0.0 | 150 ms | 0 |
| 11:30 | 0 | 0.0 | 142 ms | 0 |
| 11:45 | 0 | 0.0 | 140 ms | 0 |
| 12:00 | 0 | 0.0 | 184 ms | 0 |
| 12:15 | 0 | 0.0 | 171 ms | 0 |
| 12:30 | 0 | 0.0 | 77 ms | 0 |
| 12:45 | 0 | 0.0 | 203 ms | 0 |
| 13:00 | 0 | 0.0 | 205 ms | 0 |
| 13:15 | 0 | 0.0 | 37 ms | 0 |
| 13:30 | 0 | 0.0 | 127 ms | 0 |
| 13:45 | 0 | 0.0 | 127 ms | 0 |
| 14:00 | 0 | 0.0 | 215 ms | 0 |
| 14:15 | 0 | 0.0 | 291 ms | 0 |
| 14:30 | 0 | 0.0 | 195 ms | 0 |
| 14:45 | 0 | 0.0 | 141 ms | 0 |
| 15:00 | 0 | 0.0 | 185 ms | 0 |
| 15:15 | 0 | 0.0 | 237 ms | 0 |
| 15:30 | 0 | 0.0 | 136 ms | 0 |
| 15:45 | 0 | 0.0 | 241 ms | 0 |
| 16:00 | 0 | 0.0 | 616 ms | 0 |
| 16:15 | 0 | 0.0 | 117 ms | 0 |
| 16:30 | 0 | 0.0 | 149 ms | 0 |
| 16:45 | 0 | 0.0 | 131 ms | 0 |
| 17:00 | 0 | 0.0 | 188 ms | 0 |
| 17:15 | 0 | 0.0 | 252 ms | 0 |
| 17:30 | 0 | 0.0 | 140 ms | 0 |
| 17:45 | 0 | 0.0 | 235 ms | 0 |
| 18:00 | 0 | 0.0 | 132 ms | 0 |
| 18:15 | 0 | 0.0 | 96 ms | 0 |
| 18:30 | 0 | 0.0 | 37 ms | 0 |
| 18:45 | 0 | 0.0 | 156 ms | 0 |
| 19:00 | 0 | 0.0 | 146 ms | 0 |
| 19:15 | 0 | 0.0 | 139 ms | 0 |
| 19:30 | 0 | 0.0 | 121 ms | 0 |
| 19:45 | 0 | 0.0 | 106 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 Acquia 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 Acquia goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Acquia alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Acquia is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Acquia's side.
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.