JazzHR

All Systems Operational

About This Site

Welcome to JazzHR's Statuspage!

This page provides real-time updates on the status and performance of our systems and services. Our goal is to ensure transparency and keep our customers informed about any issues, maintenance, or updates that might affect our operations.

Key Updates include:

1) Current System Status: An at-a-glance view of the health of our critical systems.
2) Incident Reports: Detailed information on any ongoing or resolved incidents.
3) Maintenance Updates: Notifications about scheduled maintenance and upgrades.
4) Performance Metrics: Data and insights on system performance to help you stay informed.

Uptime over the past 90 days. View historical uptime.
API Operational
90 days ago
99.66 % uptime
Today
Application Operational
90 days ago
99.95 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Jun 23, 2026

No incidents reported today.

Jun 22, 2026
Service Disruption Due to Cloudflare Outage
Resolved - Cloudflare has reported that its traffic engineering efforts have successfully mitigated the majority of congestion and packet loss associated with this incident. As a result, service conditions are improving; however, some users may still experience intermittent connectivity issues while their recovery efforts continue.

Customer Impact: Most services have stabilized, but some users may continue to experience intermittent latency, timeouts, or connectivity issues during the final stages of recovery.

Customers can monitor the latest updates directly on Cloudflare's status page: https://www.cloudflarestatus.com/
We will continue to provide updates as new information becomes available.
Jun 22, 18:21 UTC
Identified - Monitoring Third-Party Network Issue

Status:
We continue to monitor an ongoing third-party network incident affecting Cloudflare, which is causing intermittent timeouts, increased latency, and occasional Cloudflare error pages for some users accessing our platforms.

Based on updates from Cloudflare, the issue is related to a network infrastructure event in North America, and their engineering teams are actively rerouting traffic and implementing mitigation measures to restore service stability.

At this time, the underlying issue resides with a third-party provider and is outside of our direct control. Our teams are closely monitoring the situation and validating service availability as Cloudflare implements corrective actions.

Customers may continue to experience intermittent connectivity issues, slow response times, or timeout errors until Cloudflare has fully resolved the incident.

For the latest updates, please monitor Cloudflare's status page directly: https://www.cloudflarestatus.com/
We appreciate your patience and will continue to provide updates as new information becomes available.
Jun 22, 16:17 UTC
Investigating - We are currently investigating an issue impacting access to our platforms. A broader Cloudflare service disruption is affecting connectivity, resulting in:

Request timeouts
Increased latency and slow page loads
Cloudflare-generated error pages (including 5xx errors)
Intermittent access to platform services

Our teams are actively monitoring the situation and assessing the impact on our services. While the issue appears to originate from Cloudflare's infrastructure, we continue to monitor service health and will provide updates as additional information becomes available.
Customers can monitor Cloudflare's incident status directly at: https://www.cloudflarestatus.com/
Start Time: ~9:35 EDT
We apologize for the inconvenience and appreciate your patience while service providers work to restore normal operations.

Customer Impact: Users may experience intermittent access issues, delayed responses, request failures, or Cloudflare error pages when accessing platform services.
Reference: Cloudflare Status Page — https://www.cloudflarestatus.com/
Jun 22, 14:42 UTC
XML Feed issue
Resolved - Status: Resolved and monitoring complete.

The backlog catch-up process has been completed. All job data is now fully synchronized, and newly created jobs and job updates are being delivered correctly through both the API and XML feeds.

We have verified that data synchronization is operating normally and no further impact is expected. We will continue to monitor the system to ensure ongoing stability. If any further issues are identified, please reach out to customer support.

An RCA will be available within 7-10 business days
Jun 22, 11:44 UTC
Update - All the jobs syndication is up to date as of 1500 EST (3pm) June 18, any delay is partner pulling and processing at this point.
Jun 19, 15:22 UTC
Monitoring - Update on job syndication, We identified the issue and have a fix in place, and feeds are currently regenerating.

Since Job boards consume and process those feeds on their own cadence, no guarantees about timing. However, we expect to resolve the feed sync issues shortly.
Jun 18, 17:16 UTC
Identified - Our Engineering team has identified the problem and are working towards a resolution.
Jun 18, 14:46 UTC
Investigating - We are currently investigating an issue where newly created jobs and job updates are not syncing to xml feed.
Jun 18, 14:40 UTC
Jun 21, 2026

No incidents reported.

Jun 20, 2026

No incidents reported.

Jun 19, 2026
Jun 18, 2026
Jun 17, 2026

No incidents reported.

Jun 16, 2026

No incidents reported.

Jun 15, 2026
LinkedIn Job Distribution
Postmortem - Read details
Jun 17, 18:30 UTC
Resolved - This incident has been resolved.

Incident Duration: June 5 - June 12
Impact Summary: Some jobs for some customers may fail to publish correctly to LinkedIn.
Cause: LinkedIn has updated their preferred method of job data ingestion for job posting and there were some data conflicts caused by referencing the older method at the same time as the updated method.
Mitigation: Validated integration code and system behavior to insure all publishing attempts go through the updated preferred method from LinkedIn at all times.

An RCA will be provided within 7-10 business days if applicable.
Jun 15, 14:58 UTC
Monitoring - We have implemented a correction for this issue where publishing jobs from JazzHR to LinkedIn was intermittently failing. We have reviewed the examples we had and are monitoring posting error rates, we believe all jobs will not publish as expected. We will continue to monitor over the weekend.

Next update: Monday June 15.
Jun 12, 19:07 UTC
Identified - We have identified the most likely cause of the ongoing issues with Jobs not successfully posting to LinkedIn and our engineering team is working with LinkedIn to correct the issues as soon as possible.

Further updates will be provided by tomorrow or soon if more information becomes available.
Jun 11, 18:34 UTC
Update - We are continuing to investigate this issue.
Jun 10, 21:43 UTC
Update - We are continuing to investigate this issue, we have confirmed that most Job Publishing actions with LinkedIn are completing successfully and reviewing this with LinkedIn.

If none of your jobs are publishing to LinkedIn at all, please first visit the Account Information Page and verify your LinkedIn Company ID is correctly set there. Help Center guide at https://help.jazzhr.com/s/article/Mapping-your-LinkedIn-Company-ID
Jun 10, 18:57 UTC
Investigating - Investigating — We have identified that some JazzHR customers are experiencing issues with jobs not posting to LinkedIn through the automated job syndication integration. Jobs submitted through the integration may not be appearing on LinkedIn as expected.

Our Engineering team is actively investigating the issue in coordination with LinkedIn. We are working to confirm the full scope of jobs that are not posted as expected and reprocess any postings we can correct directly. In the meantime, it is possible to post a link to a job directly through LinkedIn as a temporary workaround.
Jun 9, 21:18 UTC
Jun 14, 2026

No incidents reported.

Jun 13, 2026

No incidents reported.

Jun 12, 2026
Jun 11, 2026
Jun 10, 2026
Jun 9, 2026
Application Performance Degradation
Postmortem - Read details
Jun 12, 13:31 UTC
Resolved - This incident has been resolved.

Incident Duration: June 8, 2026, 3:18 PM ET – June 9, 2026, 9:30 AM ET
Service recovery began ~9:30 AM ET; full resolution confirmed and posted ~10:30 AM ET after a period of monitoring.)
Impact Summary: During this window, some users may have experienced errors or been unable to access parts of the application.
Cause: An internal issue affected a system that supports billing and subscription information. Because this system is used across the product, the disruption led to elevated errors and degraded access throughout the application.  
Mitigation: The issue has been resolved and service has returned to normal. We are putting additional safeguards in place and do not expect it to recur. A full root cause analysis will be posted within 7–10 business days.

An RCA will be provided within 7-10 business days if applicable.
Jun 9, 17:54 UTC
Monitoring - We have put in place a fix and are seeing initial positive recovery, we will continue monitoring to insure this incident is fully resolved.
Jun 9, 14:30 UTC
Identified - We are currently investigating ongoing service degradation affecting the JazzHR platform. Customers may experience intermittent 500 Internal Server Errors, slow application performance, API instability, and issues loading billing-related profile information.

Our engineers have identified the problem and are working towards a resolution.

We will provide a status update by 11 am ET.
Jun 9, 13:07 UTC
← Incident History Powered by Atlassian Statuspage