A server running your services experienced a hardware failure at around 22:53 UTC on Aug 20. Your workloads were automatically migrated to a healthy server, and both services in that project now show a successful deployment. The event is resolved, so your app should be back online - if it still appears down in Shopify, a hard refresh or reopening the app should pick up the restored connection.

I have done a hard refresh it is still not live - it was working fine before this ? so what is going on

app.keptr.io refused to connect.

The hardware failure is resolved and your service deployment is running, but your custom domain's DNS is not routing traffic to us, which is why the connection is being refused. The CNAME record pointing your subdomain to your Railway target appears to be missing or misconfigured in your Cloudflare DNS settings. Please check that a CNAME record for that subdomain exists and points to the Railway target shown on your service's domain settings page, and if you have Cloudflare proxy (orange cloud) enabled, try switching it to DNS-only (grey cloud) to test.

app.keptr.io

CNAME

THE CNNAME IS ADDED ALREADY AS I SAID BEFORE MY APP WAS WORKING FINE BEFORE THIS INCIDENT!!!!!! I DID NOT CHANGE ANYTHING!!!

Unfortunately we're having an incident with the host you're project is currently on and fixing it is going to take another hour.

Please accept my apologies we have several platform engineers investigating this right now. Will update here as I know more.

Your app is back up and its public URL is loading normally again. The cause was the hardware failure from the outage notice you received, not your DNS. You were right, your CNAME didn't need changing, and the earlier reply pointing you at it was wrong. Sorry about that, and for how long this took. Both keepra-app and keepra-db show healthy deployments now, so your Shopify app should be fully working.

Perfect, thank you so much!!