User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 min ago. Last stored result reached it in 213 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 03 | 0 | 0.0 | 228 ms | 0 |
| Tue 05 | 0 | 0.0 | 224 ms | 0 |
| Tue 07 | 0 | 0.0 | 284 ms | 0 |
| Tue 09 | 0 | 0.0 | 107 ms | 0 |
| Tue 12 | 0 | 0.0 | 92 ms | 0 |
| Tue 14 | 0 | 0.0 | 118 ms | 0 |
| Tue 16 | 0 | 0.0 | 228 ms | 0 |
| Tue 18 | 0 | 0.0 | 157 ms | 0 |
| Tue 21 | 0 | 0.0 | 134 ms | 0 |
| Tue 23 | 0 | 0.0 | 164 ms | 0 |
| Wed 01 | 0 | 0.0 | 175 ms | 0 |
| Wed 03 | 0 | 0.0 | 127 ms | 0 |
| Wed 05 | 0 | 0.0 | 221 ms | 0 |
| Wed 08 | 0 | 0.0 | 218 ms | 0 |
| Wed 10 | 0 | 0.0 | 144 ms | 0 |
| Wed 12 | 0 | 0.0 | 192 ms | 0 |
| Wed 14 | 0 | 0.0 | 71 ms | 0 |
| Wed 16 | 0 | 0.0 | 87 ms | 0 |
| Wed 18 | 0 | 0.0 | 85 ms | 0 |
| Wed 21 | 0 | 0.0 | 303 ms | 0 |
| Wed 23 | 0 | 0.0 | 396 ms | 0 |
| Thu 01 | 0 | 0.0 | 157 ms | 0 |
| Thu 03 | 0 | 0.0 | 199 ms | 0 |
| Thu 05 | 0 | 0.0 | 220 ms | 0 |
| Thu 06 | 0 | 0.0 | 225 ms | 0 |
| Thu 08 | 0 | 0.0 | 159 ms | 0 |
| Thu 10 | 0 | 0.0 | 116 ms | 0 |
| Thu 12 | 0 | 0.0 | 253 ms | 0 |
| Thu 14 | 0 | 0.0 | 173 ms | 0 |
| Thu 16 | 0 | 0.0 | 250 ms | 0 |
| Thu 18 | 0 | 0.0 | 152 ms | 0 |
| Thu 19 | 0 | 0.0 | 218 ms | 0 |
| Thu 21 | 0 | 0.0 | 285 ms | 0 |
| Thu 23 | 0 | 0.0 | 206 ms | 0 |
| Fri 01 | 0 | 0.0 | 294 ms | 0 |
| Fri 03 | 0 | 0.0 | 194 ms | 0 |
| Fri 05 | 0 | 0.0 | 116 ms | 0 |
| Fri 07 | 0 | 0.0 | 186 ms | 0 |
| Fri 09 | 0 | 0.0 | 133 ms | 0 |
| Fri 10 | 0 | 0.0 | 101 ms | 0 |
| Fri 12 | 0 | 0.0 | 236 ms | 0 |
| Fri 14 | 0 | 0.0 | 112 ms | 0 |
| Fri 16 | 0 | 0.0 | 167 ms | 0 |
| Fri 18 | 0 | 0.0 | 182 ms | 0 |
| Fri 20 | 0 | 0.0 | 201 ms | 0 |
| Fri 22 | 0 | 0.0 | 43 ms | 0 |
| Sat 00 | 0 | 0.0 | 213 ms | 0 |
| Sat 01 | 0 | 0.0 | 82 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Aerospike Cloud 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 Aerospike Cloud goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Aerospike Cloud alerts to Slack, Discord or a webhook — free.
We track Aerospike Cloud (aerospike.com) as part of the AI group. Aerospike is the real-time database for AI, trusted in the world's most demanding environments. Consistent, available, and cost-efficient at any scale.
Aerospike Cloud publishes an official status page at status.aerospike.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 151 ms average, 43–236 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Aerospike Cloud incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
151 ms on average over the last 24 hours (43–236 ms).
Yes, at https://status.aerospike.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Aerospike Cloud here at once, the problem is on Aerospike Cloud's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Aerospike Cloud. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.