User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
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 97 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 115 ms | 0 |
| Mon 15 | 0 | 0.0 | 137 ms | 0 |
| Mon 17 | 0 | 0.0 | 704 ms | 0 |
| Mon 19 | 0 | 0.0 | 108 ms | 0 |
| Mon 21 | 0 | 0.0 | 134 ms | 0 |
| Tue 00 | 0 | 0.0 | 91 ms | 0 |
| Tue 02 | 0 | 0.0 | 133 ms | 0 |
| Tue 04 | 0 | 0.0 | 132 ms | 0 |
| Tue 06 | 0 | 0.0 | 674 ms | 0 |
| Tue 08 | 0 | 0.0 | 95 ms | 0 |
| Tue 10 | 0 | 0.0 | 278 ms | 0 |
| Tue 12 | 0 | 0.0 | 136 ms | 0 |
| Tue 14 | 0 | 0.0 | 148 ms | 0 |
| Tue 17 | 0 | 0.0 | 123 ms | 0 |
| Tue 19 | 0 | 0.0 | 151 ms | 0 |
| Tue 21 | 0 | 0.0 | 177 ms | 0 |
| Wed 00 | 0 | 0.0 | 177 ms | 0 |
| Wed 02 | 0 | 0.0 | 132 ms | 0 |
| Wed 04 | 0 | 0.0 | 124 ms | 0 |
| Wed 06 | 0 | 0.0 | 198 ms | 0 |
| Wed 08 | 0 | 0.0 | 186 ms | 0 |
| Wed 11 | 0 | 0.0 | 152 ms | 0 |
| Wed 13 | 0 | 0.0 | 299 ms | 0 |
| Wed 15 | 0 | 0.0 | 164 ms | 0 |
| Wed 17 | 0 | 0.0 | 108 ms | 0 |
| Wed 19 | 0 | 0.0 | 218 ms | 0 |
| Wed 22 | 0 | 0.0 | 119 ms | 0 |
| Thu 00 | 0 | 0.0 | 233 ms | 0 |
| Thu 02 | 0 | 0.0 | 357 ms | 0 |
| Thu 04 | 0 | 0.0 | 120 ms | 0 |
| Thu 06 | 0 | 0.0 | 166 ms | 0 |
| Thu 08 | 0 | 0.0 | 168 ms | 0 |
| Thu 10 | 0 | 0.0 | 170 ms | 0 |
| Thu 12 | 0 | 0.0 | 226 ms | 0 |
| Thu 14 | 0 | 0.0 | 357 ms | 0 |
| Thu 16 | 0 | 0.0 | 203 ms | 0 |
| Thu 18 | 0 | 0.0 | 146 ms | 0 |
| Thu 21 | 0 | 0.0 | 114 ms | 0 |
| Thu 23 | 0 | 0.0 | 230 ms | 0 |
| Fri 01 | 0 | 0.0 | 121 ms | 0 |
| Fri 03 | 0 | 0.0 | 130 ms | 0 |
| Fri 05 | 0 | 0.0 | 104 ms | 0 |
| Fri 07 | 0 | 0.0 | 125 ms | 0 |
| Fri 08 | 0 | 0.0 | 108 ms | 0 |
| Fri 10 | 0 | 0.0 | 239 ms | 0 |
| Fri 12 | 0 | 0.0 | 405 ms | 0 |
| Fri 14 | 0 | 0.0 | 313 ms | 0 |
| Fri 16 | 0 | 0.0 | 129 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 Trunk 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 Trunk goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Trunk alerts to Slack, Discord or a webhook — free.
We track Trunk (trunk.io) as part of the Cloud & developer group. Trunk skips the CI jobs your PR doesn't need, quarantines flaky tests and runs a parallel merge queue. Trusted by Brex, Ramp and Zillow.
Trunk publishes an official status page at status.trunk.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 181 ms average, 97–405 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Trunk incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
181 ms on average over the last 24 hours (97–405 ms).
Yes, at https://status.trunk.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Trunk here at once, the problem is on Trunk'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 Trunk. 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.