User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 1 hr ago. Last stored result reached it in 255 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 84 ms | 0 |
| Mon 15 | 0 | 0.0 | 199 ms | 0 |
| Mon 17 | 0 | 0.0 | 354 ms | 0 |
| Mon 20 | 0 | 0.0 | 204 ms | 0 |
| Mon 22 | 0 | 0.0 | 125 ms | 0 |
| Tue 00 | 0 | 0.0 | 191 ms | 0 |
| Tue 02 | 0 | 0.0 | 215 ms | 0 |
| Tue 04 | 0 | 0.0 | 122 ms | 0 |
| Tue 06 | 0 | 0.0 | 209 ms | 0 |
| Tue 08 | 0 | 0.0 | 178 ms | 0 |
| Tue 10 | 0 | 0.0 | 354 ms | 0 |
| Tue 12 | 0 | 0.0 | 148 ms | 0 |
| Tue 15 | 0 | 0.0 | 92 ms | 0 |
| Tue 17 | 0 | 0.0 | 89 ms | 0 |
| Tue 19 | 0 | 0.0 | 244 ms | 0 |
| Tue 21 | 0 | 0.0 | 46 ms | 0 |
| Wed 00 | 0 | 0.0 | 336 ms | 0 |
| Wed 02 | 0 | 0.0 | 333 ms | 0 |
| Wed 04 | 0 | 0.0 | 195 ms | 0 |
| Wed 06 | 0 | 0.0 | 157 ms | 0 |
| Wed 09 | 0 | 0.0 | 180 ms | 0 |
| Wed 11 | 0 | 0.0 | 83 ms | 0 |
| Wed 13 | 0 | 0.0 | 196 ms | 0 |
| Wed 15 | 0 | 0.0 | 174 ms | 0 |
| Wed 17 | 0 | 0.0 | 309 ms | 0 |
| Wed 19 | 0 | 0.0 | 343 ms | 0 |
| Wed 22 | 0 | 0.0 | 178 ms | 0 |
| Thu 00 | 0 | 0.0 | 260 ms | 0 |
| Thu 02 | 0 | 0.0 | 183 ms | 0 |
| Thu 04 | 0 | 0.0 | 218 ms | 0 |
| Thu 06 | 0 | 0.0 | 286 ms | 0 |
| Thu 08 | 0 | 0.0 | 184 ms | 0 |
| Thu 10 | 0 | 0.0 | 158 ms | 0 |
| Thu 12 | 0 | 0.0 | 88 ms | 0 |
| Thu 14 | 0 | 0.0 | 80 ms | 0 |
| Thu 16 | 0 | 0.0 | 214 ms | 0 |
| Thu 18 | 0 | 0.0 | 119 ms | 0 |
| Thu 21 | 0 | 0.0 | 185 ms | 0 |
| Thu 23 | 0 | 0.0 | 255 ms | 0 |
| Fri 01 | 0 | 0.0 | 81 ms | 0 |
| Fri 03 | 0 | 0.0 | 66 ms | 0 |
| Fri 05 | 0 | 0.0 | 82 ms | 0 |
| Fri 07 | 0 | 0.0 | 262 ms | 0 |
| Fri 09 | 0 | 0.0 | 99 ms | 0 |
| Fri 11 | 0 | 0.0 | 168 ms | 0 |
| Fri 12 | 0 | 0.0 | 546 ms | 0 |
| Fri 14 | 0 | 0.0 | 151 ms | 0 |
| Fri 17 | 0 | 0.0 | 255 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Localytics 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 Localytics goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Localytics alerts to Slack, Discord or a webhook — free.
Localytics, at localytics.com, is one of the Productivity services we monitor. CRM marketing is about strategy, creativity, and judgment. Localytics builds the agents that handle the rest.
Localytics publishes an official status page at status.localytics.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 174 ms average, 25–546 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Localytics incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
174 ms on average over the last 24 hours (25–546 ms).
Yes, at https://status.localytics.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Localytics here at once, the problem is on Localytics'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 Localytics. 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.