User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 1173 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 776 ms | 0 |
| Mon 23 | 0 | 0.0 | 887 ms | 0 |
| Tue 01 | 0 | 0.0 | 965 ms | 0 |
| Tue 03 | 0 | 0.0 | 1554 ms | 0 |
| Tue 06 | 0 | 0.0 | 1277 ms | 0 |
| Tue 08 | 0 | 0.0 | 975 ms | 0 |
| Tue 10 | 0 | 0.0 | 296 ms | 0 |
| Tue 12 | 0 | 0.0 | 356 ms | 0 |
| Tue 14 | 0 | 0.0 | 958 ms | 0 |
| Tue 16 | 0 | 0.0 | 826 ms | 0 |
| Tue 19 | 0 | 0.0 | 576 ms | 0 |
| Tue 21 | 0 | 0.0 | 1313 ms | 0 |
| Tue 23 | 0 | 0.0 | 893 ms | 0 |
| Wed 01 | 0 | 0.0 | 1026 ms | 0 |
| Wed 04 | 0 | 0.0 | 2668 ms | 0 |
| Wed 06 | 0 | 0.0 | 1450 ms | 0 |
| Wed 08 | 0 | 0.0 | 1405 ms | 0 |
| Wed 10 | 0 | 0.0 | 1139 ms | 0 |
| Wed 13 | 0 | 0.0 | 731 ms | 0 |
| Wed 14 | 0 | 0.0 | 910 ms | 0 |
| Wed 16 | 0 | 0.0 | 1546 ms | 0 |
| Wed 18 | 0 | 0.0 | 274 ms | 0 |
| Wed 20 | 0 | 0.0 | 671 ms | 0 |
| Wed 22 | 0 | 0.0 | 1825 ms | 0 |
| Thu 00 | 0 | 0.0 | 1750 ms | 0 |
| Thu 02 | 0 | 0.0 | 960 ms | 0 |
| Thu 05 | 0 | 0.0 | 1685 ms | 0 |
| Thu 07 | 0 | 0.0 | 1449 ms | 0 |
| Thu 09 | 0 | 0.0 | 888 ms | 0 |
| Thu 11 | 0 | 0.0 | 620 ms | 0 |
| Thu 13 | 0 | 0.0 | 597 ms | 0 |
| Thu 15 | 0 | 0.0 | 253 ms | 0 |
| Thu 17 | 0 | 0.0 | 1624 ms | 0 |
| Thu 19 | 0 | 0.0 | 2036 ms | 0 |
| Thu 21 | 0 | 0.0 | 684 ms | 0 |
| Thu 23 | 0 | 0.0 | 945 ms | 0 |
| Fri 01 | 0 | 0.0 | 871 ms | 0 |
| Fri 04 | 0 | 0.0 | 1833 ms | 0 |
| Fri 06 | 0 | 0.0 | 1417 ms | 0 |
| Fri 08 | 0 | 0.0 | 555 ms | 0 |
| Fri 10 | 0 | 0.0 | 675 ms | 0 |
| Fri 11 | 0 | 0.0 | 1593 ms | 0 |
| Fri 12 | 0 | 0.0 | 894 ms | 0 |
| Fri 14 | 0 | 0.0 | 1562 ms | 0 |
| Fri 16 | 0 | 0.0 | 178 ms | 0 |
| Fri 18 | 0 | 0.0 | 1284 ms | 0 |
| Fri 20 | 0 | 0.0 | 1158 ms | 0 |
| Fri 22 | 0 | 0.0 | 1173 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Depict yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Depict goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Depict alerts to Slack, Discord or a webhook — free.
We track Depict (depict.ai) as part of the AI group. AI visual merchandising, site search, and product recommendations. Curate what matters, automate the rest, on Shopify, Centra, and headless storefronts.
Depict publishes an official status page at status.depict.ai; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 1123 ms average, 178–1833 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Depict incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
1123 ms on average over the last 24 hours (178–1833 ms).
Yes, at https://status.depict.ai.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Depict here at once, the problem is on Depict's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Depict. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.