Skip to main content
Ashby logo

Is Ashby Down?

No — Ashby is up

Reachable from all 8 checked regions

Average response time: 394ms

Last checked · checks run every 6 hours

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

Ashby uptime

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

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

30-day history

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

lax
136ms
DNS 49ms TCP 11ms TLS 17ms TTFB 95ms
lhr
298ms
DNS 112ms TCP 15ms TLS 86ms TTFB 241ms
nrt
1853ms
DNS 222ms TCP 230ms TLS 237ms TTFB 925ms
ord
270ms
DNS 105ms TCP 21ms TLS 26ms TTFB 188ms
sin
47ms
DNS 13ms TCP 2ms TLS 10ms TTFB 31ms
sjc
166ms
DNS 134ms TCP 2ms TLS 8ms TTFB 150ms
syd
219ms
DNS 189ms TCP 2ms TLS 8ms TTFB 206ms
yyz
168ms
DNS 25ms TCP 19ms TLS 26ms TTFB 96ms

What Ashby does

Ashby is an applicant tracking system and recruiting platform used by in-house talent teams. It handles candidate pipelines, interview scheduling, hosted job boards, offer workflows and recruiting analytics in one product, and syncs with calendar, video and HRIS tools. Companies depend on it for both internal hiring work and the public pages candidates apply through.

What an outage looks like

The Ashby app fails to load or candidate records will not save. A separate and less visible failure is Hosted Job Boards: your careers page stops serving while recruiters work normally inside Ashby, so applications stop arriving with no error anyone at the company sees. Scheduling breaks on its own when the Google or Office 365 integrations are the failing component.

What to do about it

Check status.ashbyhq.com and match the component to what you are doing. Ashby reports Recruiting, Hosted Job Boards, Scheduling, the Chrome Extension, Mobile and three separate APIs, plus each calendar and video integration. If Hosted Job Boards is affected, tell anyone running live job adverts, because a paused careers page costs applications that never generate a support ticket.

Is it down for everyone, or just you?

If this page says Ashby 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

Greenhouse
Greenhouse
Lever
Lever
I
Indeed
Zoom
Zoom

Ashby outage FAQ

Candidates say they cannot apply, but Ashby works for me. Is it down?
Probably in part. Ashby reports Hosted Job Boards as a component separate from Recruiting, so the public careers page can be unavailable while the internal app you are logged into serves normally. That failure is silent from the inside: nobody at the company gets an error, applications simply do not arrive. Check the Hosted Job Boards row specifically.
Is my interview scheduling broken because of Ashby or because of Google Calendar?
Check which component is red. Ashby lists Google, Google Calendar, Google Gmail, Google Meet, Office 365, Zoom and Single Sign On as components of their own, apart from its Scheduling component. That separation exists because scheduling failures often originate at the calendar or video provider, and the fix differs depending on which side is at fault.
Does an Ashby outage break the integrations we built on its API?
It depends which API. Ashby publishes Ashby API, Reports API and Job Post API as three separate components, so an incident can affect reporting pulls while candidate writes continue, or block job syndication while everything else is fine. Match the failing component to the endpoints your integration calls before assuming all automation has stopped.
Will candidate data be lost during an Ashby outage?
Ashby does not publish retention or queueing behaviour for failed writes on its status page, so treat anything that returned an error as unsaved. The safer move is to note what you were entering, wait for the component to recover, then confirm the record before re-entering it. Re-entering during a partial outage risks duplicate candidate records.
Can I use the Ashby mobile app while the web app is down?
Sometimes. Mobile and the Chrome Extension are reported as their own components, distinct from Recruiting, so an incident scoped to the web application can leave mobile serving. That is not guaranteed in the other direction either. Check the Mobile row rather than assuming the surfaces fail together, because they are deployed and reported separately.

How we measure this

  • We request Ashby'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 Ashby 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 Ashby 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