Bloomreach Outage History

18 incidents recorded over the last 365 days, 18 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Bloomreach status99.58% uptime history

Every Recorded Bloomreach Incident

Bloomreach incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 30, 2026Bloomreach Engagement - Application access disruption, login is unavailableThis incident has been resolved. The issue affected the application's accessibility. Other components were not affected and stayed fully operation throught the login outage.38 minResolved
Oct 20, 2026Bloomreach Engagement - UK region unavailableBloomreach Engagement in the UK region has been restored following the earlier cloud provider disruption. Platform access, tracking, and data imports are operating normally again, and primary event processing has…12h 46mResolved
Aug 6, 2026Intermittent Feed Indexing DelaysDear Customer, We are pleased to inform you the feed indexing availability has been fully restored. Regards, Bloomreach Support13 minResolved
Jul 31, 2026Search Dashboard Login IssueDear Customers, We are pleased to inform you the Bloomreach search dashboard is now accessible to all clients. Regards, Bloomreach Support Team33 minResolved
Jul 28, 2026Intermittent Dashboard Login IssueDear Customers, We are pleased to inform you the Bloomreach dashboard is now accessible to all clients. Regards, Bloomreach Support Team1h 27mResolved
Jul 24, 2026Intermittent Search API disruptionDear Customers, This issue is now resolved, and services are back to normal and fully operational. If you face any additional issues or have questions, please reach out to support@bloomreach.com. We apologize for the…1h 40mResolved
Jul 24, 2026Intermittent Dashboard login IssueDear Customers, This issue is now resolved, and services are back to normal and fully operational. If you face any additional issues or have questions, please reach out to support@bloomreach.com. We apologize for the…2h 13mResolved
Jun 24, 2026Shopify Events IssueThis incident has been resolved.21 minResolved
Feb 19, 2026US region - Investigating Partial Performance DegradationElasticsearch components have been upscaled and the situation is now stable and resolved55 minResolved
Feb 17, 2026GEUExponea private service downgradeIncident has been resolved.30 minResolved
Jan 27, 2026EU1 is temporarily downThe instance is back up and fully operational.24 minResolved
Jan 21, 2026Discovery Feed Ingestion InterruptionDear Customers, We are pleased to inform you that feed ingestion is now operational. For any further questions, please reach out to support@bloomreach.com. Thank you for your continued patience and…28 minResolved
Jan 19, 2026Temporary Access Issue on US1Dear 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.24 minResolved
Dec 10, 2025Intermittent feed indexing delaysDear 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…0 minResolved
Dec 5, 2025Cloudflare Outage[RESOLVED] Cloudflare has confirmed that the issue is resolved. Please reach out to Bloomreach Support in case you have questions.1h 6mResolved
Dec 4, 2025Consent event sync processing lag for Shopify integrationsThis incident has been resolved.3h 28mResolved
Nov 28, 2025Investigating Performance Degradation on manage EndpointThis incident has been resolved.4h 3mResolved
Nov 7, 2025Intermittent Feed processing InterruptionThis incident has been resolved.7h 58mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Bloomreach incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Bloomreach Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Bloomreach acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Bloomreach outage in this window ran 12h 46m, against a mean recovery of 2h 10m. If you depend on Bloomreach in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.