Hi Railway support,

I'm experiencing a critical database connectivity issue on my production service (strawberry-riff, Project ID: 760c7efe-6c84-44e9-8227-4f3b41fa118a). The app authenticates users via Clerk successfully but then fails immediately after, indicating the relational database is unreachable.

Current situation:

Service: strawberry-riff (running on Railway)

Database: TiDB Cloud at gateway05.us-east-1.prod.aws.tidbcloud.com:4000

Error: PROTOCOL_CONNECTION_LOST (connection reaches the gateway but immediately closes)

DATABASE_URL is set with root credentials, but I cannot access or verify the TiDB account

What I need from Railway:

Complete change history for the DATABASE_URL variable on this service, including:

Dates when it was modified

Timestamps of changes

Previous values (dates/times only, not the secrets themselves)

Audit trail or activity logs showing:

When the database connection was last working

Who made changes to DATABASE_URL and when

Whether you have any records of the original TiDB account creation (was it created by Railway, by me, or by a third party like Manus?)

Background: This service was previously dependent on the Manus.ai platform. During a migration off that platform, there may have been a hidden dependency that wasn't caught. When the Manus-Meta rollback occurred, the database connection may have broken. I have no historical backup files to reference.

I'm also unable to access the TiDB Cloud account directly (support portal is inaccessible and no support email is available), so the Railway audit trail is my best shot at figuring out what happened.

My S3 storage successfully migrated and all audio files are intact (~450 generated tracks, ~250 published), but the relational metadata (lyrics, prompts, track data) is locked inside this database. I need to either restore the connection or at least understand the change history so I can determine next steps.

Thank you.