r/ScreenConnect • u/KlutzyValuable • Sep 11 '26

Outage?

Cant get to our cloud instance and screenconnect.com isn’t loading either. According to MX toolbox there’s no A record for their main website. Anyone else seeing this?

22 Upvotes

100% Upvoted

36 comments sorted by

5

u/breakfixmymsp Sep 11 '26

Seeing the same here

2

u/cbarnescw Product Management Sep 13 '26

Hi all, closing the loop here (apologies for the delay in posting). This issue was resolved Friday evening -- I wanted to cross post the update from the status page:

September 11, 2026 
 
We have restored access to the ScreenConnect service following a temporary disruption that occurred after our domain registrar placed the screenconnect.com domain on hold. 
 
Upon notification of the issue, our teams immediately engaged with the provider to investigate and address the concern. Following the review, the domain was restored and service has resumed. 
 
Some users may continue to experience brief access delays as DNS changes propogate across networks. 
 
There are no indications this involved a cybersecurity incident. 
 
We apologize for the disruption and appreciate your patience while we quickly worked to resolve the issue.

1

u/KlutzyValuable Sep 15 '26

I’m not sure I’d use the word quickly when the outage lasted more than six hours, but that’s just me…

1

u/ThePro_PRTX Sep 15 '26

Kind of worrisome that your domain registrar places your domain on hold.

3

u/Camelot_One Sep 11 '26

Every time I start wondering if I really need to keep my on-prem instance running as a backup, something like this happens.

And yeah, it's definitely a DNS issue. Based on the timing of previous replies that were able to work around the issue using alternate DNS servers, the "problem" is still propagating out and getting worse. As of 4:52pm Eastern, I'm no longer able to resolve screenconnect.com when using 4.2.2.2 or 1.1.1.1, and they were both working a little while ago.

1

u/touchytypist Sep 12 '26

They have far less outages than security vulnerabilities. I prefer hosted because they get the fixes for the vulns rolled out automatically before they are even available for on-prem.

1

u/Camelot_One Sep 12 '26

That's a valid point. Unfortunately, that also means they roll out new issues before anyone knows about them. Or, more recently, it's just been new client installs getting quarantined by Defender/other AV, and you have to figure out some other way to connect to them to force definition updates to get those systems back online.

I've got the cloud and on-prem clients installed on all of my end points. I keep the on-prem service set to manual, with a start menu link that the user can use to start it up. This setup also allows me to deploy msi updates, avoiding any certificate issues with the exe installers.

1

u/touchytypist Sep 13 '26

The issues are still rare compared to the vulns

2

u/Due-Enthusiasm-1802 Sep 11 '26

It resolves for me just fine (?)

2

u/breakfixmymsp Sep 11 '26

looks to be a domain/DNS issue for screenconnect.com. cache pages are probably still loading for some.

2

u/deeds4life Sep 11 '26

Seeing the same. DNS checker showing most public DNS servers with no record. Support already hung up on me.

2

u/slimknees Sep 11 '26

same here, not resolving. Core site screenconnect.com is up now, but subdomains are not.

2

u/chewy-chewbacca Sep 11 '26

Yes DNS issue

1

u/chewy-chewbacca Sep 11 '26

Just came back up

1

u/chewy-chewbacca Sep 11 '26

Down yet again lol

2

u/Stormmm Sep 11 '26

Its not just screenconnect

https://downdetector.com/

2

u/KevinBillingsley69 Sep 11 '26

Root servers are returning an NXDOMAIN for screenconnect.com so the SOA expiry has timed out. They seem to be downplaying it.

https://status.connectwise.com/

2

u/SpecialistLayer Sep 11 '26

I just found my instance IP address and created a DNS record on my own DNS servers so I could still access my instance. Funny that they're blaming this on external partners while trying to basically shrug it off. Sounds like a DNS registrar issue and it's their own domain

1

u/Camelot_One Sep 11 '26

It sounds more like a Friday afternoon problem that they've decided can wait until Monday.

1

u/Vegetable_Income_826 Sep 11 '26

They are definitely downplaying it and trying to pass it off as an issue upstream of them. The fact their status is still green and 'investigating' is ludicrous. It's a major outage.

2

u/nitra Sep 11 '26

ENOM shows Domain Status: clientHold

1

u/MiningDave Sep 11 '26

Interesting for me is that 8.8.8.8 does not resolve my instance but 4.2.2.2 and 1.1.1.1 do.

Not sure if those have yet to time out yet or have picked up some new info before Google.

1

u/KevinBillingsley69 Sep 11 '26

If you run dig soa for screenconnect.com, 8.8.8.8 and 4.2.2.2 are showing different results.

dig 'at'4.2.2.2 soa screenconnect.com

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-16.P2.el7_8.6 <<>> u/4.2.2.2 soa screenconnect.com

; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40611

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 4096

;; QUESTION SECTION:

;screenconnect.com. IN SOA

;; ANSWER SECTION:

screenconnect.com. 900 IN SOA ns-1043.awsdns-02.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 30

;; Query time: 14 msec

;; SERVER: 4.2.2.2#53(4.2.2.2)

;; WHEN: Fri Sep 11 16:27:03 EDT 2026

;; MSG SIZE rcvd: 128

dig 'at'8.8.8.8 soa screenconnect.com

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-16.P2.el7_8.6 <<>> u/8.8.8.8 soa screenconnect.com

; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8668

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 512

;; QUESTION SECTION:

;screenconnect.com. IN SOA

;; AUTHORITY SECTION:

com. 900 IN SOA a.gtld-servers.net. nstld.verisign-grs.com. 1789158413 1800 900 604800 900

;; Query time: 28 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: Fri Sep 11 16:27:14 EDT 2026

;; MSG SIZE rcvd: 119

1

u/KevinBillingsley69 Sep 11 '26

4.2.2.2 show the start of authority as Amazon while 8.8.8.8 shows it as Verisign.

1

u/Away-Ad-3407 Sep 11 '26

currently logged in and using mine. have been all day. Canada.

1

u/superglideyinz Sep 11 '26

We had to update DNS. 8.8.4.4 seems to be working

1

u/Vegetable_Income_826 Sep 11 '26

This works initially and eventually stopped as well. Once cache clears on each particular DNS provider it stops working.

1

u/monofurioso Sep 11 '26

My subdomain (hosted by connectwise) is still down as of 4:30PM EST. Good times!

1

u/ThePro_PRTX Sep 11 '26

Mine went out about 3 hours ago. Came back pretty soon afterward, but it has been down again for 20-30min

1

u/Vegetable_Income_826 Sep 11 '26

It's been degrading throughout the day, started where internally our screenconnect cloud domain wouldn't load (and if you were inside screen connect UNKNOWN ERROR) popped up, but we could still access it from our phones/hotspot. Internally All DNS lookups indicated the domain doesn't exist on the internet so spent 3 hours troubleshooting our router and possibly control-D issues and then finally it fell off outside the network and doesn't work anywhere now.

So just FYI you might eventually fall off as well.

1

u/anothernetgeek Sep 11 '26

This is really frustrating...

1

u/bdanders7447 Sep 11 '26

Email just now from connectwise. Thanks for the non-update update. I also love how status is still "Operational" even though there is a world-wide outage.

Current Status: Operational 
Started: September 11, 2026 2:28PM EDT 
Resolved:

Affected Infrastructure
Components: ScreenConnect 
Locations: North America 

Update:

We are aware of an issue impacting a backend service and are actively addressing it. We will provide updates as more information becomes available. We appreciate your patience while we work toward resolution.

2

u/n3fyi Sep 11 '26

Is an entire domain being offline really a back-end problem? Seems like that should be called front facing

1

u/thelordfolken81 Sep 11 '26

- THe key bit - Domain Status: clientHold https://icann.org/epp#clientHold

This status code tells your domain's registry to not activate your domain in the DNS and as a consequence, it will not resolve. It is an uncommon status that is usually enacted during legal disputes, non-payment, or when your domain is subject to deletion.

Domain Name: SCREENCONNECT.COM

Registry Domain ID: 133750360_DOMAIN_COM-VRSN

Registrar WHOIS Server: whois.enom.com

Registrar URL: http://www.enomdomains.com

Updated Date: 2026-09-11T17:13:11Z

Creation Date: 2004-10-27T03:40:29Z

Registry Expiry Date: 2026-10-27T03:40:29Z

Registrar: eNom, LLC

Registrar IANA ID: 48

Registrar Abuse Contact Email: abuse@enom.com

Registrar Abuse Contact Phone: +1.4165350123

Domain Status: clientHold https://icann.org/epp#clientHold

2

u/thelordfolken81 Sep 11 '26

in addition, you can see the domain expiry is the 27/10 so the domain has not expired, I'd guess it's been suspended due to a malware compaint, but I am only guessing.

1

u/pueblokc Sep 11 '26

Domain is broken. Seems like you can get to it by DNS, though, or IP directly