Linear incident: Increased failures and latency for Android push notifications

1. resolvedSep 1, 2026, 12:23 UTC

   Normal functionality has resumed.

2. monitoringSep 1, 2026, 10:27 UTC

   We're aware of upstream issues which may cause increased delays or failed delivery of Android push notifications primarily in the US region. We will continue to monitor the upstream providers status and keep our status site updated accordingly.

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.

• Supabase: User unable to log in to Supabase DashboardCritical · Sep 1, 2026, 08:45 UTC
• Sentry: Sentry requests timing out / 504'sMajor · Sep 1, 2026, 08:01 UTC
• Elasticsearch: Replication bug causing slow recoveriesMajor · Sep 1, 2026, 08:16 UTC
• Snowflake: INC20000190Major · Sep 1, 2026, 09:58 UTC
• OVHcloud: [EU-SOUTH-MIL][Containers & Orchestration] - Managed Private Registry incident notificationMinor · Aug 26, 2026, 15:00 UTC
• Snowflake: INC20000150Minor · Aug 28, 2026, 00:07 UTC
• Snyk: Partial Broker Service DegradationMinor · Aug 30, 2026, 14:32 UTC
• Zoom: Service Degradation Affecting Zoom Node.Minor · Sep 1, 2026, 00:11 UTC
• Expo: EAS background operations availability issuesMinor · Sep 1, 2026, 11:45 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