I'll use it more consistently in the coming days to see how it works at different times of the day. Pages are loading slowly here but at least they're showing up ^^

3 July, ~18:30 CEST: Pages are loading slowly but everything is usable.

4 July, 22.49 CEST: 504 Gateway Time-out. The server didn't respond in time. @ruud@lemmy.world

6 July, 11:14 CEST: Pages are loading slowly but everything is usable. Making a post is extremely slow, almost feeling like it'll timeout before succeeding. (But it did succeed)

6 July, 15:28 CEST: Pages are loading slowly and it is not usable. Thumbnails are refusing to load. The timeline only loads a couple of posts before grinding into a halt. @ruud@lemmy.world

7 July, 12:07 CEST: Pages are loading slowly but everything is usable. Logging in with 2FA took 45+ seconds.

8 July, 03:54 CEST: Pages are loading slowly but everything is usable. An error box says logging in failed, immediately after successfully logging in. (It makes no difference, I can keep going)

8 July, 13:52 CEST: Timelines are loading moderately slowly, but everything is usable and it is the best performance I've observed so far since the upgrade.

12 July, 12:56 CEST: It feels extra slow today. No error messages or timeouts.

13 July, 10:08 CEST: Pages are loading slowly, but everything is usable. Logging in, loading the main timeline (i.e. the icon with boxes), and making a post all took 20-30 seconds to complete. Loading the profile, directory, calendar etc. was nearly instant. No error messages or timeouts.

16 July, 12:08 CEST: Logging in took 20-25 seconds, followed by a 10-second freeze. Loading timelines was also slow and was followed by the same freeze. For some reason loading metadata on a link while posting and making the post were both faster. Parts of the global navigation did not work, so I could not visit my own profile page.

17 July, 01:03 CEST: 504 Gateway Time-out. The server didn't respond in time. 503 Service Unavailable. No server is available to handle this request. @ruud@lemmy.world

17 July, 11:47 CEST: 503 Service Unavailable. No server is available to handle this request. @ruud@lemmy.world

I wrote a script to facilitate reporting the issues. You may find it at https://codeberg.org/gargle/check-friendica. Documentation is included.

Sat 19 Jul 17:15:35 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time. @ruud@lemmy.world

Sun 20 Jul 07:46:41 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time. @ruud@lemmy.world

Mon 21 Jul 15:03:13 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time. @ruud@lemmy.world

Tue Jul 22 07:45:11 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time. @ruud@lemmy.world

Wed Jul 23 09:06:20 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time.

Interesting! My script still reports "Wed 23 Jul 19:11:06 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time" but my browser does render all friendica.world pages. It's very slow though. My script queries api/statuses/public_timeline. If I change to api/externalprofile/show I get a 200 instead of a 504. I'll keep my script on api/statuses/public_timeline however..

Thu Jul 24 09:07:51 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time.

https://friendica.world/network initially gave a 504 Gateway Time-out in my webbrowser. https://friendica.world/profile/gargle works, and https://friendica.world/profile/gargle/conversations too. https://friendica.world/network (latest creation, latest post, and latest activity) work as well now. Tested at 9:15 CEST.

Tested again in my webbrowser at 9:30 CEST: https://friendica.world/network: 504 Gateway Time-out.

Fri 25 Jul 09:27:31 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time.

Sat 26 Jul 20:00:51 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time.

Sun 27 Jul 09:13:06 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time.

Mon Jul 28 11:20:33 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time.

https://friendica.world/network gives a 504 Gateway Time-out in my webbrowser every first attempt of the day. The second attempt however seems to work most of the last few days. My script always complains. 504 Gateway Time-out still appears in the webbrowser, but it's usable.

Tue Jul 29 08:45:19 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time.

https://friendica.world/network worked on first try today the 29th of July. It appears a bit slow, but usable.

Tue Jul 29 19:49:22 CEST 2025 : 503 : 503 Service Unavailable No server is available to handle this request.

Tue Jul 29 19:51:35 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time.

Thu 31 Jul 10:47:55 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time.

Thu Jul 31 21:56:11 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time.

https://friendica.world/network gave 504 Gateway Time-out in my webbrowser all day. https://friendica.world/profile/gargle gave a 504 Gateway Time-out in my webbrowser too. https://friendica.world/contacts shows the contacts, but the style sheet seems missing. Tested at 21:57 CEST.

Fri Aug 1 09:57:15 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time.

https://friendica.world/network worked first time in the browser today at 9:58 CEST.

Sat 2 Aug 10:01:35 CEST 2025 : 504 : 504 Gateway Time-out The server didn't respond in time.

https://friendica.world/network gave 504 Gateway Time-out in my webbrowser on the first try. https://friendica.world/profile/gargle worked right away in my webbrowser. https://friendica.world/contacts shows the contacts with proper style sheets, tested at 10:05 CEST. https://friendica.world/network in the webbrowser works too.

I'm using friendica.world more since the 6th of July. My first login on the 6th failed. Since then I haven't experienced any trouble logging in. Everything is usable since the 7th and performance is a lot better. I'll report back whenever I experience trouble.

things seem to work better now.