Intercom destination got affected for all customer tiers.

What to do

• Check whether you use RudderStack Data Processing Pipeline (US), Data Processing Pipeline (EU) in eu, us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 31m it lasted.

  Anything that failed between 2024-07-15 12:23 UTC and 2024-07-15 13:54 UTC may need a replay.

• Subscribe to RudderStack's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=rudderstack works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from RudderStack 3

1. identifiedJul 15, 2024, 12:23 PM UTC

   We have identified that a Web Application Firewall (WAF) from Intercom's side is blocking requests when the User-Agent header is set to RudderLabs. Our team is actively working to resolve this issue as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience.

   provider

2. monitoringJul 15, 2024, 1:11 PM UTC

   The issue has been fixed, and we are currently monitoring it.

   provider

3. resolvedJul 15, 2024, 1:54 PM UTC

   This incident has been resolved. Incident timeline: 13th July, 11:15 PM (UTC) to 15th July, 11:10 AM (UTC)

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.