Is Gem Down?

No — Gem is up

Gem's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 1305 ms

Right now

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

Gem's status page

status.gem.com · read 4 minutes ago · checked every 3 minutes

Operational

Gem's components, as its status page reports them
Component	Status
Gem Web Application	Operational
Gem Integrations	Operational
Gem Extension	Operational
Gem Scheduling	Operational
Gem AI	Operational
Gem API	Operational
Gem Homepage	Operational

Open their status page

FlareWarden checks

gem.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: 1305 ms
Checked: 2 hours ago

By region

Amsterdam reachable, 757 ms
Chicago reachable, 373 ms
San Jose reachable, 718 ms
Singapore reachable, 2630 ms
Stockholm reachable, 1587 ms
Sydney reachable, 1613 ms
Tokyo reachable, 2240 ms
Toronto reachable, 528 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	44 ms	4 ms	6 ms	375 ms
Chicago	120 ms	1 ms	3 ms	265 ms
San Jose	92 ms	2 ms	6 ms	470 ms
Singapore	316 ms	2 ms	5 ms	1782 ms
Stockholm	81 ms	2 ms	6 ms	1146 ms
Sydney	156 ms	1 ms	3 ms	745 ms
Tokyo	102 ms	2 ms	3 ms	1489 ms
Toronto	61 ms	8 ms	13 ms	455 ms

We check that gem.com loads, not every feature behind it. Test it yourself

History

Incidents Gem reported

Since Nov 2, 4 days · from status.gem.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Gem website availability

Measured by FlareWarden · gem.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 1182ms

Last 30 days

13-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

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

What Gem does

Gem is an AI-first recruiting platform for talent acquisition teams. It combines an ATS, a candidate CRM with automated email sequences, AI sourcing and application review, interview scheduling and analytics. Teams run it as their whole recruiting system or alongside an ATS they already use, such as Greenhouse or Lever, and recruiters add candidates from the web through its Chrome extension.

What an outage looks like

Pages or the extension load forever, as when Gem was unreachable from some EU and UK countries on January 13, 2026, or gem.com stops loading entirely, as during a Heroku outage on February 17, 2026. Smaller incidents hit one feature: sequences fail with 'Your changes were not saved because this sequence was edited elsewhere', uploads and take-home submissions fail, AI Ranking sticks on 'Ranking in progress', or ATS syncs lag.

What to do about it

Check status.gem.com, which lists the Web Application, Integrations, Extension, Scheduling, AI and API separately. If ATS data looks stale, compare it with Gem's published Greenhouse sync intervals before reporting it; some changes take an hour and others a day. In its 2026 sync incidents Gem said no updates were lost and worked through the backlog. Refresh before resending a failed sequence, then email support@gem.com.

Is it down for everyone, or just you?

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

Gem outage FAQ

Does a Greenhouse or Workday problem affect Gem?

Yes, for teams that connect Gem to those systems. On February 5, 2026 webhook processing from Greenhouse was delayed by several hours, so candidate and job changes lagged until Gem cleared the backlog that afternoon. From June 16, 2026 a Workday sync problem left pipeline metrics out of date for days; Gem said no data was permanently lost and re-ran the affected syncs.

Why is my Greenhouse data out of date in Gem?

Often it has not synced yet. Gem's help center says deleting an interview in Greenhouse shows in Gem within 15-30 minutes, adding or updating interviews and scorecards syncs hourly, and custom fields, offices, departments and user permissions sync daily around midnight Pacific Time, sometimes taking an extra day or two. Bulk actions in Greenhouse do not sync automatically. Report longer delays to support@gem.com.

Why do Gem sequences fail to send?

Check the error first. 'Failed due to API limits on your email account' means your Gmail or Microsoft mailbox hit its provider's API limit, which Gem's help center says is shared by every app connected to it, so review those apps. During a May 15, 2026 incident sequences failed with an 'edited elsewhere' error, and Gem told users to refresh the browser once it was fixed.

Does a Heroku or DocuSign outage affect Gem?

It has. On February 17, 2026 the gem.com website and application stopped loading for nearly three hours, which Gem attributed to an outage at its provider Heroku; service returned after Heroku rolled back a change. On June 11, 2026 a DocuSign outage stopped Gem from sending offer e-signature requests for about four hours, until DocuSign resolved it.

What does the check on this page measure?

It loads www.gem.com, Gem's public homepage. Gem's web app runs on the same domain, so a failure here can mean the app is down too, as on February 17, 2026. A pass does not show that sequences send, integrations sync or the extension works. Gem's status page tracks those, and the homepage, as separate components.

How we measure this

We request Gem'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 Gem 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 Gem 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 Gem goes down

We check Gem 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