Linear incident: Delayed actions for Linear agent and loops automations

1. resolvedAug 19, 2026, 15:42 UTC

   Automated actions, including Loop automations and Linear Agent responses, are now processing normally. We’re taking steps to help prevent this from recurring.

2. investigatingAug 19, 2026, 15:26 UTC

   Some customers may experience delayed responses from Linear agent and delayed runs for automated actions through Loops. We're investigating this issue now and will share an update as soon as possible.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Linear's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• DigitalOcean: Major Service Interruption in MKC1Critical · Aug 19, 2026, 11:10 UTC
• Elasticsearch: Elasticsearch 9.5.1: false-positive matches in certain boolean queriesMajor · Aug 14, 2026, 09:22 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Supabase: Sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projectsMinor · Aug 19, 2026, 12:47 UTC
• Cursor: Increased error rates for Composer 2.5Minor · Aug 19, 2026, 12:52 UTC

How often does Linear have incidents?

Linear reported 5 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 1h 6m. See Linear's uptime and incident history