BrightMove Status - Incident history

Downgraded Reporting and Analytics Data

Tue, 11 Aug 2026 21:02:50 +0000

Type: Incident

Duration: 5 days, 23 hours and 8 minutes

Affected Components: ,

Aug 11, 22:59:25 GMT+0
Identified - We have identified the underlying issue in our data pipeline and have corrected the problem. We are currently re-syncing data through our pipeline and will provide an additional update after the pipeline is completely repopulated..

Aug 11, 21:02:50 GMT+0
Investigating - We are currently investigating an issue affecting our Reporting and Analytics platform. Due to a disruption in our data pipeline, the data powering these features has not updated since August 10, 2026 at approximately 8:27 AM EST. During this time, reports and analytics may reflect outdated information. We are actively working to identify the root cause and restore normal data flow as quickly as possible. We will provide updates as our investigation progresses. .

Aug 12, 17:11:23 GMT+0
Monitoring - All data for analytics and reporting systems has re-synced and we continue to monitor these systems to ensure everything remains fully functional..

Aug 17, 20:10:36 GMT+0
Resolved - This incident has been resolved..

Maintenance on Power Search Servers

Wed, 4 Mar 2026 17:53:15 +0000

Type: Incident

Duration: 20 hours and 3 minutes

Affected Components:

Mar 4, 17:53:15 GMT+0
Investigating - We're performing some emergency maintenance on the power search servers in order to resolve a data ingestion issue causing stability problems in our search cluster. We expect the partial outage to be resolved within the hour..

Mar 5, 13:56:22 GMT+0
Resolved - Our team has completed the Maintenance we were performing on the Power Search Servers. The servers are now stable and usage is now in normal parameters. This issue is now resolved..

Indeed Applications

Wed, 25 Feb 2026 22:07:14 +0000

Type: Incident

Duration: 22 hours and 1 minute

Affected Components:

Feb 25, 22:07:14 GMT+0
Investigating - BrightMove has not received any inbound candidate applications from Indeed since 2:40pm EST today, 2/25/2026\. We have contacted Indeed and are working with their team as they investigate this issue. We do not currently have an ETA on when this will be resolved, but we will provide further updates as we receive them..

Feb 26, 20:08:27 GMT+0
Resolved - As of 2:32 PM EST on February 26, 2026, Indeed has confirmed that all applications submitted during the outage have been successfully resent to BrightMove. There are no outstanding applications pending processing. This outage was caused by an AWS issue that affected Indeed. This issue has now been resolved..

Feb 26, 00:52:04 GMT+0
Monitoring - Inbound candidate application have resumed from Indeed, we are monitoring applications as we continue to investigate the cause with Indeed..

Indeed Apply Parsing Issue

Thu, 29 Jan 2026 19:19:41 +0000

Type: Incident

Duration: 3 days, 19 hours and 46 minutes

Affected Components:

Jan 29, 19:19:41 GMT+0
Identified - Our team has been made aware of an issue with the Indeed Apply feature and that some candidates are being loaded into the ATS with the name "Indeed Connect". This appears to be because Indeed is now including a marketing cover page within the application advertising a new feature called Indeed Connect. We are not aware of any changes within ATS that would have caused this, and have opened a case with Indeed asking for them to revert the change of behavior..

Jan 29, 19:51:41 GMT+0
Identified - We have received feedback from Indeed that their team is investigating this issue on their end. Unfortunately, there is not an ETA on a resolution at this time..

Feb 2, 15:05:32 GMT+0
Resolved - This incident has been resolved..

Jan 30, 15:04:24 GMT+0
Identified - We have identified that Indeed is adding Summary Pages to resumes when candidates are applying. These are causing issues with the parsing of candidates into the ATS. We are continuing to work with Indeed on a fix for this incident..

Planned Cloud Infrastructure Maintenance & Performance Tuning

Sat, 17 Jan 2026 13:00:00 +0000

Type: Maintenance

Duration: 5 hours and 45 minutes

Affected Components: , , , , , , , , , , , , , , ,

Jan 17, 13:00:00 GMT+0
Identified - BrightMove will be conducting planned cloud infrastructure maintenance and performance tuning beginning **Saturday morning, January 17**. **The platform will be unavailable for a multi-hour period (approximately three hours or more) on Saturday morning and may experience intermittent unavailability at times throughout the remainder of the weekend.** During this maintenance window, some or all system functionalities may be unavailable. For ongoing updates, please monitor this Status Page. This is BrightMove’s official channel for maintenance and availability notifications, and you may subscribe to receive real-time updates. We appreciate your patience and understanding..

Jan 17, 13:00:01 GMT+0
Identified - Maintenance is now in progress.

Jan 17, 17:29:17 GMT+0
Identified - Maintenance is still in progress. We will let you know once completed..

Jan 17, 18:45:19 GMT+0
Completed - Maintenance has completed successfully..

UI Error

Fri, 5 Dec 2025 19:02:27 +0000

Type: Incident

Duration: 1 hour and 43 minutes

Dec 5, 19:02:27 GMT+0
Investigating - We have identified an issue within the UI that is causing an error for users. We are currently investigating this incident..

Dec 5, 19:21:48 GMT+0
Identified - We have found where the error is originating from. This error is affecting several primary functions within the ATS including Dashboards, Power Searches, Folders and others. We are continuing to work on a fix for this incident. We will provide further updates as soon as we have a fix in place for this issue..

Dec 5, 19:27:50 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Dec 5, 20:45:22 GMT+0
Resolved - This incident has been resolved. All operations are normal..

Reporting Systems

Mon, 20 Oct 2025 12:30:08 +0000

Type: Incident

Duration: 1 day, 1 hour and 28 minutes

Oct 20, 12:30:08 GMT+0
Identified - Reporting systems are not currently functioning properly. We have identified the source of this outage and are working to resolve this issue..

Oct 20, 13:14:21 GMT+0
Identified - We have identified an issue with AWS that could potentially impact all aspects of the BrightMove ATS. We are monitoring the issue with AWS and are waiting for a resolution on their end. AWS is updating every 30 mins. Their most recent update is as follows: **Increased Error Rates and Latencies** **Oct 20 7:14 AM PDT** We can confirm significant API errors and connectivity issues across multiple services in the US-EAST-1 Region. We are investigating and will provide further update in 30 minutes or sooner if we have additional information..

Oct 20, 14:32:57 GMT+0
Identified - We have received another update from AWS on this issue: **Oct 20 7:29 AM PDT** We have confirmed multiple AWS services experienced network connectivity issues in the US-EAST-1 Region. We are seeing early signs of recovery for the connectivity issues and are continuing to investigate the root cause..

Oct 20, 15:10:18 GMT+0
Identified - AWS Update: **Oct 20 8:04 AM PDT** We continue to investigate the root cause for the network connectivity issues that are impacting AWS services such as DynamoDB, SQS, and Amazon Connect in the US-EAST-1 Region. We have identified that the issue originated from within the EC2 internal network. We continue to investigate and identify mitigations..

Oct 20, 15:47:13 GMT+0
Identified - AWS Update: **Oct 20 8:43 AM PDT** We have narrowed down the source of the network connectivity issues that impacted AWS Services. The root cause is an underlying internal subsystem responsible for monitoring the health of our network load balancers. We are throttling requests for new EC2 instance launches to aid recovery and actively working on mitigations..

Oct 20, 16:20:21 GMT+0
Identified - AWS Update: **Oct 20 9:13 AM PDT** We have taken additional mitigation steps to aid the recovery of the underlying internal subsystem responsible for monitoring the health of our network load balancers and are now seeing connectivity and API recovery for AWS services. We have also identified and are applying next steps to mitigate throttling of new EC2 instance launches. We will provide an update by 10:00 AM PDT..

Oct 20, 17:15:28 GMT+0
Identified - AWS Update: **Oct 20 10:03 AM PDT** We continue to apply mitigation steps for network load balancer health and recovering connectivity for most AWS services. Lambda is experiencing function invocation errors because an internal subsystem was impacted by the network load balancer health checks. We are taking steps to recover this internal Lambda system. For EC2 launch instance failures, we are in the process of validating a fix and will deploy to the first AZ as soon as we have confidence we can do so safely. We will provide an update by 10:45 AM PDT..

Oct 20, 17:44:11 GMT+0
Identified - AWS Update: **Oct 20 10:38 AM PDT** Our mitigations to resolve launch failures for new EC2 instances are progressing and the internal subsystems of EC2 are now showing early signs of recovering in a few Availability Zones (AZs) in the US-EAST-1 Region. We are applying mitigations to the remaining AZs at which point we expect launch errors and network connectivity issues to subside..

Oct 20, 20:38:07 GMT+0
Identified - AWS Update: **Oct 20 1:03 PM PDT** Service recovery across all AWS services continues to improve. We continue to reduce throttles for new EC2 Instance launches in the US-EAST-1 Region that were put in place to help mitigate impact. Lambda invocation errors have fully recovered and function errors continue to improve. We have scaled up the rate of polling SQS queues via Lambda Event Source Mappings to pre-event levels. We will provide another update by 1:45 PM PDT..

Oct 20, 18:32:51 GMT+0
Identified - AWS Update: **Oct 20 11:22 AM PDT** Our mitigations to resolve launch failures for new EC2 instances continue to progress and we are seeing increased launches of new EC2 instances and decreasing networking connectivity issues in the US-EAST-1 Region. We are also experiencing significant improvements to Lambda invocation errors, especially when creating new execution environments (including for Lambda@Edge invocations). We will provide an update by 12:00 PM PDT..

Oct 20, 19:17:13 GMT+0
Identified - AWS Update: **Oct 20 12:15 PM PDT** We continue to observe recovery across all AWS services, and instance launches are succeeding across multiple Availability Zones in the US-EAST-1 Regions. For Lambda, customers may face intermittent function errors for functions making network requests to other services or systems as we work to address residual network connectivity issues. To recover Lambda’s invocation errors, we slowed down the rate of SQS polling via Lambda Event Source Mappings. We are now increasing the rate of SQS polling as we experience more successful invocations and reduced function errors. We will provide another update by 1:00 PM PDT..

Oct 20, 20:58:34 GMT+0
Monitoring - We have seen much improvement across the ATS and are now monitoring the situation. AWS Update: **Oct 20 1:52 PM PDT** We have continued to reduce throttles for EC2 instance launches in the US-EAST-1 Region and we continue to make progress toward pre-event levels in all Availability Zones (AZs). AWS services such as ECS and Glue, which rely on EC2 instance launches will recover as the successful instance launch rate improves. We see full recovery for Lambda invocations and are working through the backlog of queued events which we expect to be full processed in approximately in the next two hours. We will provide another update by 2:30 PM PDT..

Oct 21, 13:58:32 GMT+0
Resolved - This incident has been resolved. Final update from AWS: **Oct 20 3:53 PM PDT** Between 11:49 PM PDT on October 19 and 2:24 AM PDT on October 20, we experienced increased error rates and latencies for AWS Services in the US-EAST-1 Region. Additionally, services or features that rely on US-EAST-1 endpoints such as IAM and DynamoDB Global Tables also experienced issues during this time. At 12:26 AM on October 20, we identified the trigger of the event as DNS resolution issues for the regional DynamoDB service endpoints. After resolving the DynamoDB DNS issue at 2:24 AM, services began recovering but we had a subsequent impairment in the internal subsystem of EC2 that is responsible for launching EC2 instances due to its dependency on DynamoDB. As we continued to work through EC2 instance launch impairments, Network Load Balancer health checks also became impaired, resulting in network connectivity issues in multiple services such as Lambda, DynamoDB, and CloudWatch. We recovered the Network Load Balancer health checks at 9:38 AM. As part of the recovery effort, we temporarily throttled some operations such as EC2 instance launches, processing of SQS queues via Lambda Event Source Mappings, and asynchronous Lambda invocations. Over time we reduced throttling of operations and worked in parallel to resolve network connectivity issues until the services fully recovered. By 3:01 PM, all AWS services returned to normal operations. Some services such as AWS Config, Redshift, and Connect continue to have a backlog of messages that they will finish processing over the next few hours. We will share a detailed AWS post-event summary..

Wisdom Analytics Data

Mon, 4 Aug 2025 12:33:50 +0000

Type: Incident

Duration: 2 days, 5 hours and 49 minutes

Affected Components: ,

Aug 6, 18:19:23 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Aug 6, 18:22:44 GMT+0
Resolved - This incident has been resolved..

Aug 4, 12:33:50 GMT+0
Identified - We are currently experiencing a delay in the sync of data from our source OLTP systems to our Wisdom data warehouse. We are working with our vendor to expedite the fix on their end and to restore timely analytics and adhoc reporting..

Aug 6, 13:22:17 GMT+0
Identified - The warehouse data for adhoc reporting and some custom reports is being reloaded. Reports and analytics might be inaccurate for the next 6-8 hours. Thanks for your patience as we work through this issue with our vendor..

Analytics and Reporting

Thu, 31 Jul 2025 14:18:44 +0000

Type: Incident

Duration: 22 hours and 44 minutes

Affected Components: ,

Aug 1, 13:03:14 GMT+0
Resolved - This incident has been resolved..

Jul 31, 14:18:44 GMT+0
Investigating - We have detected an issue that is causing issues with the Analytics and Reporting systems, this may effect data accuracy temporarily. We are currently investigating this issue. .

Jul 31, 15:10:58 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Candidate Portal Resume Parsing Issue

Fri, 21 Mar 2025 13:38:56 +0000

Type: Incident

Duration: 10 days, 3 hours and 19 minutes

Affected Components: ,

Mar 21, 13:38:56 GMT+0
Investigating - We are currently investigating an issue involving Candidates uploading resumes while applying to a job. Uploaded resumes are not parsing the resume text into the Resume tab of their Candidate Profile. When a Candidate Copy/Pastes their resume while applying is still working properly. .

Mar 31, 16:57:38 GMT+0
Resolved - This incident has been resolved..

Mar 22, 22:35:37 GMT+0
Monitoring - A fix was implemented and we have been monitoring the situation..

Mar 21, 14:42:36 GMT+0
Identified - We believe we have identified the underlying cause of this issue and are working towards implementing a fix..

Indeed Apply and Basic Qualifications

Mon, 2 Dec 2024 19:14:22 +0000

Type: Incident

Duration: 22 hours and 26 minutes

Affected Components:

Dec 2, 19:14:22 GMT+0
Investigating - Multiple customers have reported an issue with Indeed Apply and the absence of answers to Basic Qualifications coming across the Indeed Apply API. We are currently investigating this issue as a high priority and will update as soon as we have more information of the root cause..

Dec 2, 20:41:50 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Dec 3, 17:40:43 GMT+0
Resolved - **Incident Update: Indeed Apply & Basic Qualifications Issue** **Issue Overview:** On **November 26, 2024**, around **1:30 PM ET**, an issue arose due to a deployment of a new **Indeed job feed specification**, which was required by **Indeed** to continue using the **Indeed Apply** function after **April 1, 2025**. The change specifically involved updates to the **Screener Questions** (synonymous with **Basic Qualifications - BQs**) format. Indeed provided specific feedback indicating the scope of the changes before and after that the changes were complete, leading the ATS team to believe there was no impact. However, this feedback was incorrect, resulting in the failure to properly capture BQ answers in the ATS for applicants who applied between **November 26, 2024**, and **December 2, 2024**. **Impact:** Applicants who applied during this period were asked BQs, but their responses were not captured in the ATS and saved as attachments to their profile. **Resolution:** A **hotfix** was deployed on **December 2, 2024**, at **3:15 PM ET**, to address the issue. However, the affected applicants' BQ responses still need to be retrieved. **What We Have Done:** This morning, on **December 3, 2024**, we deployed a configuration to all affected customers. A public, shared applicant folder titled **"Candidates from Indeed without BQs - 11/26/2024 - 12/02/2024"** has been created. This folder contains applicants who applied through Indeed Apply, but whose BQs were not properly saved in the ATS. The folder is accessible from the **My Candidates Folder** dashboard pane and the **Candidate Folders** menu item. **Next Steps:** We are actively working with **Indeed's technical support team** to determine if it is possible to replay the applications from the affected time period to properly capture the missed BQs. We do not have a solution in place yet, but we are diligently collaborating with Indeed to resolve this issue. We sincerely **apologize for any inconvenience** this may have caused and appreciate your patience as we work toward a resolution..

Dec 4, 20:30:23 GMT+0
Resolved - **Update: Application replay completed successfully** At approximately 2:30pm ET today, with the assistance of Indeed technical support, we completed the replay of all applications that occurred between 11/26 and 12/2, in which Basic Qualifications answers were not received. Customers with applicants who applied during this window should now their complete Indeed resume profile and associated screener questions with the answers that were supplied during the original application submittal. We are now marking this incident as fully resolved..

BrightSync Connectivity

Mon, 28 Oct 2024 17:21:32 +0000

Type: Incident

Duration: 13 days, 20 hours and 25 minutes

Affected Components:

Oct 28, 17:21:32 GMT+0
Identified - We are continuing to work on a fix for this incident..

Dec 6, 12:26:58 GMT+0
Identified - **Incident Update: BrightSync Module Impact** **Issue Overview:** On **October 28, 2024**, an issue arose due to Microsoft's deprecation of the API previously used for integrating with Outlook. Microsoft has mandated a transition to their **Graph API** for email service interactions, which directly impacted BrightMove users utilizing **BrightSync** with Outlook. BrightMove implemented the required coding changes to support the **Graph API**, but as a result, the BrightSync service now only supports **Office 365** and no longer supports the legacy **Microsoft Exchange** product. **Impact:** This change temporarily disrupted BrightSync's ability to integrate with Outlook for affected users. Legacy Microsoft Exchange users will no longer be supported. **Resolution:** The updated BrightSync functionality will be rolled out over the next several days to restore integrated services for Outlook users on Office 365. **Customer Action:** Customers using Office 365 can reference the following article for detailed instructions on setting up BrightSync connectivity: [BrightSync - Office 365 Email & Calendar Integration](https://support.brightmove.com/hc/en-us/articles/360043633512-BrightSync-Office-365-Email-Calendar-Integration). **Next Steps:** We encourage customers impacted by the discontinuation of legacy Microsoft Exchange support to transition to Office 365 to maintain BrightSync functionality. If you require assistance or have any questions, please contact our support team. We sincerely **apologize for any inconvenience** this may have caused and thank you for your understanding as we adapt to Microsoft's required changes..

Dec 6, 18:51:03 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Dec 12, 13:46:12 GMT+0
Resolved - This incident has been resolved..

Unable to Send or Download Attachments

Tue, 27 Aug 2024 12:42:08 +0000

Type: Incident

Duration: 1 day, 5 hours and 28 minutes

Affected Components:

Aug 27, 16:31:28 GMT+0
Identified - We are continuing to work on a fix for this incident..

Aug 27, 19:21:06 GMT+0
Identified - The ability to download and send attachments has been partially restored. However, a small but important percentage of files, including resumes, cover letters and basic qualifications, remain unavailable. Engineering is actively working to restore the missing files from archive. The time for restoration is still to be determined, but will take several hours. As a temporary workaround, resume contents are visible via the Resume tab on the Applicant screen, even for affected files. We appreciate your patience and will provide further updates as restoration progresses..

Aug 28, 13:51:39 GMT+0
Identified - Resumes are now restored. The ability to download and send attachments has been partially restored. However, a small but important percentage of files, including cover letters and basic qualifications, remain unavailable. Engineering is actively working to restore the missing files from archive. The time for restoration is still to be determined, but will take several hours. As a temporary workaround, resume contents are visible via the Resume tab on the Applicant screen, even for affected files. We appreciate your patience and will provide further updates as restoration progresses..

Aug 27, 12:42:08 GMT+0
Investigating - We are currently investigating this incident..

Aug 27, 13:15:28 GMT+0
Identified - Currently, our engineering team is investigating an issue reported by customers related to the download and sending of attachments. This issue has been triaged and is being treated as a high priority issue..

Aug 27, 13:32:00 GMT+0
Resolved - Our engineering team has identified root cause of the inability for users to download attachments and has made a corrective fix. Attachments are now fully accessible. This incident has been resolved and our support team will continue to monitor the system for stability..

Aug 28, 18:09:52 GMT+0
Resolved - This incident has been resolved. Attachments including resumes, cover letters, and basic qualification questions can be downloaded and sent in emails..

Missing Icons

Thu, 25 Apr 2024 20:29:44 +0000

Type: Incident

Duration: 1 hour and 8 minutes

Affected Components:

Apr 25, 20:29:44 GMT+0
Identified - We are continuing to work on a fix for this incident..

Apr 25, 21:38:09 GMT+0
Resolved - The issue was due to the outage of a third party cloud provider. This incident has been resolved..

Application Slowness and Availability

Tue, 12 Mar 2024 19:38:51 +0000

Type: Incident

Duration: 1 day, 20 hours and 28 minutes

Affected Components: , , ,

Mar 12, 19:38:51 GMT+0
Investigating - At this, we are seeing issues with the BrightMove ATS application performance. We are currently investigating this incident as a severity 1 issue and are working to restore services as quickly as possible..

Mar 12, 20:07:49 GMT+0
Identified - The engineering team has identified the root cause of the performance bottleneck in the ATS platform and has made a configuration change to improve stability..

Mar 12, 20:20:59 GMT+0
Monitoring - The engineering team has successfully deployed a performance improvement to ATS. We will monitor the platform for performance and stability until the issue is deemed to be resolved..

Mar 13, 14:16:17 GMT+0
Identified - We are aware of continued performance impact this morning and are actively working on performance improvements. The engineering team has deployed additional infrastructure capacity in attempts to improve performance while tuning efforts continue. While the service is online and available to users, we are treating this performance impact as a high severity issue and are working to resolve as soon as possible..

Mar 13, 15:13:28 GMT+0
Identified - Engineering team has identified a slow performing query that is impacting system performance. The development team is currently working on a query rewrite that is optimized to alleviate the impact. Engineering is planning to deploy a hotfix later this afternoon, once the optimized query can be verified. We will update this channel with more details once the HF is deployed..

Mar 13, 18:24:33 GMT+0
Monitoring - At 1:45 pm ET, the engineering team deployed a query hot fix to improve the stability and performance of the ATS platform. The team has been hands on monitoring the platform for the past 45 minutes and KPIs show significant improvement. Engineering will continue to monitor the platform..

Mar 14, 16:07:17 GMT+0
Resolved - We have been monitoring the platform since the performance hotfix deployment yesterday. At this time the engineering & operations team have concluded the incident has been fully resolved. If you have any further issues, please contact support..

Outbound Emails Not Sending

Mon, 19 Feb 2024 15:32:40 +0000

Type: Incident

Duration: 2 days, 22 hours and 46 minutes

Affected Components:

Feb 22, 14:18:15 GMT+0
Resolved - This incident has been resolved..

Feb 20, 19:35:15 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Feb 19, 15:32:40 GMT+0
Investigating - We are currently investigating this incident..

Feb 19, 21:24:50 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Feb 20, 15:07:02 GMT+0
Identified - We are continuing to work on a fix for this incident..

Ad-Hoc Reporting Feed

Tue, 14 Nov 2023 14:57:24 +0000

Type: Incident

Duration: 1 day, 18 hours and 18 minutes

Affected Components:

Nov 14, 14:57:24 GMT+0
Identified - We are continuing to work on a fix for this incident..

Nov 14, 15:46:02 GMT+0
Identified - We are continuing to work on a fix for this incident..

Nov 14, 15:39:41 GMT+0
Resolved - This incident has been resolved..

Maintenance Release: Version 2023.10.0

Sat, 28 Oct 2023 03:00:00 +0000

Type: Maintenance

Duration: 1 hour and 14 minutes

Affected Components: , ,

Oct 28, 03:00:01 GMT+0
Identified - Maintenance is now in progress.

Oct 28, 03:00:00 GMT+0
Identified - We are releasing BrightMove version 2023.10.0 on Friday, October 27, 2023 at 11pm Eastern. There may be short periods during the scheduled deployment window when BrightMove is slow or unavailable..

Oct 28, 04:14:23 GMT+0
Completed - Maintenance has completed successfully..

Oct 28, 04:14:48 GMT+0
Completed - Maintenance has completed successfully..

Adhoc Reporting Feed Delays

Tue, 19 Sep 2023 12:20:44 +0000

Type: Incident

Duration: 1 hour and 57 minutes

Affected Components:

Sep 19, 14:17:23 GMT+0
Resolved - This incident has been resolved..

Sep 19, 12:20:44 GMT+0
Investigating - ### Summary The hourly adhoc reporting data pipeline is experiencing intermittent failures and/or delays. ### Impact to Customers Adhoc report data may be not be as current as is expected (updated hourly) until this issue is resolved. All reporting functionality and scheduled reports continue to work..

Sep 19, 12:38:08 GMT+0
Identified - Root cause has been identified and we are starting the data pipline. Current adhoc reporting data should be available within 10 minutes..

Sep 19, 12:58:36 GMT+0
Monitoring - The adhoc data pipeline is successfully updating reporting data. We will continue to monitor the status to ensure updated data is available to reports..

Maintenance Release: Version 2023.9.0

Sat, 16 Sep 2023 03:00:00 +0000

Type: Maintenance

Duration: 1 hour and 49 minutes

Affected Components: ,

Sep 16, 03:00:01 GMT+0
Identified - Maintenance is now in progress.

Sep 16, 04:49:06 GMT+0
Completed - Maintenance has completed successfully..

Sep 16, 03:00:00 GMT+0
Identified - We are releasing BrightMove version 2023.9.0 on Friday, September 15, 2023 at 11pm Eastern. There may be short periods during the scheduled deployment window when BrightMove is slow or unavailable..

Indeed Quick Apply

Thu, 10 Aug 2023 17:37:34 +0000

Type: Incident

Duration: 4 days, 1 hour and 20 minutes

Affected Components: ,

Aug 11, 14:36:33 GMT+0
Monitoring - We implemented a fix with the help of Indeed and are currently monitoring the results..

Aug 10, 17:37:34 GMT+0
Identified - We have an identified an issue where applicants from Indeed Quick Apply do not appear inside BrightMove. We are continuing to work on a fix for this incident..

Aug 10, 21:06:58 GMT+0
Monitoring - We implemented a fix and are currently working with Indeed to ensure applications are properly moving through the Indeed Quick Apply integration..

Aug 14, 18:57:37 GMT+0
Resolved - This incident has been resolved..

Server Slowness / Outage

Thu, 20 Jul 2023 19:30:38 +0000

Type: Incident Affected Components: SourceJet, Outbound Email, BrightSync, Email and Resume Parser, BrightMove ATS Application, File Converter, Analytics, Web Site, Power Search and Portal Job Search, Onboarding BPM Engine, BrightTerms, Indeed Apply, ZipRecruiter Apply, Candidate Experience Portals, Third Party: Amazon Web Services (AWS) → AWS elasticache-us-east-1, Third Party: Amazon Web Services (AWS) → AWS elb-us-east-1, Third Party: Amazon Web Services (AWS) → AWS lambda-us-east-1, Third Party: Amazon Web Services (AWS) → AWS rds-us-east-1, Third Party: Amazon Web Services (AWS) → AWS route53-us-east-1, Third Party: Amazon Web Services (AWS) → AWS s3-us-east-2, REST API, Third Party: Amazon Web Services (AWS) → AWS ec2-us-east-1, Third Party: Amazon Web Services (AWS) → AWS elasticbeanstalk-us-east-1, Reporting Jul 20, 19:30:38 GMT+0 - Resolved - Today at 1:30pm EST an issue regarding high memory usage was causing users to experience slow load times or disconnections from the server. We increased our memory allocation, and the issue was resolved at 2:15pm EST. We will be releasing an update tonight at 11pm EST to add further safeguards against high memory usage.

ITC Premier Single Sign-On - 404 Error Page

Mon, 17 Jul 2023 13:44:22 +0000

Type: Incident

Duration: 2 days and 28 minutes

Affected Components:

Jul 17, 13:46:46 GMT+0
Investigating - We are continuing to work on a fix for this incident. Users affected by this error may use the link below as a temporary work around until the full issue is resolved. You will need to input your Username and Password within this link. [https://insperity.brightmove.com/](url).

Jul 17, 13:44:22 GMT+0
Investigating - We are currently investigating this incident. This is a specific outage incident for the users described below. Users that log into the BrightMove system through ITC Premier are currently experiencing a 404 error when attempting to use the single sign-on method. Our staff is aware of this issue and have placed this into our highest tier of priority. We will be working diligently to correct this issue as soon as possible with further updates provided as more information is known. We thank all affected users for their patience as we work to provide the quickest resolution possible. .

Jul 18, 17:42:57 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result. The underlying issue should be resolved at this time. Premier users may now access the BrightMove ATS from their Talent Connect portal. It is recommended that all Premier users clear their browser cache before attempting to log in via the Premier Talent Connect portal. .

Jul 17, 16:24:08 GMT+0
Identified - We are continuing to work on a fix for this incident. Our team has identified the issue and are working to provide the quickest resolution possible. More updates will be made available soon. .

Jul 17, 21:32:45 GMT+0
Identified - We are continuing to work on a fix for this incident. Our team is continuing to work towards a permanent solution to this issue. Another update will be provided once the fix has been implemented. .

Jul 19, 14:12:27 GMT+0
Resolved - This incident has been resolved..

Maintenance Release: Version 2023.6.0

Sat, 15 Jul 2023 12:00:00 +0000

Type: Maintenance

Duration: 4 hours

Affected Components: , , , , , , , , , , , , , , ,

Jul 15, 12:00:00 GMT+0
Identified - Upcoming Scheduled Maintenance Notice We are releasing BrightMove version 2023.6.0 on Saturday, July 15, 2023 at 8am Eastern. There may be short periods during the scheduled deployment window when BrightMove is slow or unavailable. [Release Notes](https://support.brightmove.com/hc/en-us/articles/17038559259035-Version-2023-6-0).

Jul 15, 12:00:01 GMT+0
Identified - Maintenance is now in progress.

Jul 15, 16:00:00 GMT+0
Completed - Maintenance has completed successfully.

Slow Page Loading Times

Tue, 30 May 2023 17:47:44 +0000

Type: Incident

Duration: 6 hours and 3 minutes

Affected Components:

May 30, 17:47:44 GMT+0
Identified - We are continuing to work on a fix for this incident..

May 30, 21:04:32 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

May 30, 23:50:31 GMT+0
Resolved - This incident has been resolved..

Infrastructure Maintenance

Sat, 6 May 2023 17:00:00 +0000

Type: Maintenance

Duration: 1 hour and 39 minutes

Affected Components:

May 6, 17:00:01 GMT+0
Identified - Maintenance is now in progress.

May 6, 18:38:49 GMT+0
Completed - Maintenance has completed successfully..

May 6, 17:00:00 GMT+0
Identified - Upcoming Scheduled Maintenance Notice We are performing maintenance on Job Portals on Saturday, May 6, 2023 at 1pm Eastern. There may be short periods during the scheduled maintenance window when Job Portals are unavailable..

Ad-Hoc Report Suite Not Displaying Correctly

Mon, 1 May 2023 14:27:46 +0000

Type: Incident

Duration: 5 hours and 7 minutes

Affected Components:

May 1, 14:27:46 GMT+0
Investigating - We are currently investigating this incident. Our team will continue to provide updates as progress is made on the Ad-Hoc tool. .

May 1, 15:12:08 GMT+0
Identified - We are continuing to work on a fix for this incident. The correction for this issue is estimated to complete in 3 hours time. More updates will be sent once more information is available..

May 1, 19:34:34 GMT+0
Resolved - The Ad-Hoc reporting suite has been restored. All saved reports and tools should be available at this time. If you continue to experience any issues with the Ad-Hoc tool, please contact our support staff via chat or email: support@brightmove.com. .

Candidate Experience Portals attached to EJOB.BZ domain currently unavailable

Tue, 25 Apr 2023 15:24:41 +0000

Type: Incident

Duration: 47 minutes

Affected Components:

Apr 25, 15:24:41 GMT+0
Identified - We are currently experiencing issues with the Candidate Experience Portal that impacts some of our customer (customers with websites tied to Portal URL using ejob.bz domain name). Our engineering team is working on implementing a resolution actively and we will update with more details shortly..

Apr 25, 16:08:04 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Apr 25, 16:11:23 GMT+0
Resolved - This incident has been resolved..

Maintenance Release: Version 2023.5.0

Sat, 1 Apr 2023 03:00:00 +0000

Type: Maintenance

Duration: 52 minutes

Affected Components: , , , , , , , , , , , , , ,

Apr 1, 03:51:41 GMT+0
Completed - Maintenance has completed successfully..

Apr 1, 03:20:21 GMT+0
Identified - Verification is currently underway for the maintenance items..

Apr 1, 03:00:00 GMT+0
Identified - Upcoming Scheduled Maintenance Notice We are releasing BrightMove version 2023.5.0 on Friday, March 31, 2023 at 11pm Eastern. There may be short periods during the scheduled deployment window when BrightMove is slow or unavailable. [Release Notes](https://support.brightmove.com/hc/en-us/articles/14073088432027-Version-2023-5-0).

Apr 1, 03:00:01 GMT+0
Identified - Maintenance is now in progress.

Maintenance Release: Version 2023.4.0

Sat, 11 Mar 2023 04:00:00 +0000

Type: Maintenance

Duration: 28 minutes

Affected Components: , , , , , , , , , , , , , ,

Mar 11, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Mar 11, 04:28:09 GMT+0
Completed - Maintenance has completed successfully..

Mar 11, 04:07:34 GMT+0
Identified - Verification is currently underway for the maintenance items..

Mar 11, 04:00:00 GMT+0
Identified - Upcoming Scheduled Maintenance Notice We are releasing BrightMove version 2023.4.0 on Friday, March 10, 2023 at 11pm Eastern. There may be short periods during the scheduled deployment window when BrightMove is slow or unavailable. This is a maintenance release and will contain several system performance improvements and bug fixes. [Release Notes](https://support.brightmove.com/hc/en-us/articles/13490722740635-Version-2023-4-0).