Salesforce's CHE16 and CHE30 instances hit a search indexing delay on 31 October, lasting 48 minutes. The fault sat on Salesforce's side, in how newly created or updated records were indexed for search.
Started
09:43 UTC
Duration
Lasted 48m
Source
IsDown
Next time
Salesforce is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: CHE16, CHE30
What happened?
Salesforce logged one incident on this date, starting at 09:43 UTC and running for 48 minutes before resolution. It affected two instances, CHE16 and CHE30, and was labelled "Performance Degradation" by Salesforce. The only update came seven minutes in, at 09:50 UTC, when Salesforce said it had identified a delay in search indexing on those two instances. The text was specific: recently created or updated records would not yet appear in search results, but search itself continued to work. Salesforce said it had identified the technical trigger and started a corrective deployment, with a promise of another update once that deployment finished or sooner if anything changed. No further update was logged after that, and the incident shows as resolved at 48 minutes, so the deployment appears to have closed it out. No user reports were filed during this window, so there is no independent account of what this looked like from outside Salesforce. Over the past 90 days, Salesforce has logged 121 incidents with a median duration of 2 hours 13 minutes, which makes this 48-minute incident shorter than typical. Across all time, Salesforce has recorded 2,497 incidents. No post-mortem has been published beyond the single update, so the deeper cause of the indexing delay is not on the record.
Learning
This incident shows a failure in a layer that sits behind your own uptime checks: search indexing. Your product can be reachable, your API calls can succeed, and your own monitoring can stay green, while records you just created or updated simply don't show up in search yet. That's a backend processing lag, not a connectivity problem, and it will not trip an external check that just pings an endpoint and gets a response. The only way to see it is to watch the provider's own status feed, the same one Salesforce used to narrate this, from "identified" through "deployment" to resolution. If you depend on search freshness inside Salesforce for things like support queues or record lookups, a gap like this can quietly break a workflow while every health check you run says fine. Your monitoring covers your half of the stack, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
