User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
armosec.io · Cloud & developer
Is ARMO down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → armosec.io—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 278 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 355 ms | 0 |
| Mon 18 | 0 | 0.0 | 172 ms | 0 |
| Mon 20 | 0 | 0.0 | 259 ms | 0 |
| Mon 22 | 0 | 0.0 | 280 ms | 0 |
| Tue 00 | 0 | 0.0 | 168 ms | 0 |
| Tue 02 | 0 | 0.0 | 302 ms | 0 |
| Tue 05 | 0 | 0.0 | 218 ms | 0 |
| Tue 07 | 0 | 0.0 | 341 ms | 0 |
| Tue 09 | 0 | 0.0 | 225 ms | 0 |
| Tue 11 | 0 | 0.0 | 270 ms | 0 |
| Tue 13 | 0 | 0.0 | 345 ms | 0 |
| Tue 15 | 0 | 0.0 | 372 ms | 0 |
| Tue 18 | 0 | 0.0 | 387 ms | 0 |
| Tue 20 | 0 | 0.0 | 344 ms | 0 |
| Tue 22 | 0 | 0.0 | 331 ms | 0 |
| Wed 00 | 0 | 0.0 | 291 ms | 0 |
| Wed 03 | 0 | 0.0 | 295 ms | 0 |
| Wed 05 | 0 | 0.0 | 279 ms | 0 |
| Wed 07 | 0 | 0.0 | 308 ms | 0 |
| Wed 09 | 0 | 0.0 | 266 ms | 0 |
| Wed 12 | 0 | 0.0 | 352 ms | 0 |
| Wed 14 | 0 | 0.0 | 276 ms | 0 |
| Wed 16 | 0 | 0.0 | 369 ms | 0 |
| Wed 18 | 0 | 0.0 | 155 ms | 0 |
| Wed 20 | 0 | 0.0 | 259 ms | 0 |
| Wed 22 | 0 | 0.0 | 185 ms | 0 |
| Thu 00 | 0 | 0.0 | 280 ms | 0 |
| Thu 03 | 0 | 0.0 | 193 ms | 0 |
| Thu 05 | 0 | 0.0 | 289 ms | 0 |
| Thu 07 | 0 | 0.0 | 285 ms | 0 |
| Thu 09 | 0 | 0.0 | 271 ms | 0 |
| Thu 11 | 0 | 0.0 | 178 ms | 0 |
| Thu 13 | 0 | 0.0 | 207 ms | 0 |
| Thu 15 | 0 | 0.0 | 314 ms | 0 |
| Thu 17 | 0 | 0.0 | 255 ms | 0 |
| Thu 19 | 0 | 0.0 | 273 ms | 0 |
| Thu 21 | 0 | 0.0 | 265 ms | 0 |
| Thu 23 | 0 | 0.0 | 326 ms | 0 |
| Fri 01 | 0 | 0.0 | 256 ms | 0 |
| Fri 03 | 0 | 0.0 | 163 ms | 0 |
| Fri 05 | 0 | 0.0 | 265 ms | 0 |
| Fri 07 | 0 | 0.0 | 281 ms | 0 |
| Fri 09 | 0 | 0.0 | 362 ms | 0 |
| Fri 11 | 0 | 0.0 | 253 ms | 0 |
| Fri 13 | 0 | 0.0 | 141 ms | 0 |
| Fri 15 | 0 | 0.0 | 270 ms | 0 |
| Fri 17 | 0 | 0.0 | 247 ms | 0 |
| Fri 18 | 0 | 0.0 | 278 ms | 0 |
Reliability
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 6 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live ARMO badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for ARMO yet. Outages of 10 minutes or more get their own page here.
Having trouble with ARMO?
One report per service every 10 minutes from this network. No account.
Follow ARMO
Get an email when ARMO goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ARMO alerts to Slack, Discord or a webhook — free.
About ARMO
We track ARMO (armosec.io) as part of the Cloud & developer group. Zero-day and every day protection for your cloud applications with a complete explainable & traceable runtime security story.
ARMO publishes an official status page at status.armosec.io; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 259 ms average, 141–362 ms range across 12 successful checks.
Questions
Is ARMO down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was ARMO last down?
We have not recorded a public ARMO incident since monitoring began 6 days ago.
What is ARMO's uptime?
From our own checks: 100% over 6 days of checks.
How fast does ARMO respond?
259 ms on average over the last 24 hours (141–362 ms).
Does ARMO have an official status page?
Yes, at https://status.armosec.io.
ARMO not working for me but the status is fine. What now?
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 ARMO here at once, the problem is on ARMO'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 ARMO. 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.