SharpSpring incident

API Generating 502 Error

Critical Resolved View vendor source →

SharpSpring experienced a critical incident on January 18, 2024 affecting APIs and Integrations, lasting 21m. The incident has been resolved; the full update timeline is below.

Started
Jan 18, 2024, 01:49 PM UTC
Resolved
Jan 18, 2024, 02:11 PM UTC
Duration
21m
Detected by Pingoru
Jan 18, 2024, 01:49 PM UTC

Affected components

APIs and Integrations

Update timeline

  1. investigating Jan 18, 2024, 01:49 PM UTC

    Our team has received reports that some customers are receiving 502 server errors when running API calls. Our team is investigating these reports and working to resolve these server errors as quickly as possible.

  2. resolved Jan 18, 2024, 02:11 PM UTC

    Our team has resolved the 502 errors that customers were experiencing earlier. Any new API calls should no longer return 502 server errors. If you continue to experience errors when making API calls, please contact our support team for further assistance.