Is Bloomreach Down Right Now? Check if there is a current outage ongoing.

We are currently investigating this issue.

This incident has been resolved.

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

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

We are currently investigating this issue. The impact is lag processing tracking from integrations on US3.

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

We are currently investigating this issue. The impact is lag processing tracking from integrations on US3.

This incident has been resolved.

We have deployed several measures and we no longer observe the impact. We are continuing to monitor the situation

The impact of the incident is intermittent. We are continuing to investigate the root cause of the issue

We are continuing to investigate this issue.

There are multiple campaign services having an issue, either being slow, or returning 5xx error. Includes transactional emails, on event triggers, campaign event tracking, public url redirections

The issue has been resolved.

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

The issue has been identified and, the instance is processing the accumulated lag.

We are currently investigating this issue.

We are pleased to inform you the Bloomreach dashboard is now accessible to all clients.

Bloomreach dashboard is now operational and we are continuing to monitor. Our apologies for the inconvenience.

Bloomreach dashboard is currently unavailable due to an issue with our authentication service. We are actively working in resolving the issue. We apologize for the inconvenience and will continue to provide you updates. Should you have any questions, please feel free to reach out to support@bloomreach.com

Dear Customer, We are pleased to inform you the Bloomreach dashboard is now fully operational. Best regards, Bloomreach Support Team

Dear Customer, Our engineering team had identified the issue and a fix has been applied for the same. We will continue to monitor. Best regards, Bloomreach Support Team

Dear Customer, Our engineering team had identified the issue and a fix has been applied for the same. We will continue to monitor. Best regards, Bloomreach Support Team

We are continuing to investigate this issue.

Dear Customer, We have detected an issue in the Bloomreach search and merchandising dashboard. Dashboard users are intermittently facing issues loading the search and merchandising dashboard . Our Engineering team is aware and is actively investigating the issue. Kind regards, Bloomreach Support team

This incident has been resolved.

There is a delay in the data processing related to data consumption, including imports and tracking.

The lag was successfully processed. This incident has been resolved.

A fix has been implemented and we are monitoring the results. The current lag on tracking and imports should be resolved within an hour from now.

There are currently delays in tracking and importing processes. The issue is being investigated.

We are currently investigating this issue. Affected modules: imports.

All customer stacks have been upgraded to the latest BRC version with a patch for this issue. The Site Protection and CMS Maintenance Mode features should no longer create any issues or outages in conjunction with production environment switches and/or Blue/Green deployments. If you notice any further issues in this area, please contact support.

We are currently rolling out a patch release to all customer stacks to resolve this issue. You may notice the maintenance banner in your Mission Control. The rollout should be completed within a few hours.

Dear Customer, We have identified the bug in the "Set Production Environment" logic [https://xmdocumentation.bloomreach.com/bloomreach-cloud/reference-documentation/mark-an-environment-as-production.html], and we are working on a patch. We expect the patch to be rolled out to all customer stacks within two business days. If you must do a Production deployment, please disable the Site Protection and CMS Maintenance Mode in both the source and target (Blue and Green) environments, before starting the deployment process, and only re-enable it/them after the entire deployment process (including production switch) is complete. If you have any further questions or need additional assistance, please reach out to support. Apologies for the inconvenience caused. Best regards, Bloomreach Support Team

Dear Customer, We are once again observing issues with our Site Protection and CMS Maintenance Mode features [https://xmdocumentation.bloomreach.com/bloomreach-cloud/reference-documentation/protect-environment.html] causing downtime during Blue/Green deployments. We recommend delaying any production deployments if either of these features is enabled in your Production Green or Blue environment, until we have deployed a patch. If you must do a Production deployment, please disable the Site Protection and CMS Maintenance Mode in both the source and target (Blue and Green) environments, before starting the deployment process, and only re-enable it after the entire deployment process is complete. If you have any further questions or need additional assistance, please reach out to support. Apologies for the inconvenience caused. Best regards, Bloomreach Support Team

The vendor has restored the DNS settings. The DNS now correctly resolve and issue is therefore fixed

We have changed the default cdn domain to cin-cdn.bloomreach.co. Newly sent emails that do not use custom cnd domain will therefore use this domain for click tracking, etc. Links in emails sent before this change will be unreachable unless the DNS for the original domain is restored.

To mitigate the DNS issues for infinario.com domains and subdomains, as a backup, it's possible to use these domains instead. This applies to the app, tracking to api in all SDKs, etc. cloud.infinario.com -> cin.bloomreach.co api.infinario.com -> cin-api.bloomreach.co public.infinario.com -> cin-cdn.bloomreach.co

After the discussion with the vendor support, we have contacted a specialized team that handles the type of issue that is impacting us. Their expected resolution times are not acceptable, and as such we are preparing another domain as a backup. Customer action will be required for the backup solution to work.

We are still in contact with the vendor support. We have not reached resolution with them yet

A vendor providing DNS records suspended DNS for infinario.com domains due to reasons currently unknown to us. As a result, on CIN (cloud.infinario.com) domain and any private domain hosted on infinario.com, the engagement platform, it's tracking and external APIs will fail due to DNS resolution. Some users might not yet experience the issues as the DNS might be cached for them, but for any user (including end customer tracking via javascript) without cached DNS, the requests will fail. Our infrastructure team is currently in contact with vendor support to determine the cause and restore the DNS

Dear Customer, Through our investigation we have not been able to reproduce the exact error using the latest version of the BRC (Bloomreach Cloud) platform. We strongly suspect that if either feature was enabled while the stack was running an older BRC (Bloomreach Cloud) version, that the Kubernetes secret created at that point could be at fault. Therefore for all environments currently using either feature, we have regenerated the secrets as a preventative measure. We have run further checks that there are no references to missing secrets. We do not expect further issues with these features during deployments. If you encounter an issue during a production deployment, please submit a high-priority ticket via Urgent@bloomreach.com. For any further questions or additional assistance, please contact the support team. Regards, Bloomreach Team

We are continuing to work on a fix for this issue.

Dear Customer, We are aware of an issue with our Site Protection and CMS Maintenance Mode features [KB article: https://xmdocumentation.bloomreach.com/bloomreach-cloud/reference-documentation/protect-environment.html] causing downtime during blue/green deployments. We recommend delaying any production deployments if either of these features is enabled in your production Green or Blue environment, until we have deployed a patch. Note: We are actively working on the patch and should be ready shortly. If you must do a production deployment, please disable the Site Protection and CMS Maintenance Mode before starting the deployment process, and only re-enable it after the deployment is complete. We apologize for the inconvenience and will update you as soon as we have more information. Best Regards, Bloomreach Team

Dear Customer, We are glad to inform you the feed processing availability has been restored. Please verify the availability of your Bloomreach applications and let us know if you are still experiencing any problems. We apologise for the inconvenience caused. If you have any further questions or need additional assistance, please reach out to support. Best regards, Bloomreach Support team

Dear Customer, A fix has been implemented and we are monitoring the feed ingestion queue to confirm this incident has been resolved. Kind regards, Bloomreach Support team.

Dear Customer, We have detected issues with feed processing for Bloomreach Discovery. Other parts of the platform were not affected. Our engineering team has identified the issue and we are actively monitoring the queued feed ingestion jobs and will confirm once incident has been resolved. Regards, Bloomreach Support Team

Dear Customer, We are glad to inform you the search has been restored. Please verify the availability of your Bloomreach applications and let us know if you are still experiencing any problems. We apologise for the inconvenience caused. If you have any further questions or need additional assistance, please reach out to support. Best regards, Bloomreach Support team

Dear Customer, The issue was identified and a fix has been implemented and we are monitoring to confirm the incident has been resolved. Kind regards, Bloomreach Support Team.

Dear Customer, We are currently experiencing a disruption in the availability of the Bloomreach Search. Our engineering team is involved and actively investigating the issue. We will keep you informed and will update you immediately as soon as we have any more information. Kind regards, Bloomreach Support Team.

Dear Customer, We are glad to inform you the availability of the Bloomreach Tools Dashboard has been restored. Please verify the availability of the dashboard and let us know if you are still experiencing any problems. If you have any further questions or need additional assistance, please let us know. Best regards, Bloomreach Support team

Dear Customer, We are glad to inform you the platform availability of the Bloomreach Tools Dashboard has been restored. We will continue to monitor. Best regards, Bloomreach Support team

We are continuing to monitor for any further issues.

Dear Customer, We are glad to inform you the platform availability of the Bloomreach Tools Dashboard has been restored. We will continue to monitor. Best regards, Bloomreach Support team

Dear Customer, We have detected an issue in the Bloomreach search and merchandising dashboard. Dashboard users are currently facing issues loading the search and merchandising dashboard . Our Engineering team is aware and is further investigating the issue. Kind regards, Bloomreach Support team

Dear Customer, We are pleased to inform you the feed processing capabilities have been fully resolved. Regards, Bloomreach Support Team.

Dear Customer, We had detected issues with feed processing for Bloomreach Discovery .Other parts of the platform were not affected. Our engineering team has implemented the fix and data processing has been resumed. We are actively monitoring the queued feed ingestion jobs and will confirm once incident has been resolved. Regards, Bloomreach Support Team

The lag was entirely processed and the situation is back to normal.

The problematic tracking was blocked. We estimate it might take up to two hours to process the lag and for the situation to go back to normal.

Because of a user error, an usually high amount of events were ingested which overwhelmed our infrastructure. Impact: slower analytics (reports, metrics etc), and a portion of the tracking might be delayed up to two hours.

The incident affecting Google Cloud Services has been resolved. Network connectivity issues impacting multiple products have been addressed, and services are now operating normally. Thank you for your patience during this time. For further details, you can refer to the Google Cloud status page https://status.cloud.google.com/index.html.

We are currently experiencing an ongoing issue with our cloud services provider, Google Cloud, affecting network connectivity across multiple products. This incident has led to intermittent connectivity problems, impacting services and potentially causing disruptions for our clients. Google Cloud is actively working to resolve the issue. We will continue to monitor the situation and provide updates as they become available. For more detailed information, you can follow the status updates on the Google Cloud Incident page ( https://status.cloud.google.com/incidents/xVSEV3kVaJBmS7SZbnre#oKGDLmoneB3YgW79P7vm ) .

Dear Customer, We are pleased to inform you the feed processing capabilities have been fully resolved. Regards, Bloomreach Support Team.

Dear Customer, A fix has been implemented and data processing has been resumed. We are actively monitoring the queued feed ingestion jobs and will confirm once incident has been resolved. Regards, Bloomreach Support Team

Dear Customer, The issue has been identified and our teams are working on implementing the fix. Regards, Bloomreach Support Team.

Dear Customer, We have detected issues with feed processing for Bloomreach Discovery .Other parts of the platform are not affected. Our engineering team is actively involved and further investigating the issue. Regards, Bloomreach Support Team.

This incident has been resolved.

A fix has been implemented the lag is getting processed, we are monitoring the situation.

We are continuing to investigate this issue.

We are currently investigating this issue.

Dear Customer, The situation has remained stable for several hours, the internal monitoring doesn’t show any problem. Therefore, we are closing the incident. The root cause has been identified: a 3rd party tool was upgraded and it introduced a bug that caused networking issue on the nodes of several clusters. The Bloomreach team has identified a list of potential improvement to prevent or mitigate the impact of similar situation in the future. Kind regards, Bloomreach Support team.

Dear Customer, Further mitigation has been applied and the situation is currently stable. However, the team is still observing and closely monitoring the clusters while working on a permanent fix that we expect to rollout tomorrow. As soon as we have any new updates, we will share with you. Kind regards, Bloomreach Support team.

Dear Customer, We are continuing to work with our upstream provider to investigate the internal DNS issue. We do not have an ETA for a resolution at the moment. In the meantime, the Bloomreach SRE team is putting all the effort in order to mitigate the impact on the affected clusters. As soon as we have any new updates, or an estimated resolution time, we will share with you. Kind regards, Bloomreach Support team.

Dear Customer, We are continuing to work with our upstream provider to investigate the internal DNS issue. We do not have an ETA for a resolution at the moment. In the meantime, the Bloomreach SRE team is putting all the effort in order to mitigate the impact on the affected clusters. As soon as we have any new updates, or an estimated resolution time, we will share with you.

Dear Customer, Unfortunately the issue the internal DNS has become apparent again this morning and we are working again with our upstream provider on a resolution of the problem. However, we do not have an ETA at the moment. In the meantime, the Bloomreach SRE team is putting all the effort in order to mitigate the impact on the affected clusters. As soon as we have any new updates, or an estimated resolution time, we will share with you. Kind regards, Bloomreach Support team.

Dear Customer, A fix has been rolled out and the team is monitoring the situation. As soon as we have any new updates, or an estimated resolution time, we will be sure to share it with you. Kind regards, Bloomreach Support team.

Dear Customer, A mitigation action is being applied and the team is monitoring the situation. As soon as we have any new updates, or an estimated resolution time, we will be sure to share it with you. Kind regards, Bloomreach Support team.

Dear Customer, A mitigation action is being applied and the team is monitoring the situation. As soon as we have any new updates, or an estimated resolution time, we will be sure to share it with you. Kind regards, Bloomreach Support team.

Dear Customer, A mitigation action is being applied and the team is monitoring the situation. As soon as we have any new updates, or an estimated resolution time, we will be sure to share with you. Kind regards, Bloomreach Support team.

Dear Customer, The issue has been identified as an internal DNS issue and we are working with our upstream provider on a resolution of the problem. However, we do not have an ETA at the moment. In the meantime, the Bloomreach SRE team is putting all the effort in order to mitigate the impact on the affected clusters. As soon as we have any new updates, or an estimated resolution time, we will share with you. Kind regards, Bloomreach Support team.

Dear Customer, The issue has been identified as an internal DNS issue and we are working with our upstream provider on a resolution of the problem. However, we do not have an ETA at the moment. In the meantime, the Bloomreach SRE team is putting all the effort in order to mitigate the impact on the affected clusters. As soon as we have any new updates, or an estimated resolution time, we will share with you. Kind regards, Bloomreach Support team.

Dear Customer, Our internal monitoring is reporting unavailability of nodes on multiple clusters. We are in close contact with our upstream provider to further investigate the problem. As soon as we have any new updates, or an estimated resolution time, we will share with you. Kind regards, Bloomreach Support team.

Dear Customer, Our internal monitoring is reporting unavailability of nodes on multiple clusters. We are in close contact with our upstream provider to further investigate the problem. As soon as we have any new updates, or an estimated resolution time, we will share with you. Kind regards, Bloomreach Support team.

Dear Customer, Our internal monitoring is reporting unavailability of nodes on multiple clusters. We are in close contact with our upstream provider to further investigate the problem. As soon as we have any new updates, or an estimated resolution time, we will share with you. Kind regards, Bloomreach Support team.

Dear Customer, Our internal monitoring is reporting unavailability of nodes on multiple clusters. We are in close contact with our upstream provider to further investigate the problem. As soon as we have any new updates, or an estimated resolution time, we will share with you. Kind regards, Bloomreach Support team.

Dear Customer, Our internal monitoring is reporting unavailability of nodes on multiple clusters. We are in close contact with our upstream provider to further investigate the problem. As soon as we have any new updates, or an estimated resolution time, we will be sure to share with you. Kind regards, Bloomreach Support team.

Normal traffic for Transactional Email API was restored.

The issue was identified to be caused by an error in configuration related to an update. A fix is being deployed and the transactional API full availability should resume shortly.

We have received multiple reports about Transactional Email API returning errors. We started the investigation.

We are pleased to inform you the incident has been resolved and the Content SaaS CMS application is fully operational.

We are aware that some clients are having issues with our Content SaaS CMS application. We are continuing to monitor. Our apologies for the inconvenience. Should you have any questions, please feel free to reach out to support@bloomreach.com Kind regards, Bloomreach Support team

This incident has been resolved.

The issue has been fixed - teams are monitoring the environment.

Update Impact: Impact is strictly in the UI, no business impact on any existing use cases

The issue has been identified. Fix is on the way ETA ~30minutes

Users are experiencing 4xx errors when navigating withing the Engagement application.

The database was recovered. Tracking and Imports lag was processed and data ingestion is fully operational. Web experience is fully operational. Campaigns lag was processed and campaigns are fully operational.

Our developer team has restarted the database and we can see affected components starting to recover. Monitoring to make sure the lag is being processed as expected.

We are continuing to investigate this issue.

We are currently investigating the issue. Impacted are Web personalization (unavailable), analytics (unavailable), and delay on campaigns and tracking.

Client has been advised not to use a bad design of the campaigns. The lags are now processed and operation back in normal

Internal brokers and replicas were upscaled to help the lag processing. We are currently monitoring the situation.

The issue has been identified at 4:30 CET. The issue has been caused by a huge property update campaign that was manually triggered by one of the clients. Lag is still being processed. There is no data loss.

Campaing event triggers crashlooping on memory. The memory usage is huge. It's being overly processed but still useing huge amount of memory The massive property update is also causing IMF oplog lag Tracking lag currently on 50m

Time: 16:01 and 16:19 CET There was an ext (data) API degradation between 16:01 and 16:19 CET. The system is currently fully operational. Potentially impacted features during this interruption: recommendation serving, catalog API (updates, fetching data), fetching customer attributes. EXP instance has experienced slight delays - the service was otherwise available. EU1 instance has experienced brief service unavailability at some intervals during the mentioned time period.

The lag has been resolved, and the platform is now fully back online. The root cause analysis will be shared with Customer Success Managers in the upcoming days.

We expect the tracking and import lag to be resolved within the next 2 hours. Campaigns are gradually resuming operations and processing accumulated lag, with an estimated completion within the next 2 hours. Regrettably, failed campaigns will require manual restarts. Our next update is scheduled for 23:30 CET or earlier if there are significant changes in the situation.

The platform's recovery is slower than anticipated. Although the application is operational, it's experiencing slowness, resulting in a complete halt of campaign processing. Our next update is scheduled for 22:00 CET or earlier if there are significant changes in the situation.

Our engineering teams have implemented the fix, and platform recovery is now in progress. We anticipate the platform's functionality to be restored within the next 60 minutes. At the moment, the accommodated lag is not yet determined. We'll communicate this information after the platform is fully back online.

Our engineering teams continue to investigate to identify the root cause. We anticipate a potential solution within the next 60 minutes. Our next update is scheduled for 20:30 CET, or earlier if there are significant changes in the situation.

Teams are still investigating and trying to identify the root cause. The scale of impact and ETA is currently not known. We will provide an update at 19:30 CET

We are currently experiencing an outage on the EXP instance. The team is working on a fix.

This incident has been resolved.

Lag has been consumed

The team has identified the issue; the lag is being processed.

We are glad to inform you that processing the data updates from the Bloomreach Engagement platform on the EU1 instance to EBQ was completed, and the service is back to its normal state.

We are glad to inform you that processing the data updates from the Bloomreach Engagement platform on the US1 instance to EBQ was completed, and the service is back to its normal state. We continue to monitor the situation on the EU1 instance, where the processing of the data updates steadily improves.

The issue has been identified and fixed; we are currently monitoring the processing of the delay.

This incident has been resolved.

The issue has been identified, and a fix has been implemented. The importing lag is being processed.

We are currently investigating this issue.

Dear Customer, We are glad to inform you the availability of the Bloomreach Tools Dashboard has been restored. Please verify the availability of the dashboard and let us know if you are still experiencing any problems. If you have any further questions or need additional assistance, please let us know. Best regards, Bloomreach Support team

Dear Customer, We are glad to inform you the platform availability of the Bloomreach Tools Dashboard has been restored. We will continue to monitor. Best regards, Bloomreach Support team

Dear Customer, We have detected an intermittent issue in the Bloomreach search and merchandising dashboard. Dashboard users are currently facing issues loading the search and merchandising dashboard . We are further investigating the issue. Kind regards, Bloomreach Support team

This incident has been resolved.

Bloomreach dashboard now appears operational but we are continuing to monitor. Our apologies for the inconvenience. Should you have any questions, please feel free to reach out to support@bloomreach.com

We are aware that some clients are currently unable to log into the Bloomreach search and merchandising dashboard due to third party authentication service. We are further investigating the issue. Kind regards, Bloomreach Support team

This incident has been resolved.

The issue has been identified and a fix is being implemented, imports are being rapidly processed.

This incident has been resolved.

Brevo (Send In Blue) has fixed the issues. We are actively monitoring the situation.

EU1 is also impacted by the incident.

Emailing service provider Brevo has a downtime on their service, Bloomreach clients using Brevo emailing integrations are impacted. We are monitoring the situation. Brevo status page: https://status.brevo.com/

This incident has been resolved.

Services are functional - the team is monitoring the incident.

Accounts on CIN are also affected, web personalization is not working (Web Layers, Experiments, Managed Tags).

Accounts on CIS instance are experiencing issue with Web Layers, Experiments, Managed Tags not being displayed. Engineers are aware of the issue and are working on resolving it.

The incident has been resolved, and Web Layers, Experiments, and Managed Tags are functional on the CIN instance.

Engineers have identified the issue, team is working on a fix.

Account on CIN instance are experiencing issue with Web Layers, Experiments, Managed Tags not being displayed.

Dear Customer, We are glad to inform you the availability of the Bloomreach Tools Dashboard has been restored. Please verify the availability of the dashboard and let us know if you are still experiencing any problems. If you have any further questions or need additional assistance, please let us know. Best regards, Bloomreach Support team

Dear Customer, We are glad to inform you the platform availability of the Bloomreach Tools Dashboard has been restored. We will continue to monitor. Best regards, Bloomreach Support team

Dear Customer, We are currently experiencing an intermittent disruption in the availability of the Bloomreach Tools Dashboard(Category Pages only). Our teams identified the issue and are attempting to restore availability as soon as possible. We apologize for the inconvenience caused. We will keep you informed and will update you immediately as soon as we have any more information or an estimated resolution time. Kind regards, Bloomreach Support team.

Dear Customer, We are pleased to inform you that disruption in the availability of the Bloomreach Search reported on 14th July 2023 has now been resolved. Please verify the availability of your end and let us know if you are still experiencing any problems. We apologise for the inconvenience caused. If you have any further questions or need additional assistance, please reach out to support. Best regards, Bloomreach Support team

Dear Customer, A fix has been implemented and we are monitoring the results. Kind regards, Bloomreach Support Team.

Dear Customer, The issue has been identified and our teams are working on implementing the fix. Kind regards, Bloomreach Support Team.

Dear Customer, We are currently experiencing a disruption in the availability of the Bloomreach Search . Our teams are busy investigating the situation and attempting to restore availability as soon as possible. We apologise for the inconvenience caused. We will keep you informed and will update you immediately as soon as we have any more information or an estimated resolution time. Kind regards, Bloomreach Support Team.

The incident was resolved.

The application is partially functional again, but downtime is still possible. Engineers are working on a rollback to previous versions to prevent further downtimes.

The fix is being prepared; the issue's complexity requires more preparation time.

Issue has been identified, team is working on making a fix.

We will provide the following update in 30 mins.

The team is investigating the issue causing the unavailability of certain features on the EU1 instance. Impacted are all features working with calculations of customers' data - reports, personalized web layers, and campaigns.

Dear Customer, We are pleased to inform you that disruption in the availability of the Bloomreach Pathways has now been resolved. Please verify the availability of the pathways API and let us know if you are still experiencing any problems. We apologize for the inconvenience caused. If you have any further questions or need additional assistance, please reach out to support. Best regards, Bloomreach Support Team

Dear Customer, A fix has been implemented and we are monitoring the results. Kind regards, Bloomreach Support team.

Dear Customer, The issue has been identified and we are working on the solution. Kind regards, Bloomreach Support Team.

We are continuing to investigate this issue.

Dear Customer, We are currently experiencing a disruption in the availability of the Bloomreach Pathways. Our teams are busy investigating the situation and attempting to restore availability as soon as possible. We apologize for the inconvenience caused. We will keep you informed and will update you immediately as soon as we have any more information or an estimated resolution time. Kind regards, Bloomreach Support team.

Dear Customer, We are pleased to inform you that disruption in the availability of the Bloomreach Search & Merch first reported on 24th April 2023 has now been resolved. Please verify the availability of your Bloomreach applications and let us know if you are still experiencing any problems. We apologize for the inconvenience caused. If you have any further questions or need additional assistance, please reach out to support. Best regards, Bloomreach Support team

A fix has been implemented and we are monitoring the results. Kind regards, Bloomreach Support Team.

The issue has been identified and we are working on the solution. Kind regards, Bloomreach Support Team.

Dear Customer, We are currently experiencing a disruption in the availability of the Bloomreach Search & Merch platform. Our teams are busy investigating the situation and attempting to restore availability as soon as possible. We apologize for the inconvenience caused. We will keep you informed and will update you immediately as soon as we have any more information or an estimated resolution time. Kind regards, Bloomreach Support team.

Dear Customer, We are pleased to inform you that disruption in the availability of the Bloomreach Pathways first reported on 24th April 2023 has now been resolved. Please verify the availability of your Bloomreach applications and let us know if you are still experiencing any problems. We apologize for the inconvenience caused. If you have any further questions or need additional assistance, please reach out to support. Best regards, Bloomreach Support Team

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

Dear Customer, We are currently experiencing a disruption in the availability of the Bloomreach Pathways. Our teams are busy investigating the situation and attempting to restore availability as soon as possible. We apologize for the inconvenience caused. We will keep you informed and will update you immediately as soon as we have any more information or an estimated resolution time. Kind regards, Bloomreach Support team.

All systems are stable, incident is resolved

A fix has been deployed, we're monitoring the situation

We are continuing to work on a fix for this issue.

Engineers have identified the issue.

On duty engineers are actively investigating the issue.

The lag was entirely processed and all delayed data was exported to EBQ on 28.02.2023 ~1:00am UTC

We fixed the issue and are monitoring the lag decreasing. Our revised ETA is ~8hours (28.02.2023 00:30 UTC)

Bloomreach engineers identified an issue on Engagement platform causing delay in event data export to EBQ. Users of EBQ might have noticed missing data for event imported to the platform after 22.02.2023. Only ENG instance is affected. ETA for all data to be fully exported to EBQ ~24hours (28.02.2023 13:00 UTC)

The incident has been resolved. UTC 12:15 - 13:05 - Complete downtime 13:05 - 13:20 - Service degradation

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

The issue has been fixed. Execution of the campaign is delayed by approximately 30 minutes. No campaigns will be lost. Tracking of customer data is delayed by approximately 30 minutes. No customer data will be lost. The team is actively monitoring the situation.

The engineering team is trying to start the EXP instance at the moment. ETA - unknown; IMPACT: - campaigns delayed - reports not working - personaliztaion not working - customized weblayers that are using personalization are not working either

IMPACT: - campaigns delayed - reports not working - personaliztaion not working - customized weblayers that are using personalization are not working either Tracking of data is NOT IMPACTED. No data is lost.

This incident has been resolved.

Dear Customer, We are glad to inform you the Bloomreach dashboard is now operational. We apologize for the inconvenience caused. If you have any further questions or need additional assistance, please reach out to support. Best regards, Bloomreach Support team

Dear Customer, Bloomreach Dashboard is currently unavailable due to an issue with our authentication service. We are actively working in resolving the issue. We apologize for the inconvenience and will continue to provide you updates. Should you have any questions, please feel free to reach us. Kind regards, Bloomreach Support team.

Dear Customer, The issue has been resolved. Best Regards, Bloomreach Support Team.

Bloomreach is continuing to work with our upstream provider and they are working to resolve. We will continue to provide status updates. Best regards, Bloomreach Support team

Dear Customer, We are currently experiencing a disruption in the availability of the Bloomreach Cloud platform. We apologize for the inconvenience caused. We will keep you informed and will update you immediately as soon as we have any more information or an estimated resolution time. After an initial investigation into the availability interruptions on the Bloomreach Cloud, we concluded that the cause is that one of our upstream providers is experiencing technical problems. We are in close contact with our upstream provider and they are working to resolve the problem. As soon as we have any new updates, or an estimated resolution time, we will be sure to share with you. Kind regards, Bloomreach Support team.

Dear Customer, Today at approximately 06:34 AM UTC, Cloudflare declared a critical P0 incident. Connectivity in Cloudflare’s network has been disrupted in broad regions. This affected multiple Content PaaS customers using the bloomreach.cloud domain. Customers on Content SaaS or using other domains are not affected. At 07:20 UTC Cloudflare implemented a fix, we are actively monitoring your application. Please verify the availability of your Bloomreach applications and let us know if you are still experiencing any problems. If you have any further questions or need additional assistance, please let us know. Best regards, Bloomreach Support team

This incident has been resolved.

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

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

Dear Customer, We are currently experiencing a disruption in the availability of Bloomreach Suggest. We apologize for the inconvenience caused. We will keep you informed and will update you immediately as soon as we have any more information. Kind regards, Bloomreach Support team.

Dear Customer, We are glad to inform you the search has been restored. Please verify the availability of your Bloomreach applications and let us know if you are still experiencing any problems. We apologize for the inconvenience caused. If you have any further questions or need additional assistance, please reach out to support. Best regards, Bloomreach Support team

The issue has been identified and we are in recovery mode at the moment.

We are continuing to investigate this issue.

Dear Customer, We are currently experiencing a disruption in the availability of the Bloomreach Search. We apologize for the inconvenience caused. We will keep you informed and will update you immediately as soon as we have any more information. Kind regards, Bloomreach Support team.

Dear Customer, The feed indexing delay is resolved. We do apologize for the inconvenience caused. Thanks and Best Regards, Bloomreach Support Team

Dear Customer, Although the issue is resolved, we are currently experiencing a delay in the feed processing. Our team is addressing that right now. We will keep you posted on the status. Kind regards, Bloomreach Support team

Dear Customer, The feed processing challenge is resolved by Engineering. Bloomreach does appreciate your patience and partnership while we worked on this. Thanks and Best Regards, Bloomreach Support Team

Dear Customer, Our team has made progress into the root cause of the incident and is working on mitigation. We now see reduced errors with the service involved, but the resolution is still in progress. We will keep you posted on further developments. Kind regards, Bloomreach Support team

Dear Customer, We are currently experiencing a delay in the feed processing. Our teams are busy investigating the situation and mitigating it as soon as possible. The anticipated time for resolution is about 4 hours. We apologize for the inconvenience caused. We will keep you informed on an hourly basis. Kind regards, Bloomreach Support team