surge
surge copied to clipboard
sintaxi
surge.sh seems to be down?
Hi @sintaxi. Should we consider surge.sh to be abandoned? It's an amazing service but it's been very unreliable lately, here's the last 30 days:
Thanks!
@joanniclaborde Every year or two surge hits a new scaling issue that has to be worked through. The downtime above is for our Toronto datacenter only. For some reason (that is not yet understood) in that datacenter we are having a cache server that is crashing when it attempts to snapshot its data. It can be valuable to observe the problem and come up with solutions that make the system more fault tolerant. Perhaps I haven't address this issue with enough urgency and my poor communication doesn't help either. For that Im sorry.
@sintaxi Thanks for the quick update, it's appreciated! Do you have an approximate date when this issue should be fixed?
That's amazing, thanks! I'll keep you posted if I notice any more downtime.
Hi all. Still seeing a 503 when I visit surge.sh unfortunately. Any updates on when this will be more completely resolved?
Seems to be back up! I hope there is some protection against this kind of disturbance, it rarely happens but it hits hard when it does.
UPDATE: New edgenodes have been stood up in the Toronto location. Doing some QA before re-routing traffic.
Thank you so much @sintaxi , honestly, surge has superior UX, the simplicity and functionality are just too good, and it has been my go-to.
New Toronto Edgenode has been running flawlessly for 72h. Also spun up a new edgenode in London which has been running for 48h.
Going to close this ticket. Thank you all for the help and support.
Hi there, I am still getting 502 Bad gateway errors for my sites as well. Any updates?
Could be specific to your deployment or region, don't see the issue here.
On Sun, Oct 15, 2023, 11:14 a.m. kevinta893 @.***> wrote:
Hi there, I am still getting 502 Bad gateway errors for my sites as well. Any updates?
— Reply to this email directly, view it on GitHub https://github.com/sintaxi/surge/issues/513#issuecomment-1763420441, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMZAK5PJJUY2PX4BCX3JTLX7P4UJANCNFSM6AAAAAA5ETT2JQ . You are receiving this because you commented.Message ID: @.***>
I have no issues during deployment, but visiting my websites is hit or miss. Sometimes my browser will grab a few files and 50X error. Sometimes I'm lucky and the whole site loads in time before another error.
I confirmed with various users of my sites across the globe that they too are having the same issues.
I can confirm there has been issues with a couple of our North America locations. Changes have been made and I think we are through the worst of it. Please keep me posted with your findings for the coming week.
thanks, Brock
Im reopening this ticket until stability is confirmed by you all.
I was seeing 502 errors across all of my deployments for a few weeks (I'm based in Australia, if that makes a difference), but they're all fixed now and everything is working as expected. Thanks for your hard work!
Now getting a 504 Gateway Time-out: "The server didn't respond in time."
Same here and it was down yesterday for me as well. Had sent an email to support but no response. I wish they would at least post outages somewhere.
Yes but sadly Surge is not saying much.
UPDATE: not five minutes after posting this comment I got an update from Surge:
Apologies for not getting back to you sooner. We have been fighting off a wave of phishing campaigns on our platform and it has lead to our SFO datacenter being temporarily out of service. We are routing the traffic to our Toronto datacenter until we get the issue resolved.
The 40 second delay is caused from the deployment server trying to verify the deployment to the SFO location and timing out. We will look into improving that experience.
So I spoke too soon.