Letta Outage History

Letta is up right now

Pingoru has recorded 49 incidents for Letta: 49 in the last 12 months and 5 in the last 90 days.

Source: status.letta.com

49incidents recorded
49last 12 months
5last 90 days
11 minutestypical duration
Incidents per month
01020AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Letta in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026110 of 720 (0%)
May 202620 of 744 (0%)
June 202650 of 720 (0%)
July 202641 of 744 (0%)
August 202631 of 744 (0%)
September 202600 of 720 (0%)
October 202611 of 581 (0%)

Incidents, newest first

Minor October 8, 2026 Reports of Letta slowdowns 27m section-268263 (Inference API), section-268263 (General API)

Started Oct 08, 2026, 09:27 PM UTC· resolved Oct 08, 2026, 09:54 PM UTC

  1. investigating Oct 08, 2026, 09:27 PM UTC

    We are investigating issues related to Letta's inference performance

  2. resolved Oct 08, 2026, 09:54 PM UTC

    Should be resolved

Read the full incident report →

Major August 17, 2026 Letta API Outage 1h 4m section-268263 (General API)

Started Aug 17, 2026, 07:35 PM UTC· resolved Aug 17, 2026, 08:39 PM UTC

  1. investigating Aug 17, 2026, 07:35 PM UTC

    Investigating continued issues with Letta API

  2. resolved Aug 17, 2026, 08:39 PM UTC

    resolved

Read the full incident report →

Major August 17, 2026 Letta API outage 8m section-268263 (General API)

Started Aug 17, 2026, 07:20 PM UTC· resolved Aug 17, 2026, 07:28 PM UTC

  1. investigating Aug 17, 2026, 07:20 PM UTC

    We are investigating an issue related to errors relating to: cannot execute UPDATE in a read-only transaction

  2. resolved Aug 17, 2026, 07:28 PM UTC

    We have resolved!

Read the full incident report →

Minor August 13, 2026 app.letta.com recovered –

Started Aug 13, 2026, 06:33 AM UTC· resolved Aug 13, 2026, 06:33 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor July 27, 2026 General API recovered –

Started Jul 27, 2026, 09:55 PM UTC· resolved Jul 27, 2026, 09:55 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor July 16, 2026 Some users reporting issues... 4m section-268263 (Inference API)

Started Jul 16, 2026, 09:15 PM UTC· resolved Jul 16, 2026, 09:19 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major July 16, 2026 Messaging API unavailable 45m section-268263 (Inference API)

Started Jul 16, 2026, 08:25 PM UTC· resolved Jul 16, 2026, 09:10 PM UTC

  1. investigating Jul 16, 2026, 08:25 PM UTC

    Issues with messaging API

Read the full incident report →

Minor June 30, 2026 Investigating reports of se... – section-268263 (Inference API)

Started Jun 30, 2026, 12:16 AM UTC· resolved Jun 30, 2026, 12:16 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 22, 2026 Inference API recovered –

Started Jun 22, 2026, 07:35 AM UTC· resolved Jun 22, 2026, 07:35 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 14, 2026 Degraded service – section-268263 (Inference API)

Started May 14, 2026, 08:20 PM UTC· resolved May 14, 2026, 08:20 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 13, 2026 Degraded Usage – section-268263 (Inference API), section-268263 (General API)

Started Apr 13, 2026, 07:54 PM UTC· resolved Apr 13, 2026, 07:54 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor March 29, 2026 Degraded services – section-268263 (Inference API), section-268258 (app.letta.com)

Started Mar 29, 2026, 05:27 AM UTC· resolved Mar 29, 2026, 05:27 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major March 28, 2026 Partial outage (some agents... – section-268263 (Inference API), section-268258 (app.letta.com)

Started Mar 28, 2026, 01:12 AM UTC· resolved Mar 28, 2026, 01:12 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major March 27, 2026 Partial outage 1h 42m section-268263 (Inference API), section-268258 (app.letta.com)

Started Mar 27, 2026, 09:36 PM UTC· resolved Mar 27, 2026, 11:18 PM UTC

  1. investigating Mar 27, 2026, 09:36 PM UTC

    There are potentially some service interruptions due to a failure of a core provider, service should stabalize soon

Read the full incident report →

Minor March 10, 2026 Elevated 409s (conversation... – section-268263 (Inference API), section-268258 (app.letta.com)

Started Mar 10, 2026, 11:26 PM UTC· resolved Mar 10, 2026, 11:26 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor March 10, 2026 Issues with conversations – section-268263 (Inference API)

Started Mar 10, 2026, 10:08 PM UTC· resolved Mar 10, 2026, 10:08 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor February 23, 2026 Issues with inference on no... 4h 33m section-268263 (Inference API)

Started Feb 23, 2026, 07:57 PM UTC· resolved Feb 24, 2026, 12:30 AM UTC

  1. investigating Feb 23, 2026, 07:57 PM UTC

    Users using non-main agent conversations may experience 409/service related slowdowns and high latency. Users are advises to swap into the main or default conversation of their agent to unblock themselves in the meantime. We are looking into the cause.

Read the full incident report →

Major February 19, 2026 Partial outage for PRO users – section-268263 (Inference API)

Started Feb 19, 2026, 08:25 PM UTC· resolved Feb 19, 2026, 08:25 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major February 16, 2026 Partial outage on api.letta... 25m section-268263 (Inference API)

Started Feb 16, 2026, 11:39 PM UTC· resolved Feb 17, 2026, 12:04 AM UTC

  1. investigating Feb 16, 2026, 11:39 PM UTC

    Some users are reporting steps created after the initial step are getting unintentionally rate limited by our system. We are working on a patch for this

Read the full incident report →