RefAssured Outage History

Started Oct 18, 2026, 04:22 PM UTC· resolved Oct 25, 2026, 03:10 AM UTC

1. monitoring Oct 18, 2026, 04:22 PM UTC

   On Saturday, October 17, Bullhorn disclosed an incident affecting its platform and temporarily disabled access to its systems while it investigates. Their outage is ongoing as of this message. For Bullhorn’s latest updates, see https://status.bullhorn.com/. The RefAssured platform is operating normally. While Bullhorn is unavailable: • Reference requests triggered from Bullhorn Automation or Talent Platform will not start. • References already in progress continue to be completed, and reports remain available in RefAssured. • Your team can request references directly in RefAssured in the meantime. • Write-backs to Bullhorn (notes, files, scores, credentials) won't land while BH is down. We are monitoring closely and will post updates here as Bullhorn restores service, including next steps for any activity completed during the outage.

2. monitoring Oct 18, 2026, 10:07 PM UTC

   A quick update on the Bullhorn service disruption that began Saturday, October 17. We remain in close communication with the Bullhorn team, and we know they are all over this. Their team is fully engaged and working around the clock to restore access safely, and we appreciate the speed and care they're bringing to it. The RefAssured platform is operating normally, and we are continuing to monitor the situation closely. While Bullhorn is unavailable, your team can request references directly in RefAssured. References already in progress continue to be completed, and reports remain available in the app. For Bullhorn's latest updates, please visit https://status.bullhorn.com/. We'll follow up as soon as service is restored. In the meantime, don't hesitate to reach out with any questions.

3. monitoring Oct 19, 2026, 02:49 PM UTC

   Bullhorn has begun bringing environments back online. RefAssured remains fully online and operating normally, and we are continuing to monitor the situation closely as Bullhorn services are restored and more information becomes available. For restoration timing by region, please refer to Bullhorn’s status page at https://status.bullhorn.com. We’ll post next steps here for any RefAssured activity completed during the outage.

4. monitoring Oct 19, 2026, 04:18 PM UTC

   Bullhorn is restoring access today, with US clusters expected back by 1pm ET. Here is what that means for your RefAssured integration. What’s working • Once you can log into Bullhorn, the RefAssured view inside Bullhorn loads normally and your team can keep requesting references from there as usual. • RefAssured itself has been online throughout. References in progress are still being completed and reports are available in the app. What’s still paused • As part of its security response, Bullhorn is reissuing API credentials for all integration partners, including RefAssured. Until your new credentials are in place, requests triggered automatically from Bullhorn (Automation, Talent Platform) will not start and write-backs to Bullhorn (notes, files, scores, credentials) will not land. • We’ve already submitted the request to Bullhorn for every customer and will update each integration as credentials come back. We’ll confirm with you directly when yours is live. • Please do not reset or change the RefAssured API user in your Bullhorn instance yourself. That can put it into a different password rotation status and cause problems later. Next steps • We’ll follow up on anything completed during the outage once your integration is reconnected. • Bullhorn’s status page remains the best source for restoration timing: https://status.bullhorn.com/ • For RefAssured updates, subscribe at https://status.refassured.com

5. monitoring Oct 19, 2026, 10:33 PM UTC

   As part of Bullhorn’s security response, the API password for the RefAssured integration must be updated before automated requests and write-backs can resume. We have submitted the update for every customer and are currently in queue with Bullhorn support to complete it. Their team is hard at work, and we are waiting patiently alongside you. In the meantime: RefAssured is fully online, and your team can request references directly in RefAssured. References already in progress are still being completed, and reports remain available in the app. Requests triggered automatically from Bullhorn (Automation, Talent Platform) and write-backs to Bullhorn (notes, files, scores, credentials) remain paused until the update is complete. Please do not reset or change the RefAssured API user in your Bullhorn instance yourself, as that can delay your reconnection. We will post an update here as soon as we have one.

6. monitoring Oct 20, 2026, 04:30 PM UTC

   Update: Bullhorn has confirmed that all regions are back online. We are still waiting for Bullhorn to reset the API credentials for the RefAssured integration, and we remain in active communication with their team. We know a timely resolution matters to our customers, and we are staying on it. Until the credentials are reset: - RefAssured is fully online. Users with a RefAssured login can request references there as usual. - The RefAssured view inside Bullhorn may or may not load depending on your instance. If it doesn’t, that is expected and will resolve once credentials are reset. Nothing on your side needs to change. - Automated requests from Bullhorn and write-backs to Bullhorn remain paused. - Please do not reset or change the RefAssured API user in your Bullhorn instance yourself, as that can delay your reconnection. We will post an update here as soon as we have more.

7. monitoring Oct 21, 2026, 03:09 AM UTC

   Update: Bullhorn has restored login access for users and is continuing to restore full functionality, including the integration points RefAssured relies on. We are still waiting for Bullhorn to reset the API credentials for the RefAssured integration, and we remain in active, daily contact with their team to push this forward. We know a timely resolution matters to your teams, and we are staying on it. Until the credentials are reset: -RefAssured is fully online. Users with a RefAssured login can request references there as usual. -The RefAssured view inside Bullhorn may or may not load depending on your instance. If it doesn’t, that is expected and will resolve once credentials are reset. Nothing on your side needs to change. -Candidate driven workflows that run through Bullhorn (Bullhorn Talent Platform, Bullhorn Automation, and custom candidate driven workflows) may become intermittent and could pause for some users until credentials are reset. If this is affecting your team, please reach out to your Customer Success manager and we will set you up with alternative access to RefAssured in the meantime. -Automated requests from Bullhorn and write-backs to Bullhorn remain paused. Please do not reset or change the RefAssured API user in your Bullhorn instance yourself, as that can delay your reconnection. We will post an update here as soon as we have more.

8. monitoring Oct 22, 2026, 03:18 AM UTC

   Update: The majority of RefAssured integrations with Bullhorn production environments have been restored and verified. We are continuing to troubleshoot a few remaining production integrations directly with Bullhorn’s team, and we will contact affected customers individually. There are several non-production environments (sandbox and test instances) that may not yet be connected. Restoration of production environments is being prioritized first, and we will share an update on non-production environments when we have one. What this means for you: - If your integration has been confirmed as working, automated requests from Bullhorn and write-backs to Bullhorn have resumed for new activity going forward. - If you have not yet heard from us, your integration is still being verified or is among those we are actively troubleshooting. - RefAssured remains fully online. Users with a RefAssured login can request references there as usual, and results for references completed during the pause are available to view or download anytime. - Please do not reset or change the RefAssured API user in your Bullhorn instance yourself, as that can delay your reconnection. We will post another update here as we continue to make progress.

9. monitoring Oct 22, 2026, 10:29 PM UTC

   **Update:** After normal integration capabilities resumed, we have received reports that the RefAssured integration is being locked in some Bullhorn instances. We are actively investigating the cause and are in direct communication with Bullhorn's team. In the meantime: - RefAssured remains fully online. Users with a RefAssured login can request references there as usual. - Please do not reset, unlock, or change the RefAssured API user in your Bullhorn instance yourself unless our team asks you to. Bullhorn Support is actively working on these accounts, and changes made in parallel can overwrite their work and delay a fix. We will post updates here as we learn more.

10. monitoring Oct 23, 2026, 03:24 AM UTC

    Update: All RefAssured integrations identified as not working in our latest audit have now been updated in coordination with Bullhorn’s team, and we have no known outstanding production issues at this time. Thank you to our customers for your patience throughout this incident. Non-production environments (sandbox and test instances) remain unavailable while production environments are prioritized. We will share an update when we have a confirmed timeline. We will continue to monitor integrations closely. If you notice anything that isn’t working as expected, please reach out to your Customer Success Manager. Please continue not to reset, unlock, or change the RefAssured API user in your Bullhorn instance yourself unless our team asks you to.

11. monitoring Oct 23, 2026, 05:50 PM UTC

    Update: All RefAssured integrations with Bullhorn production environments are working as intended. Our internal checks have not identified any issues, and we have not received any customer reports. We are continuing to monitor closely. Non-production environments (sandbox and test instances) remain unavailable while production environments are prioritized. We will share an update when we have a confirmed timeline. If you notice anything that isn’t working as expected, please reach out to your Customer Success Manager.

12. resolved Oct 25, 2026, 03:10 AM UTC

    Since our last update, we have had no reports or indications of any issues with RefAssured integrations in Bullhorn production environments, and this incident is now closed. We will continue to monitor integrations closely. Restoration of non-production environments (sandbox and test instances) will be tracked in a separate incident. Thank you for your patience throughout this incident.

Read the full incident report →

Started Jan 22, 2026, 08:30 PM UTC· resolved Jan 22, 2026, 10:09 PM UTC

1. investigating Jan 22, 2026, 08:30 PM UTC

   We are currently investigating an issue that is affecting the stability and uptime of our application.

2. identified Jan 22, 2026, 08:59 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Jan 22, 2026, 09:22 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Jan 22, 2026, 10:09 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 22, 2026, 03:43 PM UTC· resolved Jan 23, 2026, 03:57 AM UTC

1. investigating Jan 22, 2026, 03:43 PM UTC

   We are currently investigating an issue impacting email delivery to recipients with @hotmail.com and @outlook.com email addresses. Our team is actively working with our email provider to identify the root cause and restore normal delivery as quickly as possible. We will share updates as more information becomes available. Please be aware that delivery to other email domains is not impacted at this time.

2. identified Jan 22, 2026, 03:57 PM UTC

   We have identified the cause of the email delivery issue affecting @hotmail.com and @outlook.com recipients. Microsoft is currently blocking messages from one of our sending IPs as part of their automated filtering controls. Our team is working directly with our email provider and Microsoft to have the block reviewed and removed. We will continue to share updates as we progress in resolving this issue.

3. resolved Jan 23, 2026, 03:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 25, 2025, 06:37 PM UTC· resolved Jul 25, 2025, 10:18 PM UTC

1. investigating Jul 25, 2025, 06:37 PM UTC

   We are currently investigating an incident where integrated Bullhorn customers have reported authentication issues. While this seems to have resolved, we are currently investigating the root cause.

2. monitoring Jul 25, 2025, 07:34 PM UTC

   Issue Summary: Between 11:30 AM and 11:40 AM PST, some users experienced authentication errors when accessing RefAssured within Bullhorn. Root Cause: We identified the issue stemmed from our authentication provider, AWS Cognito. Resolution: The service has been restored to normal operation. We are working with AWS Support to conduct a full root cause analysis and will publish a detailed post-mortem once complete. Current Status: All systems are operating normally. We are continuing to monitor closely as a precautionary measure.

3. resolved Jul 25, 2025, 10:18 PM UTC

   After monitoring service for the last few hours and confirmation from AWS, this incident has been resolved. Post-Mortem: Authentication Service Disruption January 25, 2025 Incident Summary On January 25, 2025, RefAssured users experienced authentication errors when accessing the platform through Bullhorn. The incident lasted approximately 10 minutes, from 11:30 AM to 11:40 AM PST, affecting users' ability to sign in to the service. Timeline 11:21 AM PST - AWS Cognito (US-EAST-2) begins experiencing increased API error rates 11:25 AM PST - AWS engineering team automatically engaged 11:30 AM PST - RefAssured users begin experiencing authentication issues 11:37 AM PST - AWS implements mitigation action, recovery begins 11:40 AM PST - RefAssured authentication errors resolved 12:08 PM PST - AWS confirms full service recovery across all affected services What Happened Our authentication system relies on Amazon Web Services (AWS) to verify user logins. AWS experienced a technical issue when they deployed a software update to one of their core systems. This update caused problems with their authentication services across multiple regions, which prevented RefAssured users from logging in. AWS quickly identified the problematic update and rolled it back to restore service. While the broader AWS issue took longer to fully resolve, RefAssured users were able to log in normally again within 10 minutes. Impact Duration: 10 minutes of user impact (11:30 AM - 11:40 AM PST) Scope: Users attempting to log into RefAssured via Bullhorn Effect: New logins were blocked; users already logged in were not affected Resolution AWS rolled back their problematic software update, which restored RefAssured's authentication service by 11:40 AM PST. No action was required from RefAssured users. What We're Doing Next 1) Better Monitoring: We're adding extra alerts to detect authentication issues faster 2) Improved Communication: We're reviewing how quickly we communicate during outages 3) Backup Options: We're exploring additional authentication options to reduce reliance on any single provider Prevention While this issue was caused by our service provider and outside our direct control, we're taking steps to make our system more resilient and improve how we respond to similar situations in the future. We sincerely apologize for the inconvenience this caused. If you have questions about this incident, please contact our support team.

Read the full incident report →