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 45 min ago. Last stored result reached it in 119 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 145 ms | 0 |
| Mon 16 | 0 | 0.0 | 179 ms | 0 |
| Mon 18 | 0 | 0.0 | 161 ms | 0 |
| Mon 20 | 0 | 0.0 | 125 ms | 0 |
| Mon 22 | 0 | 0.0 | 114 ms | 0 |
| Tue 00 | 0 | 0.0 | 175 ms | 0 |
| Tue 03 | 0 | 0.0 | 86 ms | 0 |
| Tue 05 | 0 | 0.0 | 2776 ms | 0 |
| Tue 07 | 0 | 0.0 | 364 ms | 0 |
| Tue 09 | 0 | 0.0 | 115 ms | 0 |
| Tue 11 | 0 | 0.0 | 1037 ms | 0 |
| Tue 13 | 0 | 0.0 | 158 ms | 0 |
| Tue 15 | 0 | 0.0 | 145 ms | 0 |
| Tue 18 | 0 | 0.0 | 110 ms | 0 |
| Tue 20 | 0 | 0.0 | 204 ms | 0 |
| Tue 22 | 0 | 0.0 | 142 ms | 0 |
| Wed 00 | 0 | 0.0 | 274 ms | 0 |
| Wed 03 | 0 | 0.0 | 135 ms | 0 |
| Wed 05 | 0 | 0.0 | 203 ms | 0 |
| Wed 07 | 0 | 0.0 | 115 ms | 0 |
| Wed 09 | 0 | 0.0 | 244 ms | 0 |
| Wed 12 | 0 | 0.0 | 74 ms | 0 |
| Wed 14 | 0 | 0.0 | 279 ms | 0 |
| Wed 16 | 0 | 0.0 | 245 ms | 0 |
| Wed 18 | 0 | 0.0 | 220 ms | 0 |
| Wed 20 | 0 | 0.0 | 210 ms | 0 |
| Wed 22 | 0 | 0.0 | 196 ms | 0 |
| Thu 01 | 0 | 0.0 | 107 ms | 0 |
| Thu 03 | 0 | 0.0 | 235 ms | 0 |
| Thu 05 | 0 | 0.0 | 303 ms | 0 |
| Thu 07 | 0 | 0.0 | 225 ms | 0 |
| Thu 09 | 0 | 0.0 | 215 ms | 0 |
| Thu 11 | 0 | 0.0 | 171 ms | 0 |
| Thu 13 | 0 | 0.0 | 258 ms | 0 |
| Thu 15 | 0 | 0.0 | 90 ms | 0 |
| Thu 17 | 0 | 0.0 | 156 ms | 0 |
| Thu 19 | 0 | 0.0 | 133 ms | 0 |
| Thu 21 | 0 | 0.0 | 151 ms | 0 |
| Thu 23 | 0 | 0.0 | 170 ms | 0 |
| Fri 01 | 0 | 0.0 | 135 ms | 0 |
| Fri 03 | 0 | 0.0 | 155 ms | 0 |
| Fri 06 | 0 | 0.0 | 1528 ms | 0 |
| Fri 08 | 0 | 0.0 | 124 ms | 0 |
| Fri 10 | 0 | 0.0 | 111 ms | 0 |
| Fri 12 | 0 | 0.0 | 101 ms | 0 |
| Fri 14 | 0 | 0.0 | 127 ms | 0 |
| Fri 15 | 0 | 0.0 | 103 ms | 0 |
| Fri 17 | 0 | 0.0 | 119 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 Truefoundry 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 Truefoundry goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Truefoundry alerts to Slack, Discord or a webhook — free.
We track Truefoundry (truefoundry.com) as part of the AI group. Deploy, secure, and scale LLMs and AI agents with TrueFoundry's enterprise AI Gateway and MCP Gateway. Rate limiting, observability, and compliance built in.
Truefoundry publishes an official status page at status.truefoundry.com; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 236 ms average, 101–1528 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Truefoundry incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
236 ms on average over the last 24 hours (101–1528 ms).
Yes, at https://status.truefoundry.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 Truefoundry here at once, the problem is on Truefoundry'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 Truefoundry. 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.