Is ConnectWise Down?

No — ConnectWise is up

Reachable from all 8 checked regions

Average response time: 715ms

Last checked 24 minutes ago · checks run every 6 hours

Official status page: https://status.connectwise.com

ConnectWise uptime

100%

Last 7 days

—

Last 30 days

—

Last 90 days

—

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 4 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

4-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ewr

292ms

DNS 199ms TCP 1ms TLS 9ms TTFB 283ms

fra

624ms

DNS 287ms TCP 3ms TLS 15ms TTFB 571ms

gru

708ms

DNS 426ms TCP 2ms TLS 8ms TTFB 659ms

iad

327ms

DNS 194ms TCP 1ms TLS 7ms TTFB 318ms

jnb

1302ms

DNS 573ms TCP 1ms TLS 8ms TTFB 1108ms

lax

477ms

DNS 156ms TCP 1ms TLS 9ms TTFB 444ms

lhr

1083ms

DNS 520ms TCP 3ms TLS 9ms TTFB 738ms

nrt

913ms

DNS 451ms TCP 1ms TLS 9ms TTFB 846ms

What ConnectWise does

ConnectWise makes software for managed service providers: PSA for ticketing and billing, RMM and Automate for managing client machines, ScreenConnect for remote access, and security products including SIEM and MDR, with backup and NOC and help desk services. An MSP's own clients depend on these tools indirectly, so an outage slows support for many businesses at once.

What an outage looks like

The ConnectWise Home portal or single sign-on fails, locking technicians out of several products at once. PSA tickets and time entries will not load or save. RMM or Automate agents stop reporting, so client machines appear offline when they are not. ScreenConnect sessions fail to connect. Backup jobs, SIEM alerts or billing runs stall depending on the product affected.

What to do about it

Read status.connectwise.com by product and region. ConnectWise lists each product, including CW Platform, PSA, RMM, Automate, ScreenConnect, SSO, SIEM, MDR and Cloud Backup, with separate status for APAC, EMEA and North America. Check SSO first when several tools fail together. If RMM is affected, do not act on offline-device alerts until it recovers, because the agents may be fine.

Is it down for everyone, or just you?

If this page says ConnectWise is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

ConnectWise outage FAQ

Why are all my ConnectWise tools failing at once?

Check the SSO and ConnectWise Home rows first. Those sit in front of several products, so a problem there locks technicians out of PSA, RMM and others at the same time even when each product is running. If SSO is operational and only one product is failing, the incident is in that product, and its own row on status.connectwise.com will say so.

Are my clients' machines really offline?

Not necessarily. If RMM or Automate is degraded on the status page, agents can stop reporting to the console while the machines themselves are running normally. Hold off on dispatching technicians or escalating to clients because of offline alerts until the component recovers, then check which devices are still missing.

Does ConnectWise report outages by region?

Yes. Each product on status.connectwise.com shows status for APAC, EMEA and North America, and some also show other regions or all regions. An incident in EMEA does not mean North American instances are affected, so find the row for the region your instance runs in before telling clients anything.

ScreenConnect will not connect. Is that ConnectWise?

Check the ScreenConnect row on the status page. If it shows an incident, sessions may fail from your side regardless of the client's machine. If it is operational, the cause is more likely on the remote end: the client's machine is off, its network blocks the connection, or the access agent is not running.

Is ConnectWise down for everyone or just me?

Compare the status page with this page's measurements. The status page is the authority for individual products, while our probes measure connectwise.com from several regions. If both look healthy, check your own network, VPN and identity provider before opening a ticket, since a sign-in failure often starts there.

How we measure this

We request ConnectWise's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where ConnectWise publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when ConnectWise goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required