Semperis Outage History
Semperis is up right nowPingoru has recorded 18 incidents for Semperis: 8 in the last 12 months and 3 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 1 of 720 (0%) |
| May 2026 | 2 | 5 of 744 (1%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 1 | 0 of 744 (0%) |
| August 2026 | 1 | 1 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 2 | 6 of 527 (1%) |
Incidents, newest first
Critical October 14, 2026 Login issues in Production (North America) 40m NA
Started Oct 14, 2026, 11:11 AM UTC· resolved Oct 14, 2026, 11:51 AM UTC
- investigating Oct 14, 2026, 11:11 AM UTC
We are currently investigating an issue preventing some users from logging in to the Production environment in North America.
- identified Oct 14, 2026, 11:44 AM UTC
The issue has been identified and a fix is being implemented.
- resolved Oct 14, 2026, 11:51 AM UTC
This incident has been resolved.
Minor October 5, 2026 Degraded performance (North America region) 5h 4m NA
Started Oct 05, 2026, 08:50 AM UTC· resolved Oct 05, 2026, 01:55 PM UTC
- identified Oct 05, 2026, 08:50 AM UTC
Since 06:20 UTC on October 5, some customers in the North America region may see intermittent errors in Lightning. Some pages may fail to load or briefly show an access error, and collection for some data sources may be delayed. We have identified the affected service and are working to restore it.
- resolved Oct 05, 2026, 01:55 PM UTC
This incident has been resolved
Minor August 11, 2026 Some directories are not able to run manual/scheduled indicators 29m NA
Started Aug 11, 2026, 09:17 PM UTC· resolved Aug 11, 2026, 09:47 PM UTC
- investigating Aug 11, 2026, 09:17 PM UTC
We are currently investigating the issue.
- resolved Aug 11, 2026, 09:47 PM UTC
This incident has been resolved
Major July 22, 2026 Issue with login to Lightning NA Dashboard 19m NA
Started Jul 22, 2026, 08:09 AM UTC· resolved Jul 22, 2026, 08:28 AM UTC
- investigating Jul 22, 2026, 08:09 AM UTC
We are currently investigating this issue.
- resolved Jul 22, 2026, 08:28 AM UTC
This incident has been resolved.
Critical May 26, 2026 Lightning EU - Service unavailable 2h 3m EU
Started May 26, 2026, 02:56 PM UTC· resolved May 26, 2026, 05:00 PM UTC
- investigating May 26, 2026, 02:56 PM UTC
We are currently investigating this issue.
- investigating May 26, 2026, 02:56 PM UTC
We are continuing to investigate this issue.
- investigating May 26, 2026, 04:58 PM UTC
Incident resolved
- investigating May 26, 2026, 04:59 PM UTC
We are continuing to investigate this issue.
- resolved May 26, 2026, 05:00 PM UTC
This incident has been resolved.
Major May 26, 2026 AD collector status showing Disconnected although services are working 4h 29m NA, AU
Started May 26, 2026, 02:49 PM UTC· resolved May 26, 2026, 07:19 PM UTC
- investigating May 26, 2026, 02:49 PM UTC
We are currently investigating this issue.
- resolved May 26, 2026, 07:19 PM UTC
This incident has been resolved.
Notice April 14, 2026 General 1h
Started Apr 14, 2026, 06:00 AM UTC· resolved Apr 14, 2026, 07:00 AM UTC
- resolved Apr 16, 2026, 07:27 AM UTC
Lightning - Indicator package update triggered a surge of collector requests, causing resource exhaustion and temporary service degradation (EU & NA), resulting in limited access to directory data and IOE results until scaling mitigated the issue.
- postmortem Apr 19, 2026, 10:10 AM UTC
**Lightning Intelligence service degradation following routine update** **Postmortem Summary** A routine update triggered an unexpected surge in system requests, resulting in temporary service unavailability for approximately one hour across multiple environments. The issue was identified and mitigated by increasing system capacity. Preventative measures are being implemented to ensure improved resilience and monitoring going forward. **Overview** On April 14, 2026, at approximately 06:00 UTC, a routine update triggered a large number of client components to simultaneously request updated data from the platform. This unexpected spike in traffic overwhelmed a shared service, causing temporary unavailability of the Lightning UI across production environments. The incident impacted all customers in the affected environments for approximately one hour. Service was restored by scaling system capacity and stabilizing request handling. **Leadup** The security indicator update introduced a new version of configuration data. Upon release, all connected components detected the update at the same time and attempted to retrieve it simultaneously. This behavior had not been previously observed at production scale, and existing validation processes did not simulate this level of concurrent activity. **Impact** * **Duration:** ~1 hour * **User impact:** All customers in affected environments * **Customer experience:** * Temporary inability to access directory data in the Lightning UI * Intelligence features \(Dashboards, Exposures, etc.\) were unavailable during the incident * Some background components temporarily failed to update and remained on a previous version until normal operations resumed **Detection** The issue was detected via automated alerting shortly after the spike in system load. Initial detection was limited to a subset of environments, and full impact visibility was established shortly afterward. **Improvement opportunity:** Enhancing system-wide monitoring and alerting will allow faster and more complete detection across all environments. **Response** The engineering team responded immediately upon alert and identified the root cause as a traffic spike overwhelming system capacity. Mitigation actions included increasing available capacity to handle the load. Response time was slightly impacted by access control processes required for emergency changes. **Recovery** Service was restored after increasing system capacity, allowing the platform to handle both background update traffic and customer-facing requests. Once the surge subsided and systems stabilized, full functionality was restored. Total recovery time was approximately one hour. **Root Cause** The incident was caused by a simultaneous update request from a large number of client components following a routine release. This created a sudden spike in demand that exceeded the system’s capacity, impacting both background processing and customer-facing services. **Preventative Measures** The following improvements are being implemented: * **Improved system capacity and scalability** for handling burst traffic * **Enhanced monitoring and alerting** across all environments * **Load testing at production scale scenarios** prior to releases * **Improved resilience of client update mechanisms** * **Clear incident communication processes**, including status page ownership **Timeline** _All times in UTC on April 14, 2026_ * **06:00** – Update released; spike in requests begins * **~06:05** – Automated alert triggered * **~06:10** – Investigation begins * **~06:30** – Capacity increased to mitigate load * **~06:45** – Service begins recovering * **~07:00** – Full service restored; incident resolved
Minor March 31, 2026 Issue with our upstream provider 1h 4m NA
Started Mar 31, 2026, 09:20 PM UTC· resolved Mar 31, 2026, 10:24 PM UTC
- identified Mar 31, 2026, 09:20 PM UTC
One of our upstream provider, is currently experiencing an issue which is affecting some of the Ready1 customers in North America Region. We will resolve this incident once we have received confirmation that the issue has been resolved from our upstream provider.
- monitoring Mar 31, 2026, 09:52 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Mar 31, 2026, 09:53 PM UTC
We are continuing to monitor for any further issues.
- resolved Mar 31, 2026, 10:24 PM UTC
This incident has been resolved.