API calls longer than expected after netlify outage

Hi, @ragazzid. From the technical support side of things, I’m missing important information required to troubleshoot.

I use the analogy of me being a veterinarian and the issue being a sick horse. If I cannot see the sick horse, I cannot tell you why it is sick. In this case, the “sick horse” would be the slow API call. I need as much information about that API call as possible to troubleshoot.

Now, if the HTTP response is not being routed via Netlify, then you are chasing a red herring. Nothing at Netlify could impact a third-party API hosted elsewhere.

If, on the other hand, the HTTP response does route through Netlify, what we would need to identify the slow response is the x-nf-request-id HTTP response header for the slow response. We have a support guide about that header here:

If the header is not available we need the following details to troubleshoot:

  • the full URL requested
  • the client IP address making the HTTP request
  • the server IP address responding to the request
  • the date, time, and timezone of the request

With that information we can research the issue to see what the reason is for the slowness.

If there are questions about how to gather any of this information or why we require it, please let us know.

1 Like