Teamtailor Outage History
16 incidents recorded over the last 365 days, 12 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 Teamtailor Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 1, 2026 | Marketing website (www.teamtailor.com) unavailableBetween approximately 02:05 and 02:20 CEST our marketing website www.teamtailor.com was unavailable for some visitors due to a problem with its security certificate. The certificate was renewed and the website is… | 0 min | Resolved |
| Sep 28, 2026 | Degraded performanceFrom approximately 09:30 to 13:55 CEST some customers in the North America region experienced intermittent slow response times when accessing Teamtailor and career sites, with short periods of errors around 11:55, 12:15… | 0 min | Resolved |
| Sep 25, 2026 | Degraded performanceBetween approximately 11:50 and 12:01 CEST some customers in the EU region experienced slow response times and errors when accessing Teamtailor and career sites. The cause was high load on one of our internal systems… | 0 min | Resolved |
| Sep 24, 2026 | Intermittent availability issueBetween approximately 11:25 and 11:31 CEST some customers in the EU region experienced errors when accessing Teamtailor and career sites. The cause was high database load. The issue has been identified and resolved. We… | 0 min | Resolved |
| Sep 24, 2026 | Degraded performance and intermittent errorsBetween approximately 15:15 and 15:27 CEST, some customers in the EU region experienced slow response times and intermittent errors when using Teamtailor and career sites. The issue briefly returned around 17:25 CEST… | -1064 min | Resolved |
| Sep 23, 2026 | Short data store maintenanceThe scheduled maintenance has been completed. | 15 min | Scheduled |
| Sep 16, 2026 | Intermittent availability issueBetween approximately 11:16 and 11:35 CEST some customers experienced intermittent errors when accessing Teamtailor. The issue has been identified and resolved. We apologise for any inconvenience. | 0 min | Resolved |
| Jul 8, 2026 | Degraded performance – delayed background processingBetween approximately 08:50 and 11:30 CEST, customers may have experienced general slowness across the platform and delays in background processing (e.g. resume parsing and other queued actions). The cause was a… | -265 min | Resolved |
| Jul 6, 2026 | Increased database issues for customers on na-maroonThis incident has been resolved. | 4h 39m | Resolved |
| Jul 2, 2026 | Marketing website (www.teamtailor.com) unavailableA new SSL certificate has been deployed and www.teamtailor.com is fully available again. This incident is resolved. | 44 min | Resolved |
| Jun 15, 2026 | Intermittent errors when uploading and displaying imagesThis issue has been resolved. The problem with our external service provider has been fixed, error rates have returned to zero, and image uploads and display are operating normally again across all regions. Thank you… | 7 min | Resolved |
| Jun 5, 2026 | Availability issueThis incident has been resolved. | 37 min | Resolved |
| May 22, 2026 | Delays and intermittent errors across multiple featuresThis incident has been resolved, all system features are back to normal. | 33 min | Resolved |
| May 20, 2026 | North America - Scheduled database maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| May 16, 2026 | Europe - Scheduled database maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Nov 5, 2025 | US/NA: Scheduled database 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 Teamtailor 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 Teamtailor 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 Teamtailor 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 Teamtailor outage in this window ran 4h 39m, against a mean recovery of 43 min. If you depend on Teamtailor 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.