User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is Lexer 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 → lexer.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 13 min ago. Last stored result reached it in 48 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 17 | 0 | 0.0 | 94 ms | 0 |
| Mon 19 | 0 | 0.0 | 76 ms | 0 |
| Mon 21 | 0 | 0.0 | 91 ms | 0 |
| Mon 23 | 0 | 0.0 | 66 ms | 0 |
| Tue 01 | 0 | 0.0 | 74 ms | 0 |
| Tue 03 | 0 | 0.0 | 67 ms | 0 |
| Tue 05 | 0 | 0.0 | 103 ms | 0 |
| Tue 07 | 0 | 0.0 | 171 ms | 0 |
| Tue 09 | 0 | 0.0 | 71 ms | 0 |
| Tue 12 | 0 | 0.0 | 49 ms | 0 |
| Tue 14 | 0 | 0.0 | 52 ms | 0 |
| Tue 16 | 0 | 0.0 | 55 ms | 0 |
| Tue 18 | 0 | 0.0 | 73 ms | 0 |
| Tue 21 | 0 | 0.0 | 81 ms | 0 |
| Tue 23 | 0 | 0.0 | 33 ms | 0 |
| Wed 01 | 0 | 0.0 | 59 ms | 0 |
| Wed 03 | 0 | 0.0 | 117 ms | 0 |
| Wed 06 | 0 | 0.0 | 123 ms | 0 |
| Wed 08 | 0 | 0.0 | 49 ms | 0 |
| Wed 10 | 0 | 0.0 | 151 ms | 0 |
| Wed 12 | 0 | 0.0 | 70 ms | 0 |
| Wed 14 | 0 | 0.0 | 51 ms | 0 |
| Wed 16 | 0 | 0.0 | 108 ms | 0 |
| Wed 19 | 0 | 0.0 | 97 ms | 0 |
| Wed 21 | 0 | 0.0 | 97 ms | 0 |
| Wed 23 | 0 | 0.0 | 96 ms | 0 |
| Thu 01 | 0 | 0.0 | 103 ms | 0 |
| Thu 03 | 0 | 0.0 | 106 ms | 0 |
| Thu 05 | 0 | 0.0 | 76 ms | 0 |
| Thu 07 | 0 | 0.0 | 55 ms | 0 |
| Thu 09 | 0 | 0.0 | 67 ms | 0 |
| Thu 11 | 0 | 0.0 | 53 ms | 0 |
| Thu 14 | 0 | 0.0 | 88 ms | 0 |
| Thu 15 | 0 | 0.0 | 119 ms | 0 |
| Thu 17 | 0 | 0.0 | 79 ms | 0 |
| Thu 19 | 0 | 0.0 | 74 ms | 0 |
| Thu 21 | 0 | 0.0 | 71 ms | 0 |
| Thu 23 | 0 | 0.0 | 55 ms | 0 |
| Fri 01 | 0 | 0.0 | 75 ms | 0 |
| Fri 03 | 0 | 0.0 | 58 ms | 0 |
| Fri 05 | 0 | 0.0 | 87 ms | 0 |
| Fri 07 | 0 | 0.0 | 67 ms | 0 |
| Fri 09 | 0 | 0.0 | 51 ms | 0 |
| Fri 11 | 0 | 0.0 | 44 ms | 0 |
| Fri 13 | 0 | 0.0 | 41 ms | 0 |
| Fri 15 | 0 | 0.0 | 152 ms | 0 |
| Fri 17 | 0 | 0.0 | 113 ms | 0 |
| Fri 19 | 0 | 0.0 | 48 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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Lexer 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 Lexer yet. Outages of 10 minutes or more get their own page here.
Having trouble with Lexer?
One report per service every 10 minutes from this network. No account.
Follow Lexer
Get an email when Lexer goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Lexer alerts to Slack, Discord or a webhook — free.
About Lexer
Lexer, at lexer.io, is one of the Productivity services we monitor. Ask your customer data anything. Lexi brings every source into one trusted view, so any team can find, build and activate audiences.
Lexer publishes an official status page at status.lexer.io; when we can read it, its incident level is folded into the status shown here.
Common problems for 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: 71 ms average, 41–152 ms range across 13 successful checks.
Questions
Is Lexer down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Lexer last down?
We have not recorded a public Lexer incident since monitoring began 8 days ago.
What is Lexer's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Lexer respond?
71 ms on average over the last 24 hours (41–152 ms).
Does Lexer have an official status page?
Yes, at https://status.lexer.io.
Lexer 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 productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Lexer here at once, the problem is on Lexer'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 Lexer. 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.