Salesforce: Performance Degradation: Core Service
Affected components: Core Service179 instances
Timeline of updates
- update
We're aware of an issue that began impacting the PBSGeo service, beginning at 17:19 UTC. During this time, some customers may have experienced degraded functionality, with address geocoding requests failing intermittently. This means some address lookups may not have been able to be converted to geographic coordinates.
At 20:38 UTC, we implemented rate limits to block excessive API traffic. Service functionality has returned to normal levels. We apologize for how this incident affected you and your business.
We will undertake a full investigation to establish the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-18 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
c9b7002e6c070f91…
Impact, status and times are the vendor’s own, as last archived. View on status.salesforce.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Salesforce, started 2026-01-21 17:19 UTC, resolved after 3.3 h, 1 update(s).
- Title
- Performance Degradation: Core Service
- Vendor
- Salesforce
- Date
- URL
- https://rewindex.com/company/salesforce/incidents/20003602
Salesforce profileRecent Salesforce incidentsAll outages on January 21, 2026Salesforce in January 2026MarkdownJSON