Incident on 30th Sept 2:47 AM CEST

From Sep 30, 2022 02:47:09 until 02:53:49 CEST Sentry reported the following errors connecting to the Postgres database:

connection to server at “dpg-cahf9ukgqg49t4u99040-a” (10.202.215.156), port 5432 failed: Connection timed out. Is the server running on that host and accepting TCP/IP connections?

and

could not translate host name “dpg-cahf9ukgqg49t4u99040-a” to address: Name or service not known

The Postgres service itself doesn’t seem to have an issue at all. At the same time all three web service instances were reported unhealthy and were restarted:

Server unhealthy
Get “http://10.201.153.60:10000/”: context deadline exceeded (Client.Timeout exceeded while awaiting headers) while running your code.
September 30, 2022 at 2:49 AM

I had a look at https://status.render.com but there was no incident reported for the Frankfurt region. My application hasn’t seen a deploy for a few days and CPU and memory usage hadn’t been suspicious before the servers have been considered unhealthy.

Did someone else experience this? Is this an issue on Render’s part? How do I prevent this from happening?

1 Like

Did you find out what caused this? This morning the connection to Postgres was failing again from 08:15:43 CEST until 8:17:33 CEST

connection to server at “dpg-cahf9ukgqg49t4u99040-a” (10.202.89.237), port 5432 failed: Connection refused. Is the server running on that host and accepting TCP/IP connections?

All three instances were restarted and are healthy again since.

It is now two weeks since the initial report. Can you say what caused this and if this can occur in the future again?

It happened again. This time twice at 9:25 AM:

Server unhealthy

Get “http://10.201.208.194:10000/”: context deadline exceeded (Client.Timeout exceeded while awaiting headers) while running your code.

Even if you still don’t know what is going on I’d be relieved to know that you will have a look at this eventually. The lack of communication is concerning.

The problem still occurs:

Server unhealthy

Get “http://10.201.224.254:10000/”: context deadline exceeded (Client.Timeout exceeded while awaiting headers) while running your code.

November 2, 2022 at 5:07 PM

I have been seeing the same error a lot recently.

My frontend service (NextJS) repeatedly fails with

Get “http://10.201.104.155:10000/api/healthcheck”: context deadline exceeded (Client.Timeout exceeded while awaiting headers) while running your code.

Backend service (NestJS) does the exact same thing simultaneously with frontend one

Get “http://10.201.2.222:10000/api/healthcheck/v2”: context deadline exceeded (Client.Timeout exceeded while awaiting headers) while running your code.

Dear support staff, do you have any updates on this for us?

Hi we are also repeatedly running into this issue and it is disrupting customers. We aren’t seeing any errors/crashes in our logs, we just see this:

[Our URL]: context deadline exceeded (Client.Timeout exceeded while awaiting headers

Can we get a support response on this ASAP?