User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Trint down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → trint.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 107 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 31 ms | 0 |
| Mon 17 | 0 | 0.0 | 122 ms | 0 |
| Mon 19 | 0 | 0.0 | 41 ms | 0 |
| Mon 21 | 0 | 0.0 | 60 ms | 0 |
| Tue 00 | 0 | 0.0 | 67 ms | 0 |
| Tue 02 | 0 | 0.0 | 135 ms | 0 |
| Tue 04 | 0 | 0.0 | 66 ms | 0 |
| Tue 06 | 0 | 0.0 | 197 ms | 0 |
| Tue 08 | 0 | 0.0 | 58 ms | 0 |
| Tue 10 | 0 | 0.0 | 211 ms | 0 |
| Tue 12 | 0 | 0.0 | 92 ms | 0 |
| Tue 14 | 0 | 0.0 | 124 ms | 0 |
| Tue 17 | 0 | 0.0 | 65 ms | 0 |
| Tue 19 | 0 | 0.0 | 391 ms | 0 |
| Tue 21 | 0 | 0.0 | 87 ms | 0 |
| Wed 00 | 0 | 0.0 | 134 ms | 0 |
| Wed 02 | 0 | 0.0 | 51 ms | 0 |
| Wed 04 | 0 | 0.0 | 80 ms | 0 |
| Wed 06 | 0 | 0.0 | 130 ms | 0 |
| Wed 08 | 0 | 0.0 | 128 ms | 0 |
| Wed 11 | 0 | 0.0 | 150 ms | 0 |
| Wed 13 | 0 | 0.0 | 129 ms | 0 |
| Wed 15 | 0 | 0.0 | 91 ms | 0 |
| Wed 17 | 0 | 0.0 | 148 ms | 0 |
| Wed 19 | 0 | 0.0 | 120 ms | 0 |
| Wed 21 | 0 | 0.0 | 50 ms | 0 |
| Wed 23 | 0 | 0.0 | 91 ms | 0 |
| Thu 01 | 0 | 0.0 | 86 ms | 0 |
| Thu 03 | 0 | 0.0 | 108 ms | 0 |
| Thu 05 | 0 | 0.0 | 117 ms | 0 |
| Thu 07 | 0 | 0.0 | 62 ms | 0 |
| Thu 09 | 0 | 0.0 | 60 ms | 0 |
| Thu 12 | 0 | 0.0 | 123 ms | 0 |
| Thu 14 | 0 | 0.0 | 423 ms | 0 |
| Thu 16 | 0 | 0.0 | 126 ms | 0 |
| Thu 18 | 0 | 0.0 | 80 ms | 0 |
| Thu 20 | 0 | 0.0 | 124 ms | 0 |
| Thu 22 | 0 | 0.0 | 43 ms | 0 |
| Fri 00 | 0 | 0.0 | 109 ms | 0 |
| Fri 02 | 0 | 0.0 | 56 ms | 0 |
| Fri 05 | 0 | 0.0 | 85 ms | 0 |
| Fri 07 | 0 | 0.0 | 51 ms | 0 |
| Fri 08 | 0 | 0.0 | 100 ms | 0 |
| Fri 10 | 0 | 0.0 | 75 ms | 0 |
| Fri 11 | 0 | 0.0 | 102 ms | 0 |
| Fri 13 | 0 | 0.0 | 56 ms | 0 |
| Fri 15 | 0 | 0.0 | 120 ms | 0 |
| Fri 17 | 0 | 0.0 | 107 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Trint badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Trint yet. Outages of 10 minutes or more get their own page here.
Having trouble with Trint?
One report per service every 10 minutes from this network. No account.
Follow Trint
Get an email when Trint goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Trint alerts to Slack, Discord or a webhook — free.
About Trint
Trint, at trint.com, is one of the AI services we monitor. Fast-track your first draft with Trint's AI-connected media production. Transcribe, translate and collaborate in 50+ languages. Trusted by newsrooms worldwide.
Trint publishes an official status page at status.trint.com; when we can read it, its incident level is folded into the status shown here.
Common problems for 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: 83 ms average, 10–124 ms range across 17 successful checks.
Questions
Is Trint down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Trint last down?
We have not recorded a public Trint incident since monitoring began 8 days ago.
What is Trint's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Trint respond?
83 ms on average over the last 24 hours (10–124 ms).
Does Trint have an official status page?
Yes, at https://status.trint.com.
Trint not working for me but the status is fine. What now?
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 Trint here at once, the problem is on Trint'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 Trint. 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.