When webhooks stop pulling data, first verify your endpoint URL is correct and accessible, check for payload formatting errors, and ensure your server sends a successful (2xx) HTTP status code. [1]
While we maintain 99.9% uptime and cannot guarantee zero outages due to causes outside our reasonable control (including network infrastructure failures), webhook issues are often related to endpoint configuration rather than platform outages. [2]
Also check if you've hit the 50,000 record limit per webhook table, as this prevents new data from being added. [3]
If you still need help resolving your webhook issue, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any specific errors you’re encountering?
It did not help me at all. I mean the webhook was working until 8 am this morning. But since then I am getting the output as OK. If you can help me, I would be so grateful.
Hi Canga - thanks so much for reaching out. You're right that there was an outage earlier today, which may cause some latency issues, but as you mentioned seems like data is being pulled in from your webhook now. Are you facing any other issues?
Understood - apologies for the issues here, but we are tracking this issue. AWS has applied mitigations and is reporting signs of recovery, but some requests may still be processing as they work through a backlog. There is a AWS dashboard to view the current status of what's happening: https://health.aws.amazon.com/health/status
