Later incident

Reels Publishing & Intermittent Access Issues

Minor Resolved View vendor source →

Later experienced a minor incident on February 26, 2026 affecting Instagram and General Site and 1 more component, lasting 19h 8m. The incident has been resolved; the full update timeline is below.

Started
Feb 26, 2026, 05:14 PM UTC
Resolved
Feb 27, 2026, 12:22 PM UTC
Duration
19h 8m
Detected by Pingoru
Feb 26, 2026, 05:14 PM UTC

Affected components

InstagramGeneral SiteLogin/SignupScheduling

Update timeline

  1. monitoring Feb 26, 2026, 05:14 PM UTC

    We’re currently experiencing an issue impacting Instagram Reel & Stories publishing. Based on our investigation, this appears to stem from Meta’s API. We’re actively monitoring Meta for updates and will share more information as it becomes available. Earlier today, some users may have also experienced minor disruptions when logging into Later. This issue is now resolved. If you continue to experience any problems or have questions, please contact our support team through the chatbot on site.

  2. monitoring Feb 26, 2026, 08:19 PM UTC

    We’re currently experiencing issues with publishing video posts to Instagram, including both Reels and Stories. This appears to be related to an ongoing issue with Meta, and we’re continuing to monitor the situation closely while awaiting their resolution. If you experienced any disruptions when logging into Later earlier today, please try clearing your browser’s cache.

  3. monitoring Feb 26, 2026, 11:06 PM UTC

    We’re currently experiencing issues with publishing video posts to Instagram, including both Reels and Stories. This appears to be related to an ongoing issue with Meta, and we’re continuing to monitor the situation closely while awaiting their resolution. If you experienced any disruptions when logging into Later earlier today, please try clearing your browser’s cache.

  4. resolved Feb 27, 2026, 12:22 PM UTC

    We can confirm that publishing video posts to Instagram, including Reels and Stories, is now fully operational. Thank you for your patience while Meta addressed this issue.