Respond.io incident

N8N: Delay Performance in trigger and action

Major Resolved View vendor source →

Respond.io experienced a major incident on July 13, 2026 affecting Integrations (Integrations), lasting 3h 2m. The incident has been resolved; the full update timeline is below.

Started
Jul 13, 2026, 07:10 AM UTC
Resolved
Jul 13, 2026, 10:12 AM UTC
Duration
3h 2m
Detected by Pingoru
Jul 13, 2026, 07:10 AM UTC

Affected components

Integrations (Integrations)

Update timeline

  1. identified Jul 13, 2026, 07:10 AM UTC

    We are currently experiencing an issue affecting N8N where there is delay performance in trigger and action. Our team is actively investigating the situation. Some customers may experience delayed performance with N8N. We will provide further updates as soon as more information...

  2. investigating Jul 13, 2026, 08:00 AM UTC

    Our Engineering team has identified the root cause of the n8n delay affecting trigger and action performance . They are currently preparing a hotfix and working to expedite its release as quickly as possible. We will share another update as soon as more information becomes...

  3. resolved Jul 13, 2026, 10:12 AM UTC

    This incident has been resolved. The issue was caused by communication failures with affected webhook endpoints, which resulted in some webhook requests being rejected. Webhook deliveries are now processing normally, and we will continue to monitor the service to ensure...