Notice history

Jan 2026

Feb 2026

Mar 2026

Jan 2026

Feb 2026

Mar 2026

Jan 2026

Feb 2026

Mar 2026

Resolved
March 04, 2026 at 4:55 PM
Resolved
March 04, 2026 at 4:55 PM
This incident has been resolved.
Investigating
March 03, 2026 at 10:28 PM
Investigating
March 03, 2026 at 10:28 PM

Resolved
February 26, 2026 at 11:55 AM
Resolved
February 26, 2026 at 11:55 AM
This incident has been resolved.
Identified
February 26, 2026 at 11:45 AM
Identified
February 26, 2026 at 11:45 AM
We are continuing to work on a fix for this incident. Services are recovering.
Investigating
February 26, 2026 at 11:24 AM
Investigating
February 26, 2026 at 11:24 AM
We are currently investigating this incident.

Resolved
February 25, 2026 at 11:30 AM
Resolved
February 25, 2026 at 11:30 AM
This incident has been resolved.
Investigating
February 25, 2026 at 3:03 AM
Investigating
February 25, 2026 at 3:03 AM
We are currently investigating this incident.

Resolved
January 27, 2026 at 8:28 AM
Resolved
January 27, 2026 at 8:28 AM
This incident has been resolved.
Investigating
January 27, 2026 at 8:04 AM
Investigating
January 27, 2026 at 8:04 AM
We are currently investigating this incident.

Resolved
January 27, 2026 at 3:41 AM
Resolved
January 27, 2026 at 3:41 AM
This incident has been resolved.
Update
January 27, 2026 at 2:24 AM
Update
January 27, 2026 at 2:24 AM
Issue has been resolved for majority of customers. If you encounter errors, contact us and use the temporary backup API endpoint.

api-backup.exa.sh/search
Monitoring
January 27, 2026 at 1:48 AM
Monitoring
January 27, 2026 at 1:48 AM
We are rolling out a fix and are currently monitoring the result.
Identified
January 27, 2026 at 1:28 AM
Identified
January 27, 2026 at 1:28 AM
DNS configuration issue identified as root cause.
Investigating
January 27, 2026 at 1:21 AM
Investigating
January 27, 2026 at 1:21 AM
Elevated error rates

Resolved
January 23, 2026 at 11:38 PM
Resolved
January 23, 2026 at 11:38 PM
This incident has been resolved.
Investigating
January 23, 2026 at 11:26 PM
Investigating
January 23, 2026 at 11:26 PM
We are currently investigating this incident.

Resolved
January 15, 2026 at 3:50 PM
Resolved
January 15, 2026 at 3:50 PM
This incident has been resolved.
Identified
January 15, 2026 at 3:30 PM
Identified
January 15, 2026 at 3:30 PM
We are continuing to work on a fix for this incident. A temporary mitigation has been applied.
Investigating
January 15, 2026 at 2:30 PM
Investigating
January 15, 2026 at 2:30 PM
We are currently investigating this incident.

Jan 2026 to Mar 2026

Exa - Notice history