User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
armazem.cloud · Cloud & developer
Our checks are failing. User reports are still near the baseline — active checks often catch this before crowd reports do.
Estimated fix: Not enough Armazem Cloud history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–12 h; 78 outages).
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.
Checks failing
Last checked 1 hr ago. Last stored result failed with HTTP 530.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 09:00 | 0 | 0.0 | 2272 ms | 0 |
| 11:00 | 0 | 0.0 | 1973 ms | 0 |
| 13:15 | 0 | 0.0 | 2158 ms | 0 |
| 15:15 | 0 | 0.0 | 1896 ms | 0 |
| 17:15 | 0 | 0.0 | 3047 ms | 0 |
| 19:30 | 0 | 0.0 | 1553 ms | 0 |
| 21:30 | 0 | 0.0 | — | 1 |
| 23:30 | 0 | 0.0 | 2466 ms | 0 |
| 01:30 | 0 | 0.0 | — | 1 |
| 01:45 | 0 | 0.0 | — | 1 |
| 02:00 | 0 | 0.0 | 2232 ms | 0 |
| 04:00 | 0 | 0.0 | — | 1 |
| 06:00 | 0 | 0.0 | 2750 ms | 1 |
92.54% 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 6 days of data so far, so the 90-day numbers fill in over time.
One report per service every 10 minutes from this network. No account.
Get an email when Armazem Cloud goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Armazem Cloud alerts to Slack, Discord or a webhook — free.
Armazem Cloud is listed in our Cloud & developer category and checked at armazem.cloud. Armazém Cloud - Infraestrutura que impulsiona o seu negócio. O Armazém Cloud é um data center com soluções de ponta para segurança dos seus dados.
Armazem Cloud publishes an official status page at status.armazem.cloud; 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: 92.54% over 6 days of checks. We logged 1 public incident since monitoring began 6 days ago.
Response time over the last 24 hours: 2261 ms average, 1553–3047 ms range across 9 successful checks.
Our checks are failing. User reports are still near the baseline — active checks often catch this before crowd reports do.
The most recent public incident we recorded started 2026-11-13 and lasted 4 h 36 min. 1 incident since monitoring began 6 days ago.
From our own checks: 92.54% over 6 days of checks.
2261 ms on average over the last 24 hours (1553–3047 ms).
Yes, at https://status.armazem.cloud.
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 Armazem Cloud here at once, the problem is on Armazem 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 Armazem 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.