Jobylon Outage History
6 incidents recorded over the last 365 days, 6 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 Jobylon Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 29, 2026 | Degraded performance on the Jobylon ATSWe identified the source of the unusual crawling activity and blocked it from overloading our systems. The platform is operating normally, and we are continuing to strengthen our caching to prevent similar issues. | 4h 5m | Resolved |
| Sep 25, 2026 | Elevated errors and timeoutsWe experienced elevated level of errors and timeouts in the application. This was due to spikes in traffic on some specific endpoints. | 0 min | Resolved |
| Jul 17, 2026 | Issues with logging in and saving changesAll reported issues have now been resolved. Both the initial outage and the subsequent issues affecting certain actions (switching accounts, editing jobs, adding comments) have been addressed; these were caused by a… | 3h 25m | Resolved |
| May 6, 2026 | Embedded Widget Rendering IssuesWe identified an issue affecting embedded widgets following a recent deployment. The issue has since been resolved by rolling back the affected deployment changes. Our team is actively investigating the root cause and… | 8h 20m | Resolved |
| Dec 5, 2025 | Intermittent Access Issues Due to Cloudflare Service DegradationThis incident has been resolved. | 23 min | Resolved |
| Nov 18, 2025 | Intermittent Access Issues Due to Cloudflare Service DegradationCloudflare has identified the underlying issue and deployed a fix. We are now observing services recovering across our environment, and application performance is returning to normal. We continue to monitor traffic and… | 3h 3m | Resolved |
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 Jobylon 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 Jobylon 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 Jobylon 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 Jobylon outage in this window ran 8h 20m, against a mean recovery of 3h 13m. If you depend on Jobylon 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.