Updates to Bitbucket webhook infrastructure

We are making changes to Bitbucket webhooks to improve the reliability and scalability of the infrastructure. These changes should be mostly transparent, however it is important to note that webhooks might be sent from a different range of IPs than they have been in the past as highlighted in this blog post.

Most users will not have to do anything to continue receiving webhooks. Users with services behind firewalls might want to double check whether their firewall rules include the full list of addresses. The full list of Atlassian IP ranges can be found here: https://ip-ranges.atlassian.com/

As always, please contact our support team if you have further questions or if you need further assistance.

1 Like

Hello Jeroen,

I am hoping you can provide some quick insight for my question.
We are using Bitbucket Enterprise server solution at work.

I have set a CICD to launch a webhook on a commit. This all works fine but once a while the webhook gets busy or rare network glitch and the pipe fails …

I was wondering how can i have bitbucket report to me when a webhook fails to launch ?.. i could not find any mechanism for it.

thanks for your time