User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
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 26 min ago. Last stored result reached it in 57 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 113 ms | 0 |
| Tue 01 | 0 | 0.0 | 67 ms | 0 |
| Tue 03 | 0 | 0.0 | 98 ms | 0 |
| Tue 05 | 0 | 0.0 | 86 ms | 0 |
| Tue 07 | 0 | 0.0 | 134 ms | 0 |
| Tue 10 | 0 | 0.0 | 55 ms | 0 |
| Tue 12 | 0 | 0.0 | 69 ms | 0 |
| Tue 14 | 0 | 0.0 | 77 ms | 0 |
| Tue 16 | 0 | 0.0 | 179 ms | 0 |
| Tue 18 | 0 | 0.0 | 104 ms | 0 |
| Tue 21 | 0 | 0.0 | 149 ms | 0 |
| Tue 23 | 0 | 0.0 | 102 ms | 0 |
| Wed 01 | 0 | 0.0 | 45 ms | 0 |
| Wed 03 | 0 | 0.0 | 155 ms | 0 |
| Wed 06 | 0 | 0.0 | 191 ms | 0 |
| Wed 08 | 0 | 0.0 | 115 ms | 0 |
| Wed 10 | 0 | 0.0 | 148 ms | 0 |
| Wed 12 | 0 | 0.0 | 81 ms | 0 |
| Wed 14 | 0 | 0.0 | 85 ms | 0 |
| Wed 16 | 0 | 0.0 | 82 ms | 0 |
| Wed 19 | 0 | 0.0 | 110 ms | 0 |
| Wed 21 | 0 | 0.0 | 70 ms | 0 |
| Wed 23 | 0 | 0.0 | 129 ms | 0 |
| Thu 01 | 0 | 0.0 | 144 ms | 0 |
| Thu 03 | 0 | 0.0 | 67 ms | 0 |
| Thu 05 | 0 | 0.0 | 87 ms | 0 |
| Thu 07 | 0 | 0.0 | 139 ms | 0 |
| Thu 09 | 0 | 0.0 | 68 ms | 0 |
| Thu 11 | 0 | 0.0 | 120 ms | 0 |
| Thu 14 | 0 | 0.0 | 107 ms | 0 |
| Thu 16 | 0 | 0.0 | 118 ms | 0 |
| Thu 18 | 0 | 0.0 | 257 ms | 0 |
| Thu 20 | 0 | 0.0 | 136 ms | 0 |
| Thu 22 | 0 | 0.0 | 206 ms | 0 |
| Fri 00 | 0 | 0.0 | 76 ms | 0 |
| Fri 02 | 0 | 0.0 | 78 ms | 0 |
| Fri 04 | 0 | 0.0 | 114 ms | 0 |
| Fri 06 | 0 | 0.0 | 108 ms | 0 |
| Fri 08 | 0 | 0.0 | 97 ms | 0 |
| Fri 10 | 0 | 0.0 | 85 ms | 0 |
| Fri 11 | 0 | 0.0 | 63 ms | 0 |
| Fri 12 | 0 | 0.0 | 71 ms | 0 |
| Fri 14 | 0 | 0.0 | 54 ms | 0 |
| Fri 16 | 0 | 0.0 | 240 ms | 0 |
| Fri 18 | 0 | 0.0 | 235 ms | 0 |
| Fri 20 | 0 | 0.0 | 104 ms | 0 |
| Fri 22 | 0 | 0.0 | 57 ms | 0 |
| Sat 00 | 0 | 0.0 | 109 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 Letta 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 Letta goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Letta alerts to Slack, Discord or a webhook — free.
We track Letta (letta.com) as part of the Cloud & developer group. Making machines that learn. Create stateful agents that remember everything, learn continuously, and improve themselves over time.
Letta publishes an official status page at status.letta.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 109 ms average, 54–240 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Letta incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
109 ms on average over the last 24 hours (54–240 ms).
Yes, at https://status.letta.com.
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 Letta here at once, the problem is on Letta'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 Letta. 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.