E
Outage recap · Encord

Encord outage — August 7, 2026

On August 7, 2026, Encord had 3 reported incidents on Encord's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Degraded data explorer performance

minor
Started
Aug 7, 11:32 AM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked Encord 24 times in the two hours after Encord's start time (it published no end time), once every five minutes. Every one of them reached Encord's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 229 ms, against 216 ms over the 24 hours before. Encord's feed showed the incident by Aug 7, 11:40 AM EDT (we read it every five minutes).

Updates are Encord's own words from its status page (status: resolved); we never add an inferred cause.

Degraded Data Explorer performance

minor
Started
Aug 7, 1:56 PM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked Encord 24 times in the two hours after Encord's start time (it published no end time), once every five minutes. Every one of them reached Encord's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 169 ms, against 213 ms over the 24 hours before. Encord's feed showed the incident by Aug 7, 2:05 PM EDT (we read it every five minutes).

Updates are Encord's own words from its status page (status: resolved); we never add an inferred cause.

Degraded Data Explorer performance

minor
Started
Aug 7, 2:46 PM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked Encord 24 times in the two hours after Encord's start time (it published no end time), once every five minutes. Every one of them reached Encord's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 182 ms, against 210 ms over the 24 hours before. Encord's feed showed the incident by Aug 7, 2:55 PM EDT (we read it every five minutes).

Updates are Encord's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with Encord. This recap summarizes incidents published on Encord's official status page.