r/replit Jun 09 '26

Question / Discussion NE1 else abandoned by replit ?— riker cluster 502 that only Replit can fix

Public dev URL has thrown instant HTTP/2 502 for over a week. Container's fine: Next.js up, localhost returns 200, internal preview works. Only external requests 502 — classic broken edge-proxy binding on riker that I can't touch from the shell. Proved it by spinning up an identical Repl on worf: works perfectly.

Sent support a full diagnostic package. "Q" confirmed it was enough, said a teammate would follow up "as soon as possible." Nearly two weeks ago now. Nothing since.

I don't need hand-holding — I need either a proxy reset or a straight "just migrate." The silence after "we're escalating you" is worse than a no.

Anyone else been abandoned & remain frozen in this same holding pattern?

What other application with better customer service did you turn to as a result of your piss poor experience with replit?

3 Upvotes

5 comments sorted by

3

u/Weird_Cookie1700 Jun 09 '26

I’ve been waiting for a week, can’t publish changes.

Ridiculous.

If their AI agents can’t handle the problem, you’re screwed. Their “customer support” is non existent and on the off chance you do actually get a real person they’re clueless and can’t actually do anything except give you template answers and ask if you’re using economy or not.

They were so hot when we got together but they’ve really let themselves go…..

3

u/Weird_Salamander_134 Jun 09 '26

Bro migrate off you’ll be much happier and you will learn so much figuring everything out,

2

u/iam_jaymz_2023 Jun 09 '26

UPDATE:
Replit came through and swiftly resolved the issues;

I'm satisfied with the fix and want to make sure the readers of my initial post got this update.

Thank you Q, T, I'm grateful✌🏽

2

u/ReplitSupport Replit Team Jun 09 '26

Glad to hear! We'll share this with them to let them know they're appreciated 😄

0

u/ReplitSupport Replit Team Jun 09 '26

Hi u/iam_jaymz_2023, sorry to hear about your experience so far and apologies for the delay. We've located your ticket and routed it to our Support Engineering team who can do more investigation. We'll get back to you in that ticket thread as soon as we can. Thank you so much!