Ashby logo

Is Ashby Down?

AnalyticsLive status, outages, and incident history

No. Ashby is up right now.

Every monitored Ashby system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · every 60s

Know the moment Ashby breaks

Ashby is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Ashby status page
How we know: the official Ashby status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Ashby Status Summary

As of 22:50 UTC on 9 November 2026, Ashby is operational. PulsAPI checked Ashby's official status page and found 31 of 31 components operational, with no active incidents. Over the last 30 days PulsAPI measured 99.97% uptime for Ashby, counting degraded performance as up. The latest incident, "Platform Latency", was on Oct 26, 2026 and lasted 59 min.

Cite as: PulsAPI, “Ashby status”, checked 9 November 2026, 22:50 UTC. https://www.pulsapi.com/services/ashby

Ashby Component Status

The main Ashby systems on this page. All 31 are operational right now.

31operational
Ashby APIs » Ashby API
Operational
Ashby APIs » Documentation
Operational
Ashby APIs » Job Post API
Operational

28 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Ashby APIs » Reports API, Ashby Products » AI Notetaker, Ashby Products » Analytics, Ashby Products » Chrome Extension, Ashby Products » Hosted Job Boards, Ashby Products » Mobile, Ashby Products » Recruiting, Ashby Products » Scheduling, Authentication Services » Google, Authentication Services » Magic Link, Authentication Services » Office 365, Authentication Services » Single Sign On, and 16 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Ashby Outages & Incidents

Incident history from the official Ashby status page, including resolution updates.

Platform LatencyResolved Oct 26, 2026 · 59 minResolved

This incident has been resolved. --- [2026-10-26T17:30:33.129Z] (monitoring) We are starting to see improvement in overall application performance, but we are continuing to monitor. We are still investigating the root cause --- [2026-10-26T16:54:33.915Z] (investigating) We have determined the part of the system causing the latency, but we are still determining the root cause. --- [2026-10-26T16:50:40.364Z] (investigating) We are investigating reports of latency across the platform.

Sporadic reports of Ashby unavailableResolved Oct 23, 2026 · 2h 44mResolved

This incident has been resolved. --- [2026-10-23T16:10:28.952Z] (monitoring) We received reports of some users being unable to access Ashby. This appears related to a network connectivity issue reported by our upstream provider, Cloudflare. Access appears to be recovering, and we’re monitoring for further disruption.

Disruption to Dropbox Sign and BambooHR integrationsResolved Oct 21, 2026 · 4h 38mResolved

BambooHR has recovered, and its integration with Ashby is now working normally. Data updates and new-hire transfers are processing as expected. --- [2026-10-21T16:44:14.880Z] (identified) Dropbox Sign has recovered, and its integration with Ashby is now working normally. E-signature workflows, including creating and sending requests, sending reminders, and cancelling requests, are functioning as expected. --- [2026-10-21T14:31:13.383Z] (identified) Dropbox Sign and BambooHR are experiencing service disruptions, affecting their integrations with Ashby. E-signature workflows using Dropbox Sign may fail or be delayed, including creating and sending requests, sending reminders, and cancelling requests. BambooHR integration data updates and new-hire transfers may also fail or be delayed. Both providers are performing emergency maintenance. We are monitoring their recovery and will share another update as more information becomes available.

Ashby Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Ashby incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 13 days with incidentsNov 9

Going further back: Ashby uptime by month and every recorded Ashby outage.

Live Ashby Outage Reports

Problems reported by engineers using Ashby. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Ashby problems reported yet.

Something wrong with Ashby on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Ashby

Is Ashby down? Ashby reports live availability for 37 components at status.ashbyhq.com, among them Job Feed, Email and Google. Track Ashby outages, degradations and past incidents here, with uptime history and alerts across your analytics stack.

Over the past 30 days, PulsAPI has measured Ashby uptime at 99.97%. Response times, incident history, and SLA tracking for Ashby are available on the PulsAPI dashboard.

Ashby Status FAQ

Is Ashby down right now?

The verdict at the top of this page comes from the latest poll of the official Ashby status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Ashby is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Ashby recovers.

How do I check Ashby uptime history?

PulsAPI tracks Ashby uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.97%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Ashby changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Ashby outages?

PulsAPI reads the official Ashby status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Ashby components?

Yes. PulsAPI monitors 31 individual Ashby components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Ashby goes down?

Yes. Create a free account and subscribe to Ashby: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Ashby to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Ashby problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Ashby?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Ashby plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Ashby with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services