Blackthorn incident
Degraded service due to a Salesforce platform disruption
Blackthorn experienced a minor incident on September 16, 2026 affecting Blackthorn Events and Blackthorn Payments and 1 more component, lasting 23h 43m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Sep 16, 2026, 11:02 AM UTC
Salesforce is currently experiencing a platform-wide service disruption affecting core services across all regions (Salesforce incident 20004433, ongoing since 7:50 AM UTC on September 16). Blackthorn Events, Payments, and Messaging run on and connect to the Salesforce platform, so some Blackthorn functionality may be unavailable or degraded while this disruption continues — including loading event registration and payment pages and authenticating to Salesforce orgs. Sessions and pages that were already loaded may continue to work normally. This is an upstream Salesforce platform incident, not a defect or outage in the Blackthorn applications. No changes to your Blackthorn configuration are required, and no action is needed on your side to resolve it. Our hosted services remain operational and will return to normal as Salesforce restores service. Salesforce has identified the cause as an internal login service consuming platform resources and is validating a fix before rolling it out across affected instances. We are monitoring the incident and will post updates here as the situation changes. Impact began: 7:50 AM UTC, September 16, 2026 (ongoing) Affected: Salesforce instances across all regions. Confirm whether your instance is impacted at status.salesforce.com/incidents/20004433.
- resolved Sep 17, 2026, 10:45 AM UTC
Salesforce has declared the platform disruption resolved, reporting that instance stability and performance have returned to expected levels. Blackthorn services that depend on the Salesforce platform — event registration and payment pages, and authentication to Salesforce orgs — are operating normally again. If you see any lingering errors, a browser refresh or fresh login should clear them. Salesforce is conducting a full investigation into the trigger and root cause and will publish preventive actions. Thank you for your patience during the disruption.