- Detected by Pingoru
- Feb 19, 2026, 01:01 PM UTC
- Resolved
- Feb 19, 2026, 01:56 PM UTC
- Duration
- 55m
Affected: US1US2US3
Timeline · 3 updates
-
investigating Feb 19, 2026, 01:01 PM UTC
Status: We are investigating a partial degradation within a shared technical component. Impact: Current impact is being assessed. The service remains functional but may experience intermittent issues or increased latency. Action: Engineering teams are actively troubleshooting to determine the root cause and full scope. We will provide an update as soon as more information is available.
-
monitoring Feb 19, 2026, 01:25 PM UTC
Status: The situation is now under control and performance has returned to normal. Impact: There were several minutes of performance degradation, specifically affecting catalogs, during the incident. Resolution: The root cause was identified, and a fix has been applied. Monitoring: Engineering teams are continuing to monitor the environment to ensure stability.
-
resolved Feb 19, 2026, 01:56 PM UTC
Elasticsearch components have been upscaled and the situation is now stable and resolved
Read the full incident report →
- Detected by Pingoru
- Feb 17, 2026, 01:49 PM UTC
- Resolved
- Feb 17, 2026, 02:19 PM UTC
- Duration
- 30m
Timeline · 3 updates
-
investigating Feb 17, 2026, 02:43 PM UTC
Issue is being currently investigated. Affected instances are PWR, ECC, TMB, RNK, SPE
-
identified Feb 17, 2026, 02:50 PM UTC
We identified the underscale of the backend components. More resources have been provided to process the existing lag on the processed messages.
-
resolved Feb 17, 2026, 02:52 PM UTC
Incident has been resolved.
Read the full incident report →
Critical January 27, 2026 - Detected by Pingoru
- Jan 27, 2026, 10:44 PM UTC
- Resolved
- Jan 27, 2026, 11:09 PM UTC
- Duration
- 24m
Affected: EU1
Timeline · 4 updates
-
investigating Jan 27, 2026, 10:44 PM UTC
We are currently investigating this issue.
-
investigating Jan 27, 2026, 10:45 PM UTC
Investigation in progress
-
identified Jan 27, 2026, 10:58 PM UTC
The service has been restored and is operating normally. We are continuing to monitor the situation and investigate the issue, checking all components
-
resolved Jan 27, 2026, 11:09 PM UTC
The instance is back up and fully operational.
Read the full incident report →
Critical January 21, 2026 - Detected by Pingoru
- Jan 21, 2026, 08:26 AM UTC
- Resolved
- Jan 21, 2026, 08:54 AM UTC
- Duration
- 28m
Affected: Discovery USDiscovery EMEADiscovery APAC
Timeline · 4 updates
-
investigating Jan 21, 2026, 08:26 AM UTC
Dear Customers, We're currently observing catalog feed Ingestion failures. Our engineering team is actively investigating the root cause and closely monitoring performance. We'll provide updates here as soon as more information becomes available. For any immediate assistance, please reach out to [email protected]/[email protected]. Thank you for your continued patience and cooperation. Kind regards, Bloomreach Support Team.
-
identified Jan 21, 2026, 08:44 AM UTC
Dear Customers, The issue has been identified, and our teams are working on implementing the fix. Regards, Bloomreach Support Team.
-
monitoring Jan 21, 2026, 08:51 AM UTC
Dear Customer, A fix has been implemented, and data ingestion has been resumed. Please verify, and we are continuing to monitor. Regards, Bloomreach Support Team.
-
resolved Jan 21, 2026, 08:54 AM UTC
Dear Customers, We are pleased to inform you that feed ingestion is now operational. For any further questions, please reach out to [email protected]. Thank you for your continued patience and cooperation. Regards, Bloomreach Support Team.
Read the full incident report →
- Detected by Pingoru
- Jan 19, 2026, 03:57 PM UTC
- Resolved
- Jan 19, 2026, 04:22 PM UTC
- Duration
- 24m
Affected: US1
Timeline · 2 updates
-
monitoring Jan 19, 2026, 03:57 PM UTC
Dear customer, Access to the US1 instance was temporarily impacted. The instance and service have been successfully restored, and normal operation has resumed. We continue to monitor the system to ensure stability.
-
resolved Jan 19, 2026, 04:22 PM UTC
Dear customer, The temporary access issue on the US1 instance has been fully resolved. The instance and service are operating normally, and all systems are stable. We thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Dec 10, 2025, 06:27 AM UTC
- Resolved
- Dec 10, 2025, 06:27 AM UTC
- Duration
- —
Affected: Discovery USDiscovery EMEADiscovery APAC
Timeline · 1 update
-
resolved Dec 10, 2025, 06:27 AM UTC
Dear Customers, Earlier today, we observed intermittent delays in background data replication, leading to increased feed indexing time, which was caused by a temporary issue with the third-party cloud service provider (AWS). Our teams proactively detected and mitigated the issue, and systems are operating normally. We have built-in resiliency and automatic retry mechanisms in place, which have limited customer impact. We identified the behavior early through monitoring and have been actively coordinating with AWS while continuing to closely observe system health. There was no impact on customer-facing APIs or live traffic. If you experience any issues or have questions, please contact us at [email protected]. Regards, Bloomreach Support Team
Read the full incident report →
Critical December 5, 2025 - Detected by Pingoru
- Dec 05, 2025, 09:21 AM UTC
- Resolved
- Dec 05, 2025, 10:27 AM UTC
- Duration
- 1h 6m
Affected: US EastUS NortheastUS WestUS NorthwestBloomreach Content SaaSCA CentralEU West-1EU West-2EU CentralAsia Pacific Southeast (SG)
Timeline · 3 updates
-
investigating Dec 05, 2025, 09:21 AM UTC
Cloudflare is experiencing a major global outage. This is affecting applications and customers across the internet, including Bloomreach. We will provide updates as soon as more information becomes available.
-
monitoring Dec 05, 2025, 09:43 AM UTC
Cloudflare is operational again and we observe systems being accessible. We will continue to monitor the situation to make sure it is completely resolved. Please reach out to Bloomreach Support if you are facing any issues.
-
resolved Dec 05, 2025, 10:27 AM UTC
[RESOLVED] Cloudflare has confirmed that the issue is resolved. Please reach out to Bloomreach Support in case you have questions.
Read the full incident report →
- Detected by Pingoru
- Dec 04, 2025, 10:19 AM UTC
- Resolved
- Dec 04, 2025, 01:48 PM UTC
- Duration
- 3h 28m
Affected: ENG
Timeline · 4 updates
-
investigating Dec 04, 2025, 10:19 AM UTC
We are investigating a consent event sync processing lag for Shopify Integrations.
-
identified Dec 04, 2025, 12:56 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Dec 04, 2025, 01:45 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 04, 2025, 01:48 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 28, 2025, 04:24 PM UTC
- Resolved
- Nov 28, 2025, 08:28 PM UTC
- Duration
- 4h 3m
Affected: US3
Timeline · 7 updates
-
investigating Nov 28, 2025, 04:24 PM UTC
Investigating Performance Degradation on manage Endpoint We are currently investigating a performance degradation affecting the manage endpoint. Impact: Under assessment — not yet confirmed. Our Engineering team is actively working to identify the root cause and restore normal performance. We will provide updates as soon as more information becomes available.
-
monitoring Nov 28, 2025, 04:30 PM UTC
The team has implemented a fix for the performance degradation on the manage endpoint and is currently monitoring the situation to confirm stability. We will provide further updates as needed.
-
monitoring Nov 28, 2025, 05:43 PM UTC
We are continuing to monitor for any further issues.
-
monitoring Nov 28, 2025, 06:00 PM UTC
During ongoing monitoring, a few additional minor issues were detected and promptly addressed. Further fixes were implemented at 18:35 CET. We continue to monitor the situation closely.
-
investigating Nov 28, 2025, 06:08 PM UTC
The issue has reoccurred, and the managed endpoints remain unstable. Our Engineering team is actively investigating to identify the root cause.
-
monitoring Nov 28, 2025, 06:42 PM UTC
The situation has stabilized, and the managed endpoints are operating normally again as of 19:25 CET. Monitoring will continue to ensure ongoing stability.
-
resolved Nov 28, 2025, 08:28 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 07, 2025, 09:44 AM UTC
- Resolved
- Nov 07, 2025, 05:43 PM UTC
- Duration
- 7h 58m
Affected: Discovery USDiscovery EMEADiscovery APAC
Timeline · 4 updates
-
investigating Nov 07, 2025, 09:44 AM UTC
Dear Customer, We're currently observing intermittent catalog feed processing failures affecting a limited subset of customers. In most cases, other catalogs for the same accounts are processing normally, and no broad impact is expected. Our engineering team is actively investigating the root cause and closely monitoring performance. We'll provide updates here as soon as more information becomes available. For any immediate assistance, please reach out to [email protected] Thank you for your continued patience and cooperation. Kind regards, Bloomreach Support Team.
-
monitoring Nov 07, 2025, 09:57 AM UTC
Dear Customer, A fix has been implemented for the intermittent catalog feed processing failures, and we are actively monitoring. Kind regards, Bloomreach Support Team.
-
monitoring Nov 07, 2025, 10:05 AM UTC
Dear Customer, We are pleased to inform you that the feed processing capabilities have been fully resolved. Regards, Bloomreach Support Team.
-
resolved Nov 07, 2025, 05:43 PM UTC
This incident has been resolved.
Read the full incident report →
Critical October 20, 2025 - Detected by Pingoru
- Oct 20, 2025, 06:41 PM UTC
- Resolved
- Oct 20, 2025, 08:56 PM UTC
- Duration
- 2h 15m
Affected: Discovery US
Timeline · 3 updates
-
investigating Oct 20, 2025, 06:41 PM UTC
We are experiencing latency with Recs and Pathways API. This is related to the ongoing AWS outage. We apologize for the inconvenience caused and will update as soon as we have any more information.
-
monitoring Oct 20, 2025, 08:32 PM UTC
The Recs and Pathways API latency is stable. We are currently monitoring and will update as soon as we have additional information.
-
resolved Oct 20, 2025, 08:56 PM UTC
We are pleased to inform you the Recs and Pathways latency has been resolved.
Read the full incident report →
Critical October 20, 2025 - Detected by Pingoru
- Oct 20, 2025, 06:32 PM UTC
- Resolved
- Oct 21, 2025, 07:34 AM UTC
- Duration
- 13h 2m
Affected: Discovery USDiscovery EMEADiscovery APAC
Timeline · 4 updates
-
investigating Oct 20, 2025, 06:32 PM UTC
We are experiencing interruptions with Dashboard components. This is related to the ongoing AWS outage. We apologize for the inconvenience caused and will update as soon as we have any more information.
-
investigating Oct 20, 2025, 09:01 PM UTC
We are continuing to investigate the Dashboard interruptions and will update as soon as we have more information.
-
monitoring Oct 20, 2025, 09:50 PM UTC
Dashboard components are stable and we are continuing to monitor.
-
resolved Oct 21, 2025, 07:34 AM UTC
We are pleased to inform you, after monitoring the incident, we can confirm Dashboard components are stable and operational.
Read the full incident report →
Critical October 20, 2025 - Detected by Pingoru
- Oct 20, 2025, 04:07 PM UTC
- Resolved
- Oct 20, 2025, 08:35 PM UTC
- Duration
- 4h 27m
Affected: Discovery USDiscovery EMEADiscovery APAC
Timeline · 4 updates
-
investigating Oct 20, 2025, 04:07 PM UTC
Dear Customer, We are currently experiencing a delay with feed processing potentially related to ongoing AWS outages. Our teams are investigating the situation will mitigate as soon as possible. All other parts of the platform were not affected. 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.
-
identified Oct 20, 2025, 05:29 PM UTC
Dear Customer, We can confirm the delay with feed processing is related to the ongoing AWS outages. We do apologize for the inconvenience caused. We will continue to provide updates as we have more information to share. Kind regards, Bloomreach Support team.
-
monitoring Oct 20, 2025, 07:19 PM UTC
The feed processing is progressing. We are continuing to monitor. We will update as soon as we have any more information.
-
resolved Oct 20, 2025, 08:35 PM UTC
We are pleased to inform you the feed processing availability has been restored.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 10:14 AM UTC
- Resolved
- Oct 20, 2025, 12:47 PM UTC
- Duration
- 2h 32m
Affected: Discovery USDiscovery EMEADiscovery APAC
Timeline · 2 updates
-
monitoring Oct 20, 2025, 10:14 AM UTC
Dear Customer, We previously experienced intermittent connectivity issues with our Cloud Service Provider, which affected access to the Bloomreach Discovery. Due to this, we were unable to provide timely updates via our status page. We are pleased to inform you that Bloomreach Discovery services are now accessible. Our teams continue to actively monitor the situation to ensure ongoing stability and performance. If you have any questions or require further assistance, please contact our support team. We appreciate your patience and understanding as we worked through this issue. Kind regards, Bloomreach Support Team
-
resolved Oct 20, 2025, 12:47 PM UTC
Dear Customer, We are glad to inform you that, after monitoring the incident, we can confirm Bloomreach services are operational. Please verify the availability of your Bloomreach applications and let us know if you continue to experience any issues. 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
Read the full incident report →
- Detected by Pingoru
- Oct 07, 2025, 04:45 PM UTC
- Resolved
- Oct 07, 2025, 06:25 PM UTC
- Duration
- 1h 40m
Affected: Discovery USDiscovery EMEADiscovery APAC
Timeline · 4 updates
-
investigating Oct 07, 2025, 04:45 PM UTC
We are experiencing issues with feed processing for Bloomreach Discovery. Bloomreach Engineering team is actively investigating this situation to resolve it as soon as possible. We apologize for the inconvenience and will update you as soon as we have more information or an estimated resolution time.
-
identified Oct 07, 2025, 04:56 PM UTC
The Issue has been identified. We do apologize for the inconvenience and will update you as soon as we have more information.
-
monitoring Oct 07, 2025, 05:38 PM UTC
A fix has been implemented for the feed processing delays and we are monitoring.
-
resolved Oct 07, 2025, 06:25 PM UTC
We are pleased to inform that the Feed Processing delays have been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 01, 2025, 10:47 AM UTC
- Resolved
- Oct 01, 2025, 03:53 PM UTC
- Duration
- 5h 5m
Affected: Discovery USDiscovery EMEADiscovery APAC
Timeline · 5 updates
-
investigating Oct 01, 2025, 10:47 AM UTC
We are experiencing partial disruption in the Bloomreach Discovery Dashboard Catalogs UI, as well as issues with feed processing for Bloomreach Discovery. Bloomreach Engineering team is actively investigating this situation to resolve it as soon as possible. We apologize for the inconvenience and will update you as soon as we have more information or an estimated resolution time.
-
identified Oct 01, 2025, 11:38 AM UTC
Issue has been identified and Bloomreach Engineering is working on implementing the fix. We apologize for the inconvenience and will update you as soon as we have more information.
-
identified Oct 01, 2025, 01:38 PM UTC
A fix has been implemented to address the underlying issue, and data processing and indexing are now functioning as expected. We are continuing to work on issues related to the Catalog Management UI. Please note that this does not impact ongoing data processing.
-
monitoring Oct 01, 2025, 02:48 PM UTC
A fix has been implemented for the Dashboard Catalogs UI issue and we are monitoring the results to confirm the system stability.
-
resolved Oct 01, 2025, 03:53 PM UTC
We are pleased to inform that the underlying issues with Dashboard Catalogs UI and Feed Processing have been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2025, 02:14 PM UTC
- Resolved
- Aug 25, 2025, 12:15 PM UTC
- Duration
- 5d 22h
Affected: US EastUS NortheastUS WestUS NorthwestCA CentralEU West-1EU West-2EU CentralAsia Pacific Southeast (SG)
Timeline · 3 updates
-
identified Aug 19, 2025, 02:14 PM UTC
We are currently investigating an issue within our CMS that appears to be affecting redeployments and updates to custom domains. Preliminary analysis suggests a potential underlying bug. Our engineering teams are actively working to identify the root cause and implement a resolution. While we do not yet have an estimated time for recovery, please rest assured that this matter is being treated with the highest priority. As a precaution, we recommend temporarily postponing any deployments or modifications to custom domains until further notice. We will provide updates as soon as additional information becomes available. If you would require assistance for adding domains or deployment, we would encourage you to reach out to support and raise a ticket. Thank you for your patience and understanding.
-
monitoring Aug 21, 2025, 08:47 AM UTC
A fix for the issue identified on 19th Aug has been deployed by our engineering team. We are currently monitoring the results to ensure full resolution. We will provide updates as soon as additional information becomes available. If you would require assistance we would encourage you to reach out to Bloomreach Support and raise a ticket . Thank you for your patience and understanding.
-
resolved Aug 25, 2025, 12:15 PM UTC
We are pleased to inform you the CMS issue has been resolved. If you would require assistance, we would encourage you to reach out to support and raise a ticket. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Aug 15, 2025, 11:23 AM UTC
- Resolved
- Aug 19, 2025, 06:54 AM UTC
- Duration
- 3d 19h
Affected: EXP
Timeline · 3 updates
-
investigating Aug 15, 2025, 11:23 AM UTC
We are currently investigating this issue.
-
monitoring Aug 18, 2025, 10:22 AM UTC
We are actively monitoring; the situation has been identified and improvements implemented.
-
resolved Aug 19, 2025, 06:54 AM UTC
The situation has been resolved, and the infrastructure is stable and functioning as expected.
Read the full incident report →
- Detected by Pingoru
- Aug 14, 2025, 11:45 AM UTC
- Resolved
- Aug 14, 2025, 09:32 PM UTC
- Duration
- 9h 47m
Affected: C7SCA1CINCISENGEU1EU2EXPUK1US1US2US3
Timeline · 3 updates
-
investigating Aug 14, 2025, 11:45 AM UTC
We are currently investigating this issue.
-
identified Aug 14, 2025, 01:27 PM UTC
The issue has been identified, and a fix is being applied.
-
resolved Aug 14, 2025, 09:32 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 14, 2025, 10:47 AM UTC
- Resolved
- Aug 14, 2025, 01:32 PM UTC
- Duration
- 2h 45m
Affected: EXP
Timeline · 3 updates
-
identified Aug 14, 2025, 10:47 AM UTC
The issue has been identified and a fix is being implemented. Potentially impacted features: platform access, campaign execution, import execution, personalization, data API, transactional API
-
identified Aug 14, 2025, 12:59 PM UTC
All features apart from campaign execution were restored. Fix is being implemented.
-
resolved Aug 14, 2025, 01:32 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 07:07 PM UTC
- Resolved
- Jun 13, 2025, 07:31 AM UTC
- Duration
- 12h 24m
Affected: C7SCA1CINCISENGEU1EU2EXPUK1US1US2US3
Timeline · 7 updates
-
investigating Jun 12, 2025, 07:07 PM UTC
We are currently investigating this issue.
-
investigating Jun 12, 2025, 07:28 PM UTC
We are continuing to investigate this issue.
-
investigating Jun 12, 2025, 07:52 PM UTC
Bloomreach is currently impacted by the Google Cloud outage
-
identified Jun 12, 2025, 10:35 PM UTC
Bloomreach is currently impacted by the Google Cloud outage
-
monitoring Jun 12, 2025, 10:52 PM UTC
Bloomreach is currently impacted by the Google Cloud outage
-
monitoring Jun 13, 2025, 07:13 AM UTC
We are continuing to monitor for any further issues.
-
resolved Jun 13, 2025, 07:31 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2025, 09:36 AM UTC
- Resolved
- Jun 04, 2025, 04:38 PM UTC
- Duration
- 7h 2m
Affected: US3
Timeline · 4 updates
-
investigating Jun 04, 2025, 09:36 AM UTC
We are currently investigating this issue. The impact is lag processing tracking from integrations on US3.
-
identified Jun 04, 2025, 12:50 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 04, 2025, 04:29 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 04, 2025, 04:38 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 22, 2024, 02:45 AM UTC
- Resolved
- Nov 22, 2024, 08:14 AM UTC
- Duration
- 5h 28m
Affected: US1
Timeline · 5 updates
-
investigating Nov 22, 2024, 02:45 AM UTC
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
-
investigating Nov 22, 2024, 03:56 AM UTC
We are continuing to investigate this issue.
-
investigating Nov 22, 2024, 05:31 AM UTC
The impact of the incident is intermittent. We are continuing to investigate the root cause of the issue
-
monitoring Nov 22, 2024, 06:03 AM UTC
We have deployed several measures and we no longer observe the impact. We are continuing to monitor the situation
-
resolved Nov 22, 2024, 08:14 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 08, 2024, 12:39 PM UTC
- Resolved
- Nov 08, 2024, 03:56 PM UTC
- Duration
- 3h 16m
Affected: US1
Timeline · 4 updates
-
investigating Nov 08, 2024, 12:39 PM UTC
We are currently investigating this issue.
-
identified Nov 08, 2024, 12:49 PM UTC
The issue has been identified and, the instance is processing the accumulated lag.
-
monitoring Nov 08, 2024, 12:53 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Nov 08, 2024, 03:56 PM UTC
The issue has been resolved.
Read the full incident report →
Critical September 19, 2024 - Detected by Pingoru
- Sep 19, 2024, 04:58 PM UTC
- Resolved
- Sep 19, 2024, 05:09 PM UTC
- Duration
- 10m
Affected: Discovery USDiscovery EMEA
Timeline · 3 updates
-
investigating Sep 19, 2024, 04:58 PM UTC
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 [email protected]
-
monitoring Sep 19, 2024, 05:04 PM UTC
Bloomreach dashboard is now operational and we are continuing to monitor. Our apologies for the inconvenience.
-
resolved Sep 19, 2024, 05:09 PM UTC
We are pleased to inform you the Bloomreach dashboard is now accessible to all clients.
Read the full incident report →
