Sapia.ai Outage History
Sapia.ai is up right nowPingoru has recorded 9 incidents for Sapia.ai: 2 in the last 12 months and 2 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 2 | 12 of 527 (2%) |
Incidents, newest first
Notice October 20, 2026 Customers unable to login to TalentHub – TalentHub Portal
Started Oct 20, 2026, 01:59 PM UTC· resolved Oct 20, 2026, 01:59 PM UTC
- resolved Oct 20, 2026, 01:59 PM UTC
Customers in the US-East-1 region were unable to login to TalentHub. Authorised Users received an "Sign in failed, please contact support." error message on sign in.
Notice October 20, 2025 Services unavailable in US-East-1 2h 11m Chat Classic, Chat Pro, Chat Pro, Chat Pro and 2 more
Started Oct 20, 2025, 07:11 AM UTC· resolved Oct 20, 2025, 09:22 AM UTC
- resolved Oct 20, 2025, 10:37 AM UTC
At 12:11 AM PDT (07:11 AM UTC), a widespread outage occurred with our major cloud infrastructure partner (Amazon Web Services), in their US-East-1 region. This briefly impacted our platform's availability and some specific features. Our team immediately began monitoring the situation, and services were restored at 2:22 AM PDT (09:22 AM UTC). The impact varied depending on your location and the services you were using: For customers in our US-hosted region: You and your candidates would have been unable to access our platform during the time of the outage. For all other customers: The main platform remained online and accessible. However, our Chat Pro generative AI services (SAIGE scoring) were temporarily unavailable. For any candidates who completed a Chat Pro interview during this window, the scoring and Talent Insights report will have been delayed. We have now generated these for all impacted candidates. The outage also affected our ability to update our Status Page in real-time. This has now been retrospectively updated to accurately reflect the incident.