Hi!
In my scenario I have a webhook that takes +3 seconds to receive 400B of data. Why is this?
I’m currently in the Core plan, if I move to the Pro will it solve it?
I need to acknowledge the request under 3 seconds, but sometimes I’m unable to.
In this example it took 5 seconds.
Thanks!
Hello @eliassilva,
I can’t speak much to this, but I really don’t think changing to another plan will help this issue.
I am very curious, though, to know what service requires a response in under 3 seconds.
Why can’t you extend the response time requirement with that service?
Hi @Donald_Mitchell!
I thought it might be helpful since the PRO plan offers priority execution. Maybe?
The service that requires a response within 3 seconds is Slack: Slack API – Acknowledgment response
I’m building a complex bot that handles interactions with multiple users and sends them actions and buttons to interact with.
Interesting…maybe you can find a service that can receive the event, respond quickly, then forward the payload to your Make webhook for all the subsequent processing?
As of late the make.com US1 webhook response time has been lacking, and have seen quite a few errors or timeouts. Is this a scaling issue as make.com gets more popular? I’d like to get back to the bulletproof processing times that I used to know late last year… further to add to that the make.com status shows partial outages OFTEN for the US1. This needs fixing, I know that 99.88% uptime is pretty good, but it appears that the .12% of downtime is affecting me quite a bit on time of processing!
Yes I can see the spikes etc. but what i’m referring to is an ongoing issue since almost the beginning of this year. Its intermittent and causing my scenarios to run very slow, everything inbetween the hooks runs fast! 
Agree, the webhook response time is really bad. I’m integrating it with voice chat, and waiting 5 seconds and then timing out becomes really problematic.
I also want to add my voice, Webhooks on the make platform is unreliable
Unfortunately there is not much we can do about it on this forum except to highlight the current problems with webhooks.
For technical issues like this, we should always directly contact support for a faster resolution. They have access to server-side logs and internal tools, which will allow them to investigate more thoroughly than what we have access to.
Everyone should open a new ticket to raise the priority of the issue, or if you are unable to login for some reason, you can create another new free account to access the ticketing system (which is only available to logged-in users).
You can also join us in my Discord server to live chat with other makers!
@here Hello everyone, thank you for raising this here in the community.
We were experiencing a delay in Webhook responses on our us1.make.com zone yesterday. However, the situation should now be stable. You can check our status page here: https://status.make.com. Feel free to let us know if the situation has improved for you.
We genuinely apologize for any disruptions, inconvenience, and frustrations this may have caused.
Thank you very much for your understanding. 
As illustrated in the image, this problem is not confined to a single day or a specific issue like webhooks. The us1.make.com server is consistently the worst performer, causing disruptions every few hours.
For those of us who have built entire workflows and systems on top of Make, these constant issues are absolutely unacceptable. Our processes are severely impacted, leading to significant negative consequences for our operations.
This situation is untenable, and we demand immediate action. It’s high time to add or upgrade a new server for the US to ensure reliable infrastructure. We need assurance that our workflows can run without these persistent interruptions.
Hello @Sam_Krausz
Once again, we are truly sorry for the disruptions and trouble caused.
We have experienced unexpected growth in our US zone and we are actively working to expand the zone’s capabilities. In particular, our engineering team is implementing several performance optimizations and adjusting our cloud infrastructure setup to address the bottlenecks that you have unfortunately experienced. Additionally, we are exploring new solutions to better manage user demand in the future.
Thank you very much for your patience and understanding throughout this process.
We are back in business, but once again, US1 is affected. Why are we facing these disruptions repeatedly?
We demand more effective solutions to manage user demand and ensure stable performance. It’s time for these recurring problems to be resolved.
Hello again @Sam_Krausz, I wanted to share an important message from our team regarding the recent performance issues you’ve encountered:
Dear Sam,
The stability of our platform and the user experience are extremely important to us. Recently, we have experienced multiple performance issues and incidents affecting the US1 zone. We understand the inconvenience this has caused and appreciate your patience as we work to resolve these issues.
One of the recent errors was due to a bug that occurred in an edge-case scenario, making it almost impossible to capture through non-production tests. We are pleased to inform you that this bug has now been fixed.
In addition to addressing this specific issue, we have implemented several technical improvements to enhance overall performance and scenario execution stability. While the situation has remained stable for the past few days, we are further investing our capabilities into optimizing the platform for further scale.
Thank you for your patience and understanding!
Finally, us2.make.com has arrived! With this new server in town, we’ll experience fewer interruptions and smoother operations.
