Jeeva

System Status

Jeeva

System Status

Jeeva

System Status

All System Operational

History

Resolved

Partial Service Disruption – AWS Regional Outage (US-EAST-1)

October 20, 2025

Start: 12:11 AM PDT

End: 3:26 PM PDT

Duration: ~15 hours and 15 minutes

Incident

Between 12:11 AM and 3:26 PM PDT on October 20, 2025, Jeeva AI experienced intermittent service disruptions affecting specific features such as Notetaker meeting joins and data enrichment workflows. The issue was caused by a major AWS infrastructure outage in the US-EAST-1 region, which impacted multiple global platforms. The underlying problem was identified as a DNS subsystem failure within AWS’s network layer.

Resolution

AWS engineers resolved the DNS subsystem issue and restored normal operations by 3:26 PM PDT. Jeeva AI systems automatically recovered, and all services returned to normal. A temporary banner was displayed in the application to keep users informed during the incident. No customer data was lost or compromised.

Resolved

Service Outage

July 30, 2025

Start: 8:07 AM PDT

End: 8:33 AM PDT

Duration: ~25 minutes

Incident

Users were unable to log in or access the Jeeva platform due to an unexpected error after a production deployment. The engineering team identified the cause and restored service promptly. No customer data was lost or compromised.

Resolution

The system was restored by 8:33 AM PDT. Additional deployment controls are being implemented to prevent future occurrences.

All System Operational

History

Resolved

Partial Service Disruption – AWS Regional Outage (US-EAST-1)

October 20, 2025

Start: 12:11 AM PDT

End: 3:26 PM PDT

Duration: ~15 hours and 15 minutes

Incident

Between 12:11 AM and 3:26 PM PDT on October 20, 2025, Jeeva AI experienced intermittent service disruptions affecting specific features such as Notetaker meeting joins and data enrichment workflows. The issue was caused by a major AWS infrastructure outage in the US-EAST-1 region, which impacted multiple global platforms. The underlying problem was identified as a DNS subsystem failure within AWS’s network layer.

Resolution

AWS engineers resolved the DNS subsystem issue and restored normal operations by 3:26 PM PDT. Jeeva AI systems automatically recovered, and all services returned to normal. A temporary banner was displayed in the application to keep users informed during the incident. No customer data was lost or compromised.

Resolved

Service Outage

July 30, 2025

Start: 8:07 AM PDT

End: 8:33 AM PDT

Duration: ~25 minutes

Incident

Users were unable to log in or access the Jeeva platform due to an unexpected error after a production deployment. The engineering team identified the cause and restored service promptly. No customer data was lost or compromised.

Resolution

The system was restored by 8:33 AM PDT. Additional deployment controls are being implemented to prevent future occurrences.

All System Operational

History

Resolved

Partial Service Disruption – AWS Regional Outage (US-EAST-1)

October 20, 2025

Start: 12:11 AM PDT

End: 3:26 PM PDT

Duration: ~15 hours and 15 minutes

Incident

Between 12:11 AM and 3:26 PM PDT on October 20, 2025, Jeeva AI experienced intermittent service disruptions affecting specific features such as Notetaker meeting joins and data enrichment workflows. The issue was caused by a major AWS infrastructure outage in the US-EAST-1 region, which impacted multiple global platforms. The underlying problem was identified as a DNS subsystem failure within AWS’s network layer.

Resolution

AWS engineers resolved the DNS subsystem issue and restored normal operations by 3:26 PM PDT. Jeeva AI systems automatically recovered, and all services returned to normal. A temporary banner was displayed in the application to keep users informed during the incident. No customer data was lost or compromised.

Resolved

Service Outage

July 30, 2025

Start: 8:07 AM PDT

End: 8:33 AM PDT

Duration: ~25 minutes

Incident

Users were unable to log in or access the Jeeva platform due to an unexpected error after a production deployment. The engineering team identified the cause and restored service promptly. No customer data was lost or compromised.

Resolution

The system was restored by 8:33 AM PDT. Additional deployment controls are being implemented to prevent future occurrences.