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 10 min ago. Last stored result reached it in 181 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 144 ms | 0 |
| Tue 00 | 0 | 0.0 | 104 ms | 0 |
| Tue 02 | 0 | 0.0 | 68 ms | 0 |
| Tue 05 | 0 | 0.0 | 130 ms | 0 |
| Tue 07 | 0 | 0.0 | 247 ms | 0 |
| Tue 09 | 0 | 0.0 | 199 ms | 0 |
| Tue 11 | 0 | 0.0 | 105 ms | 0 |
| Tue 13 | 0 | 0.0 | 176 ms | 0 |
| Tue 15 | 0 | 0.0 | 315 ms | 0 |
| Tue 18 | 0 | 0.0 | 236 ms | 0 |
| Tue 20 | 0 | 0.0 | 275 ms | 0 |
| Tue 22 | 0 | 0.0 | 207 ms | 0 |
| Wed 00 | 0 | 0.0 | 78 ms | 0 |
| Wed 03 | 0 | 0.0 | 205 ms | 0 |
| Wed 05 | 0 | 0.0 | 136 ms | 0 |
| Wed 07 | 0 | 0.0 | 74 ms | 0 |
| Wed 09 | 0 | 0.0 | 192 ms | 0 |
| Wed 12 | 0 | 0.0 | 336 ms | 0 |
| Wed 14 | 0 | 0.0 | 240 ms | 0 |
| Wed 16 | 0 | 0.0 | 186 ms | 0 |
| Wed 18 | 0 | 0.0 | 129 ms | 0 |
| Wed 20 | 0 | 0.0 | 114 ms | 0 |
| Wed 22 | 0 | 0.0 | 155 ms | 0 |
| Thu 01 | 0 | 0.0 | 30 ms | 0 |
| Thu 03 | 0 | 0.0 | 28 ms | 0 |
| Thu 05 | 0 | 0.0 | 194 ms | 0 |
| Thu 07 | 0 | 0.0 | 374 ms | 0 |
| Thu 09 | 0 | 0.0 | 74 ms | 0 |
| Thu 11 | 0 | 0.0 | 354 ms | 0 |
| Thu 13 | 0 | 0.0 | 158 ms | 0 |
| Thu 15 | 0 | 0.0 | 94 ms | 0 |
| Thu 17 | 0 | 0.0 | 164 ms | 0 |
| Thu 19 | 0 | 0.0 | 167 ms | 0 |
| Thu 21 | 0 | 0.0 | 354 ms | 0 |
| Thu 23 | 0 | 0.0 | 110 ms | 0 |
| Fri 01 | 0 | 0.0 | 192 ms | 0 |
| Fri 03 | 0 | 0.0 | 90 ms | 0 |
| Fri 06 | 0 | 0.0 | 305 ms | 0 |
| Fri 08 | 0 | 0.0 | 230 ms | 0 |
| Fri 10 | 0 | 0.0 | 193 ms | 0 |
| Fri 11 | 0 | 0.0 | 216 ms | 0 |
| Fri 13 | 0 | 0.0 | 53 ms | 0 |
| Fri 14 | 0 | 0.0 | 16 ms | 0 |
| Fri 15 | 0 | 0.0 | 136 ms | 0 |
| Fri 17 | 0 | 0.0 | 164 ms | 0 |
| Fri 18 | 0 | 0.0 | 190 ms | 0 |
| Fri 19 | 0 | 0.0 | 507 ms | 0 |
| Fri 21 | 0 | 0.0 | 181 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for TraceGains 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 TraceGains goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send TraceGains alerts to Slack, Discord or a webhook — free.
TraceGains is listed in our AI category and checked at tracegains.com. Imagine networking people and ingredient data togetherin new ways to achieve business agility. Together with TraceGains, the world's only Networked Ingredients Marketplace, we can overcome today's supply chain challenges.
TraceGains publishes an official status page at status.tracegains.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 185 ms average, 16–507 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 TraceGains incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
185 ms on average over the last 24 hours (16–507 ms).
Yes, at https://status.tracegains.com.
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 TraceGains here at once, the problem is on TraceGains'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 TraceGains. 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.