Worth flagging this alongside another current thread — "can't open postgres container side sheet with options" (redbirdma) — which describes the same core symptom (Postgres service panel won't open, other services work fine). Two independent reports of the same failure mode specifically on Postgres tiles is a stronger signal than either alone, so worth linking the two threads together for Railway.

The detail that stands out here is the "attention" warning badge on both tiles — that's likely the actual trigger, not a side effect. Railway's dashboard often tries to fetch extra metadata (e.g. a specific alert/health detail) to populate the side sheet when a service has an active warning state, and if that fetch fails or hangs, it can manifest exactly as "URL flickers, panel never renders" rather than a clean error.

A few things to check in the meantime:

What does the "attention" warning actually say if you hover/click the badge itself (not the tile) — does it show a tooltip or a distinct clickable element separate from the main service click target?

Browser console errors when clicking the tile (DevTools → Console/Network tab) — if the panel's data fetch is failing, it'll usually show a failed request there, which would confirm this is a metadata-fetch issue tied to the warning state rather than a generic rendering bug.

Since both DBs are functioning fine for actual traffic, this is very likely dashboard/API-layer only — not a database health issue — so no urgency on the database side while this gets sorted.

If you can share what the attention warning actually says, that'd probably be the fastest way to confirm the connection between the two.

Hi,

It's now "fixed". Nothing changed since then, but it opens.

The warnings were about security updates. One of them auto-applied in the meantime, yet I still couldn't open the panel.

I retried 5 minutes ago, both panels opened. I manually started the update on the other Postgres. It still opens after the manual update.

The cause is a total mystery.

Thanks for your contribution!

Apologies. It was a display bug which was preventing you from opening your panel (separate from the notice on the Postgres instance). This bug is now fixed, which is why it mysteriously started working. Sorry for the inconvenience. Let us know if you have further issues.