Website and dashboard take forever to load

1

Is there an issue with the dashboard and page? it’s taking forever to load, inspecting the network tab I’m seeing some 520 errors coming from https://render.com/page-data/app-data.json and the response body seems to be from cloudflare, I’m located in Mexico.

Screen Shot 2022-10-12 at 15.37.19
Screen Shot 2022-10-12 at 15.37.191920×999 125 KB

This has been happening since yesterday, not a great experience considering I was proposing using render to a client and the dashboard took ages to load, making it seem like an unreliable service.

The website eventually loaded after several minutes.

2

Now the main site is displaying this:

Screen Shot 2022-10-12 at 15.51.41
Screen Shot 2022-10-12 at 15.51.412272×1448 217 KB

Not seeing any open issues in the status page.

3

I’m also in Mexico and having the same issue. My ISP is Totalplay and seems its related to this.

4

That’s interesting, I also have Totalplay, what is weird is that cloudflare is reporting that the host is the one having issues.

5

Hey there - we have 3 customers from Mexico talking about this now, we’re reaching out to CloudFlare to see if they have an insight from their side

John B

6

Could you possible post results of traceroute dashboard.render.com here please.

John B

7

Hi John,
Thanks for debugging this. Please keep us posted.

Here is the info you requested. Im happy to help with anything else needed.

traceroute: Warning: dashboard.render. com has multiple addresses; using 216.24.57.253
traceroute to render-dashboard-2.onrender.com.cdn.cloudflare.net (216.24.57.253), 64 hops max, 52 byte packets
1 192.168.100.1 (192.168.100.1) 5.412 ms 3.672 ms 4.852 ms
2 172.24.0.1 (172.24.0.1) 7.048 ms 5.814 ms 6.410 ms
3 10.180.25.106 (10.180.25.106) 9.900 ms 7.688 ms 11.220 ms
4 10.180.25.81 (10.180.25.81) 6.690 ms 7.358 ms 5.894 ms
5 10.180.200.173 (10.180.200.173) 12.779 ms 14.935 ms 14.421 ms
6 fixed-187-190-77-251.totalplay.net (187.190.77.251) 46.507 ms 38.417 ms 39.037 ms
7 216.24.57.253 (216.24.57.253) 40.249 ms 38.074 ms 38.864 ms

8

Are you able to provide the output of traceroute 172.69.166.221 also please?

John B

9

traceroute 172.69.166.221
traceroute to 172.69.166.221 (172.69.166.221), 64 hops max, 52 byte packets
1 192.168.100.1 (192.168.100.1) 3.785 ms 4.016 ms 3.316 ms
2 172.24.0.1 (172.24.0.1) 4.077 ms 5.607 ms 5.565 ms
3 10.180.25.106 (10.180.25.106) 4.450 ms 4.253 ms 5.187 ms
4 10.180.25.81 (10.180.25.81) 5.567 ms 6.424 ms 4.788 ms
5 10.180.200.173 (10.180.200.173) 12.812 ms 14.251 ms 12.885 ms
6 fixed-187-190-77-251.totalplay.net (187.190.77.251) 37.384 ms 36.219 ms 39.221 ms
7 172.69.166.221 (172.69.166.221) 37.596 ms 36.928 ms 38.060 ms

10

traceroute 172.69.166.221
traceroute to 172.69.166.221 (172.69.166.221), 64 hops max, 52 byte packets
1 192.168.100.1 (192.168.100.1) 3.785 ms 4.016 ms 3.316 ms
2 172.24.0.1 (172.24.0.1) 4.077 ms 5.607 ms 5.565 ms
3 10.180.25.106 (10.180.25.106) 4.450 ms 4.253 ms 5.187 ms
4 10.180.25.81 (10.180.25.81) 5.567 ms 6.424 ms 4.788 ms
5 10.180.200.173 (10.180.200.173) 12.812 ms 14.251 ms 12.885 ms
6 fixed-187-190-77-251.totalplay.net (187.190.77.251) 37.384 ms 36.219 ms 39.221 ms
7 172.69.166.221 (172.69.166.221) 37.596 ms 36.928 ms 38.060 ms

11

traceroute 172.69.166.221
traceroute to 172.69.166.221 (172.69.166.221), 64 hops max, 52 byte packets
1 192.168.100.1 (192.168.100.1) 3.785 ms 4.016 ms 3.316 ms
2 172.24.0.1 (172.24.0.1) 4.077 ms 5.607 ms 5.565 ms
3 10.180.25.106 (10.180.25.106) 4.450 ms 4.253 ms 5.187 ms
4 10.180.25.81 (10.180.25.81) 5.567 ms 6.424 ms 4.788 ms
5 10.180.200.173 (10.180.200.173) 12.812 ms 14.251 ms 12.885 ms
6 fixed-187-190-77-251.totalplay. net (187.190.77.251) 37.384 ms 36.219 ms 39.221 ms
7 172.69.166.221 (172.69.166.221) 37.596 ms 36.928 ms 38.060 ms

I added a whitespace before net on totalplay URL as otherwise the automated spam filter doesn’t allow me to send my reply.

12

Still getting 520 errors as of today, my traceroutes are exactly the same as Andres_MB, maybe there’s a routing problem from Cloudflare’s Mexico server and your server?

13

This is what CloudFlare are investigating - it’s very targetted to the one Country/ISP and mostly connections to Google!

14

Hopefully it can be solved soon. As far as I know, this ISP has around 15-20% of the market share in Mexico.

15

Hi there - this should all be working now - CloudFlare confirmed there were networking issues between QRO (Queretaro) and MEX (Mexico city) which have now been resolved. How’s it been these past few days for you?

John B

16

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.