Hello Railway Support,

I cannot retrieve historical HTTP logs for my production service, although recent HTTP logs and historical application logs remain accessible.

Service: mcp-x402

Environment: production

Deployment ID: c06c74da-fa37-4706-894b-5d7cbb47a62e

Operating system: Windows 11 / PowerShell

Railway CLI: 5.43.2

This command fails:

railway.cmd logs c06c74da-fa37-4706-894b-5d7cbb47a62e --http --service mcp-x402 --environment production --since 2026-08-24T15:44:11Z --until 2026-08-24T16:14:11Z --json

Result:

Problem processing request

The same error occurs:

• With 500, 1,000 and 3,000 lines.
• With and without the deployment ID.
• With --since and --until.
• With --until only.
• With a narrow 30-minute interval.
• After upgrading Railway CLI from 5.41.2 to 5.43.2.

Control tests:

• Retrieving the latest 500 HTTP logs works.
• Historical application logs for the same service work, including an export of 1,000 lines.
• The deployment is successful and the service is operating normally.
• The requested logs are approximately two days old and should be within the Hobby plan’s documented retention period.

This appears isolated to Railway’s historical HTTP-log query. I receive no HTTP 401 or 403 error, only “Problem processing request”.

I need these HTTP logs to correlate application events with Railway edge information, including request IDs, source IPs, user agents, regions, latency and requests that may have failed before reaching the application.

Could you please:

1. Confirm whether this is a known CLI or HTTP-log backend issue?
2. Confirm whether the historical HTTP logs still exist?
3. Provide a workaround or alternative export method?
4. Help me retrieve the logs for the affected period?

Thank you.