Skip to main content
SalesLoft logo

Is SalesLoft Down?

No — SalesLoft is up

Reachable from all 8 checked regions

Average response time: 8415ms

Last checked · checks run every 6 hours

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

SalesLoft uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
2951ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 1 day measured so far. A dash means we have no measurement for that window.

30-day history

Jun 29: no data
Jun 30: no data
Jul 1: no data
Jul 2: no data
Jul 3: no data
Jul 4: no data
Jul 5: no data
Jul 6: no data
Jul 7: no data
Jul 8: no data
Jul 9: no data
Jul 10: no data
Jul 11: no data
Jul 12: no data
Jul 13: no data
Jul 14: no data
Jul 15: no data
Jul 16: no data
Jul 17: no data
Jul 18: no data
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 24 checks
Jun 29 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.

ams
9627ms
DNS 42ms TCP 12ms TLS 17ms TTFB 9598ms
lax
46ms
DNS 5ms TCP 1ms TLS 12ms TTFB 36ms
lhr
9550ms
DNS 0ms TCP 1ms TLS 15ms TTFB 9541ms
nrt
9381ms
DNS 0ms TCP 0ms TLS 14ms TTFB 9371ms
ord
9830ms
DNS 0ms TCP 2ms TLS 14ms TTFB 9820ms
sin
9257ms
DNS 21ms TCP 15ms TLS 23ms TTFB 9246ms
sjc
9823ms
DNS 0ms TCP 1ms TLS 13ms TTFB 9811ms
syd
9737ms
DNS 0ms TCP 5ms TLS 11ms TTFB 9729ms
yyz
117ms
DNS 1ms TCP 17ms TLS 21ms TTFB 91ms

What SalesLoft does

Salesloft runs sales engagement: sequenced outreach, dialling, email tracking and deal management, wired into a CRM. Reps work a queue inside it all day, so an outage stops outbound activity for a whole team at once and leaves cadences half-executed in a way that is awkward to resume cleanly.

What an outage looks like

The web application fails to load or opens with an empty task queue, so reps have nothing to work. Emails sent through a cadence fail or send without logging. The dialler cannot connect calls when the VoIP provider is affected. CRM sync stops, so activity is missing from Salesforce or HubSpot, and the Chrome extension stops surfacing data in the inbox.

What to do about it

Check status.salesloft.com, which lists the web application, the VoIP provider, Conversation Intelligence, Deals, the Chrome extension and each third-party integration (Salesforce, HubSpot, Outlook, G Suite, LinkedIn) separately, so a dialling failure may be the VoIP provider rather than Salesloft. Pause cadences rather than letting them run half-delivered against the same contacts.

Is it down for everyone, or just you?

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

Test it yourself

Related services

Gong
Gong
ZoomInfo
ZoomInfo
Salesforce
Salesforce
HubSpot
HubSpot

SalesLoft outage FAQ

Is Salesloft down or is the integration at fault?
Salesloft reports Salesforce, HubSpot, Outlook, G Suite and LinkedIn as separate components, and the failure is often in one of those rather than in Salesloft. If the application loads and only CRM logging is missing, check the relevant integration component before raising a ticket, since the two teams involved would be entirely different.
Should I pause cadences during an outage?
For anything time sensitive, yes. A cadence that runs while delivery is degraded can send some steps and skip others, leaving prospects with an incoherent sequence, or send a burst of delayed messages at once during recovery. Pausing costs a day of outreach; an incoherent sequence costs credibility with the prospect.
Were my emails actually sent during the incident?
Check the recipient side or your own sent items rather than relying on the activity log, because logging and sending fail independently. An email can send without being recorded, which makes it look unsent, and a logged email may not have delivered. Resending blindly is how prospects receive the same message twice.
Why can I not make calls when the app is working?
The dialler depends on a VoIP provider that Salesloft reports as its own component. When that provider is degraded, calls fail while the rest of the platform works normally. Using a phone directly is a reasonable fallback for urgent calls; just note that the activity will not be logged automatically afterwards.
Does an outage lose Conversation Intelligence recordings?
Conversation Intelligence is tracked separately, and recordings already processed are retained. Calls that took place while it was degraded may not have been captured at all, and a conversation that was never recorded cannot be recovered. For a call that matters, arrange another recording rather than relying on automatic capture during an incident.

How we measure this

  • We request SalesLoft's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • 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 SalesLoft publishes an official status feed we read it too, and let it override us in both directions.

Get alerted when SalesLoft goes down

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

Start Free Monitoring
Free plan available No credit card required