Gem Outage History
21 incidents recorded over the last 365 days, 16 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Gem Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 31, 2026 | File uploads and attachments are failingThis issue has been resolved. Our team will continue to monitor for any problems. | 1h 1m | Resolved |
| Jul 2, 2026 | Scheduled maintenance, July 2 2026The scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jun 18, 2026 | Workday data sync and webhook disruptionsThis incident has been resolved. | 258h 15m | Resolved |
| Jun 11, 2026 | Unable to send offer e-signature requestsDocusign has resolved the outage with their services, and Gem e-signature and offer requests are now working normally. | 4h 2m | Resolved |
| Jun 4, 2026 | Scheduled MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jun 1, 2026 | Scheduled DB MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| May 15, 2026 | Sequence Sending FailuresThe issue affecting sequence sending has been resolved. If you were seeing the error "Your changes were not saved because this sequence was edited elsewhere," please refresh your browser — sequences should now send… | 11 min | Resolved |
| Mar 25, 2026 | Some AI Ranking tasks not completingWe have confirmed that the fix resolved the issue, and we have processed all delayed ranking requests. AI Ranking should now be working normally. | 2h 40m | Resolved |
| Feb 24, 2026 | AI Sourcing search delaysThis issue has been resolved. | 1h 24m | Resolved |
| Feb 23, 2026 | Delays in nightly Greenhouse syncsThis incident has been resolved. | 346h 59m | Resolved |
| Feb 18, 2026 | gem.com is downWe are resolving this incident. | 2h 51m | Resolved |
| Feb 5, 2026 | Delayed processing of Greenhouse updatesThe backlog of webhooks from Greenhouse has been processed, and future updates will process at the normal pace. This issue is resolved. | 6h 3m | Resolved |
| Jan 13, 2026 | Partial Outage: Gem is not accessible from certain Countries in EU and UKThis incident is now resolved and service has been fully restored for impacted users. If you still have any issues loading Gem pages, please email support@gem.com for further investigation. | 11h 45m | Resolved |
| Dec 18, 2025 | Some data from December 17, 2025 is currently unavailableAffected candidates, applications, scorecards, projects, campaigns, forms, and sequences are now available for all customers. In cases where a new object was created in place of one that was temporary missing, the new… | 131h 31m | Resolved |
| Dec 18, 2025 | Routine Database UpgradeThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Dec 15, 2025 | Delays in Gem Scheduling syncing and notificationsThis issue has been resolved. All delayed Gem Scheduling actions have been completed successfully. | 23h 34m | Resolved |
| Dec 4, 2025 | Notification emails failed to sendEarlier this morning, our team identified an issue that caused sending failures for some notification emails. This impacted modules and features that rely on notification messages, such as Gem Scheduling and Gem ATS… | -442 min | Resolved |
| Nov 17, 2025 | Prospect Search results are staleThis issue has been resolved. Prospect Search has caught up and data update intervals are now back to normal. | 5h 44m | Resolved |
| Nov 12, 2025 | Loading issues with Dashboards and Pipeline AnalyticsThis issue should now be resolved, and we will continue to monitor performance. | 123h 38m | Resolved |
| Nov 10, 2025 | Blank pages in Pipeline AnalyticsThis issue has been resolved. | 52 min | Resolved |
| Nov 5, 2025 | Gem Scheduling - Scheduled MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Gem incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Gem Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Gem acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Gem outage in this window ran 14d 10h, against a mean recovery of 1d 22h. If you depend on Gem in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.