Surge is down, surge.sh id down

[valerii15298]

The website surge.sh is down and does not open

surge cli does not work either:

Error: getaddrinfo ENOTFOUND surge.surge.sh
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:122:26) {
  errno: -3008,
  code: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: 'surge.surge.sh'
}

[fu-sen]

I had also detected server anomalies for several hours.
However, the current issue seems to be occurring throughout Surge.

fo.surge.sh 138.197.235.123 US, San Francisco
000 Could not resolve host: sfo.surge.sh

lhr.surge.sh 46.101.67.123 GB, London
000 Could not resolve host: lhr.surge.sh

yyz.surge.sh 159.203.50.177 CA, Toronto
000 Resolving timed out after 15000 milliseconds

jfk.surge.sh 159.203.159.100 US, New York
000 Could not resolve host: jfk.surge.sh

ams.surge.sh 188.166.132.94 NL, Amsterdam
000 Could not resolve host: ams.surge.sh

fra.surge.sh 138.68.112.220 DE, Frankfurt
000 Could not resolve host: fra.surge.sh

sgp.surge.sh 139.59.195.30 SG, Singapore
000 Resolving timed out after 15001 milliseconds

blr.surge.sh 139.59.50.135 IN, Bangalore
000 Resolving timed out after 15000 milliseconds

syd.surge.sh 45.76.126.95 AU, Sydney
000 Could not resolve host: syd.surge.sh

nrt.surge.sh 172.104.96.133 JP, Tokyo
000 Could not resolve host: nrt.surge.sh

My surge command has the same issue.

$ surge

/home/balloon/.local/opt/node-v24.4.1/lib/node_modules/surge/lib/util/helpers.js:158
      if (e) throw e
             ^

Error: getaddrinfo ENOTFOUND surge.surge.sh
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:122:26) {
  errno: -3008,
  code: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: 'surge.surge.sh'
}

Node.js v24.4.1

[Gorb]

Can confirm, this is still down.

[fu-sen]

Yes. Currently, Surge appears to have the entire server down.

sfo.surge.sh 138.197.235.123 US, San Francisco
000 Could not resolve host: sfo.surge.sh

lhr.surge.sh 46.101.67.123 GB, London
000 Could not resolve host: lhr.surge.sh

yyz.surge.sh 159.203.50.177 CA, Toronto
000 Could not resolve host: yyz.surge.sh

jfk.surge.sh 159.203.159.100 US, New York
000 Resolving timed out after 15001 milliseconds

ams.surge.sh 188.166.132.94 NL, Amsterdam
000 Resolving timed out after 15000 milliseconds

fra.surge.sh 138.68.112.220 DE, Frankfurt
000 Could not resolve host: fra.surge.sh

sgp.surge.sh 139.59.195.30 SG, Singapore
000 Could not resolve host: sgp.surge.sh

blr.surge.sh 139.59.50.135 IN, Bangalore
000 Could not resolve host: blr.surge.sh

syd.surge.sh 45.76.126.95 AU, Sydney
000 Resolving timed out after 15001 milliseconds

nrt.surge.sh 172.104.96.133 JP, Tokyo
000 Could not resolve host: nrt.surge.sh

It has no response from the name server level.

$ nslookup surge.sh 8.8.8.8
;; communications error to 8.8.8.8#53: timed out
;; communications error to 8.8.8.8#53: timed out
;; communications error to 8.8.8.8#53: timed out
;; no servers could be reached

$ nslookup surge.sh 1.1.1.1
;; Got SERVFAIL reply from 1.1.1.1
Server:		1.1.1.1
Address:	1.1.1.1#53

** server can't find surge.sh: SERVFAIL

[b-xb]

Hi all, I only noticed this issue of surge.sh being down for me today.
The last record I have of having no problems at all is at roughly 4am GMT on 29th September 2025.

After a bit of sleuthing I have managed to access the main site, my app site and use the command line again.

To do so I added the following lines to my /etc/hosts file

159.203.50.177 surge.sh
192.241.214.148 surge.surge.sh
192.241.214.148 my-app.surge.sh

After pushing my website changes using the command line, my app site isn't updating however.

Definitely seems to be a DNS issue.

I also noticed, in my sleuthing, that surge.world is due to expire in a couple of weeks time.

https://uk.godaddy.com/whois/results.aspx?itc=dlp_domain_whois&domain=surge.world

surge.world is listed as the domain name being used to point to the nameservers for surge.sh

https://uk.godaddy.com/whois/results.aspx?itc=dlp_domain_whois&domain=surge.sh

I hope this info helps.

[b-xb]

When I say I am able to use the command line (after editing /etc/hosts) here is a (partially redacted) screenshot of the results I got back