Keysight Eggplant Outage History
Keysight Eggplant is up right nowPingoru has recorded 46 incidents for Keysight Eggplant: 0 in the last 12 months and 0 in the last 90 days.
Incidents, newest first
Notice August 16, 2025 Monitoring Insights Portal increased authentication error rate 3m Portal Hub
Started Aug 16, 2025, 12:50 PM UTC· resolved Aug 16, 2025, 12:54 PM UTC
- monitoring Aug 16, 2025, 12:50 PM UTC
We have identified an increased rate of authentication errors on the Monitoring Insights Portal between 13:06-13:40 (BST). The authentication errors might have caused degraded service for a small number of users when browsing the portal during the time window. To mitigate the issue, the central cache storage has been cleared to generate new session tokens. This might have caused already logged in users having to sign-in again. This incident only impacted the Monitoring Insights Portal, testing and alerting have been working as expected.
- resolved Aug 16, 2025, 12:54 PM UTC
This incident has been resolved.
Notice June 14, 2025 Potential issue with viewing test results 28m Portal Hub, Testing, Reporting, API v1 and 1 more
Started Jun 14, 2025, 02:15 PM UTC· resolved Jun 14, 2025, 02:44 PM UTC
- investigating Jun 14, 2025, 02:15 PM UTC
We are investigating a potential issue viewing test results. This seems to only be impacting some accounts.
- resolved Jun 14, 2025, 02:44 PM UTC
Upon investigation, it appears test results and testing are fine.
Notice May 19, 2025 DAI 25.2.0 upgrade –
Started May 19, 2025, 09:30 AM UTC· resolved May 19, 2025, 09:30 AM UTC
- resolved May 19, 2025, 09:30 AM UTC
We will be updating DAI for all US Eggplant Cloud tenancies to version 25.2.0 There may be a brief interruption to the portal and test execution whilst services are restarted.
Notice March 9, 2025 Monitoring Insights test agent failure 1d 1h Testing
Started Mar 09, 2025, 12:23 PM UTC· resolved Mar 10, 2025, 01:48 PM UTC
- monitoring Mar 09, 2025, 12:23 PM UTC
We have detected an out of memory incident on one of our Agent 10 instances at 11:14:20 (UTC) today. Test agent 31200 has now been cordoned and will undergo further investigation.
- resolved Mar 10, 2025, 01:48 PM UTC
This incident has been resolved.