Skip to main content
Ashby logo

Is Ashby Down?

No — Ashby is up
Ashby's status page
Operational · no open incidents
FlareWarden checks
Website reachable · 8 of 8 regions · 622 ms

Right now

The verdict is the worse of these two. How we decide

Ashby's status page

status.ashbyhq.com · read · checked every 3 minutes

Operational
Ashby's components, as its status page reports them
ComponentStatus
Job FeedOperational
Google GmailOperational
Google CalendarOperational
Google MeetOperational
ZoomOperational
ATS SyncOperational
HRIS IntegrationOperational
Dropbox SignOperational
Microsoft 365Operational
Help Center AI ChatOperational
AssessmentsOperational
EmailOperational
19 more, all operational · show all 31
All of Ashby's components
ComponentStatus
Third-Party Integrations
Job FeedOperational
Google GmailOperational
Google CalendarOperational
Google MeetOperational
ZoomOperational
ATS SyncOperational
HRIS IntegrationOperational
Dropbox SignOperational
Microsoft 365Operational
Help Center AI ChatOperational
AssessmentsOperational
Notification Delivery
EmailOperational
SlackOperational
Authentication Services
GoogleOperational
Office 365Operational
Magic LinkOperational
Single Sign OnOperational
Ashby APIs
Ashby APIOperational
Reports APIOperational
Job Post APIOperational
DocumentationOperational
Ashby Products
RecruitingOperational
AnalyticsOperational
Hosted Job BoardsOperational
SchedulingOperational
Chrome ExtensionOperational
MobileOperational
AI NotetakerOperational
Infrastructure Providers
SendGrid API v3Operational
SendGrid Parse APIOperational
AWSOperational

FlareWarden checks

ashbyhq.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
622 ms
Checked

By region

  • Ashburn reachable, 172 ms
  • Frankfurt reachable, 69 ms
  • Johannesburg reachable, 1954 ms
  • London reachable, 131 ms
  • Los Angeles reachable, 316 ms
  • Newark reachable, 275 ms
  • São Paulo reachable, 756 ms
  • Tokyo reachable, 1305 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Ashburn64 ms2 ms7 ms163 ms
Frankfurt37 ms5 ms9 ms58 ms
Johannesburg206 ms248 ms254 ms961 ms
London20 ms15 ms19 ms75 ms
Los Angeles96 ms10 ms15 ms275 ms
Newark91 ms10 ms14 ms235 ms
São Paulo405 ms2 ms10 ms748 ms
Tokyo258 ms74 ms78 ms1010 ms
We check that ashbyhq.com loads, not every feature behind it. Test it yourself

History

Incidents Ashby reported

Since Oct 22, 15 days · from status.ashbyhq.com

Incidents
5
Major or critical
1
Median to resolve
2h 8m
  1. Platform Latency

    minor ·

    lasted 59m
  2. lasted 2h 44m
  3. lasted 4h 38m
  4. lasted 2h 8m
  5. lasted 28m

Ashby website availability

Measured by FlareWarden · ashbyhq.com

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

Last 30 days

69-day clean streak
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 32 checks
Oct 16: 100.00% uptime, 32 checks
Oct 17: 100.00% uptime, 32 checks
Oct 18: 100.00% uptime, 32 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 31 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 31 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of ashbyhq.com from multiple regions every 6 hours. Ashby's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 69 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • 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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Ashby itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Ashby goes down

We check Ashby every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required