User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
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 54 min ago. Last stored result reached it in 295 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 09 | 0 | 0.0 | 223 ms | 0 |
| Tue 11 | 0 | 0.0 | 308 ms | 0 |
| Tue 13 | 0 | 0.0 | 290 ms | 0 |
| Tue 15 | 0 | 0.0 | 273 ms | 0 |
| Tue 18 | 0 | 0.0 | 289 ms | 0 |
| Tue 20 | 0 | 0.0 | 335 ms | 0 |
| Tue 22 | 0 | 0.0 | 314 ms | 0 |
| Wed 00 | 0 | 0.0 | 304 ms | 0 |
| Wed 03 | 0 | 0.0 | 277 ms | 0 |
| Wed 05 | 0 | 0.0 | 356 ms | 0 |
| Wed 07 | 0 | 0.0 | 293 ms | 0 |
| Wed 10 | 0 | 0.0 | 290 ms | 0 |
| Wed 12 | 0 | 0.0 | 263 ms | 0 |
| Wed 14 | 0 | 0.0 | 253 ms | 0 |
| Wed 16 | 0 | 0.0 | 296 ms | 0 |
| Wed 18 | 0 | 0.0 | 277 ms | 0 |
| Wed 20 | 0 | 0.0 | 281 ms | 0 |
| Wed 22 | 0 | 0.0 | 292 ms | 0 |
| Thu 01 | 0 | 0.0 | 240 ms | 0 |
| Thu 03 | 0 | 0.0 | 303 ms | 0 |
| Thu 05 | 0 | 0.0 | 307 ms | 0 |
| Thu 07 | 0 | 0.0 | 266 ms | 0 |
| Thu 09 | 0 | 0.0 | 284 ms | 0 |
| Thu 11 | 0 | 0.0 | 278 ms | 0 |
| Thu 13 | 0 | 0.0 | 247 ms | 0 |
| Thu 15 | 0 | 0.0 | 323 ms | 0 |
| Thu 17 | 0 | 0.0 | 348 ms | 0 |
| Thu 19 | 0 | 0.0 | 277 ms | 0 |
| Thu 21 | 0 | 0.0 | 315 ms | 0 |
| Thu 23 | 0 | 0.0 | 348 ms | 0 |
| Fri 01 | 0 | 0.0 | 272 ms | 0 |
| Fri 03 | 0 | 0.0 | 272 ms | 0 |
| Fri 06 | 0 | 0.0 | 277 ms | 0 |
| Fri 08 | 0 | 0.0 | 263 ms | 0 |
| Fri 10 | 0 | 0.0 | 255 ms | 0 |
| Fri 12 | 0 | 0.0 | 322 ms | 0 |
| Fri 14 | 0 | 0.0 | 279 ms | 0 |
| Fri 16 | 0 | 0.0 | 263 ms | 0 |
| Fri 17 | 0 | 0.0 | 266 ms | 0 |
| Fri 18 | 0 | 0.0 | 335 ms | 0 |
| Fri 19 | 0 | 0.0 | 271 ms | 0 |
| Fri 21 | 0 | 0.0 | 245 ms | 0 |
| Fri 23 | 0 | 0.0 | 268 ms | 0 |
| Sat 01 | 0 | 0.0 | 273 ms | 0 |
| Sat 03 | 0 | 0.0 | 287 ms | 0 |
| Sat 05 | 0 | 0.0 | 390 ms | 0 |
| Sat 07 | 0 | 0.0 | 280 ms | 0 |
| Sat 09 | 0 | 0.0 | 295 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Apura 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 Apura goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Apura alerts to Slack, Discord or a webhook — free.
Apura is listed in our Cloud & developer category and checked at apura.io. Protecting your digital infrastructure with cutting-edge threat detection and response. Featuring BTTng and BTTli - next-generation security products.
Apura publishes an official status page at status.apura.io; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 286 ms average, 245–390 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Apura incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
286 ms on average over the last 24 hours (245–390 ms).
Yes, at https://status.apura.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Apura here at once, the problem is on Apura'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 Apura. 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.