Issue: Custom domains failing with ERR_SSL_PROTOCOL_ERROR

Services Affected:zabriskie.app, clr.zabriskie.app

Diagnosis: Generated by Railway Agent

Custom domains are returning SSL protocol errors in all browsers across multiple devices. The issue appeared suddenly with no code changes or configuration updates on the user's end.

Investigation Findings:

• DNS records are correctly configured (ALIAS for zabriskie.app → trgxw7gd.up.railway.app; CNAME for clr.zabriskie.app → fc8tleko.up.railway.app)
• DNS records match exactly what Railway's dashboard shows
• However, both CNAME targets resolve to IP 66.33.22.72, which is not a valid Railway edge IP
• Railway's native domain (zabriskie-web-production.up.railway.app) works fine over HTTP, confirming services are healthy
• Services were restarted on 2026-05-06 with no improvement

Root Cause: The CNAME targets provided by Railway are resolving to a stale/inactive IP address, indicating a Railway infrastructure issue rather than a user configuration problem.

Action Required: Please investigate the DNS resolution for trgxw7gd.up.railway.app and fc8tleko.up.railway.app, and either restore them to active edge infrastructure or issue new CNAME targets.

I"m able to access your site just fine. Try accessing the site from an incognito window or a different device. Your browser might be caching stale data.

I've tried it across multiple devices in incognito windows and not (both Chrome and Safari.) I did just ask some others and they are able to access it, but not me. Perhaps there's some sort of caching issue or something in Xfinity network. It's definitely dead for me across three computers on Xfinity. Let me reboot everything here. (also tried dnscacheutil on the computers, didn't work either.)

This appears as to be an Xfinity issue. I'll follow up. Thanks.