User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Telecom
Is Olarm 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 → olarm.com—
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 117 ms.
Official status
All clear
All systems operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 1735 ms | 0 |
| Mon 18 | 0 | 0.0 | 84 ms | 0 |
| Mon 20 | 0 | 0.0 | 116 ms | 0 |
| Mon 22 | 0 | 0.0 | 63 ms | 0 |
| Tue 00 | 0 | 0.0 | 51 ms | 0 |
| Tue 02 | 0 | 0.0 | 81 ms | 0 |
| Tue 05 | 0 | 0.0 | 83 ms | 0 |
| Tue 07 | 0 | 0.0 | 78 ms | 0 |
| Tue 09 | 0 | 0.0 | 81 ms | 0 |
| Tue 11 | 0 | 0.0 | 64 ms | 0 |
| Tue 13 | 0 | 0.0 | 86 ms | 0 |
| Tue 15 | 0 | 0.0 | 91 ms | 0 |
| Tue 18 | 0 | 0.0 | 140 ms | 0 |
| Tue 20 | 0 | 0.0 | 109 ms | 0 |
| Tue 22 | 0 | 0.0 | 60 ms | 0 |
| Wed 00 | 0 | 0.0 | 133 ms | 0 |
| Wed 03 | 0 | 0.0 | 87 ms | 0 |
| Wed 05 | 0 | 0.0 | 170 ms | 0 |
| Wed 07 | 0 | 0.0 | 50 ms | 0 |
| Wed 09 | 0 | 0.0 | 103 ms | 0 |
| Wed 12 | 0 | 0.0 | 81 ms | 0 |
| Wed 14 | 0 | 0.0 | 77 ms | 0 |
| Wed 16 | 0 | 0.0 | 143 ms | 0 |
| Wed 18 | 0 | 0.0 | 87 ms | 0 |
| Wed 20 | 0 | 0.0 | 124 ms | 0 |
| Wed 22 | 0 | 0.0 | 56 ms | 0 |
| Thu 01 | 0 | 0.0 | 101 ms | 0 |
| Thu 03 | 0 | 0.0 | 170 ms | 0 |
| Thu 05 | 0 | 0.0 | 114 ms | 0 |
| Thu 07 | 0 | 0.0 | 64 ms | 0 |
| Thu 09 | 0 | 0.0 | 89 ms | 0 |
| Thu 11 | 0 | 0.0 | 114 ms | 0 |
| Thu 13 | 0 | 0.0 | 276 ms | 0 |
| Thu 15 | 0 | 0.0 | 1376 ms | 0 |
| Thu 17 | 0 | 0.0 | 170 ms | 0 |
| Thu 19 | 0 | 0.0 | 1308 ms | 0 |
| Thu 21 | 0 | 0.0 | 183 ms | 0 |
| Thu 23 | 0 | 0.0 | 70 ms | 0 |
| Fri 01 | 0 | 0.0 | 148 ms | 0 |
| Fri 03 | 0 | 0.0 | 68 ms | 0 |
| Fri 06 | 0 | 0.0 | 1450 ms | 0 |
| Fri 08 | 0 | 0.0 | 72 ms | 0 |
| Fri 10 | 0 | 0.0 | 69 ms | 0 |
| Fri 12 | 0 | 0.0 | 96 ms | 0 |
| Fri 14 | 0 | 0.0 | 43 ms | 0 |
| Fri 16 | 0 | 0.0 | 37 ms | 0 |
| Fri 17 | 0 | 0.0 | 95 ms | 0 |
| Fri 19 | 0 | 0.0 | 117 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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Olarm 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 Olarm yet. Outages of 10 minutes or more get their own page here.
Having trouble with Olarm?
One report per service every 10 minutes from this network. No account.
Follow Olarm
Get an email when Olarm goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Olarm alerts to Slack, Discord or a webhook — free.
About Olarm
We track Olarm (olarm.com) as part of the Telecom group. Turn your existing alarm into a smart system you control from your phone. Works with Paradox, DSC, Texecom, IDS and more. Check if yours qualifies.
Olarm publishes an official status page at status.olarm.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with telecom services: no service or data, account and billing pages failing, and app sign-in problems.
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: 193 ms average, 37–1450 ms range across 13 successful checks.
Questions
Is Olarm down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Olarm last down?
We have not recorded a public Olarm incident since monitoring began 7 days ago.
What is Olarm's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Olarm respond?
193 ms on average over the last 24 hours (37–1450 ms).
Does Olarm have an official status page?
Yes, at https://status.olarm.com.
Olarm 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 telecom services, watch for no service or data, account and billing pages failing, and app sign-in problems. If many people report Olarm here at once, the problem is on Olarm'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 Olarm. 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.