User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
transcend.io · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Tests transcend.io from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 485 ms · 9 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:15 | 0 | 0.0 | 461 ms | 0 |
| 03:30 | 0 | 0.0 | 318 ms | 0 |
| 03:45 | 0 | 0.0 | 366 ms | 0 |
| 04:00 | 0 | 0.0 | 411 ms | 0 |
| 04:15 | 0 | 0.0 | 208 ms | 0 |
| 04:30 | 0 | 0.0 | 429 ms | 0 |
| 04:45 | 0 | 0.0 | 406 ms | 0 |
| 05:00 | 0 | 0.0 | 551 ms | 0 |
| 05:15 | 0 | 0.0 | 211 ms | 0 |
| 05:30 | 0 | 0.0 | 320 ms | 0 |
| 05:45 | 0 | 0.0 | 408 ms | 0 |
| 06:00 | 0 | 0.0 | 152 ms | 0 |
| 06:15 | 0 | 0.0 | 364 ms | 0 |
| 06:30 | 0 | 0.0 | 211 ms | 0 |
| 06:45 | 0 | 0.0 | 404 ms | 0 |
| 07:00 | 0 | 0.0 | 309 ms | 0 |
| 07:15 | 0 | 0.0 | 342 ms | 0 |
| 07:30 | 0 | 0.0 | 234 ms | 0 |
| 07:45 | 0 | 0.0 | 423 ms | 0 |
| 08:00 | 0 | 0.0 | 214 ms | 0 |
| 08:15 | 0 | 0.0 | 431 ms | 0 |
| 08:30 | 0 | 0.0 | 196 ms | 0 |
| 08:45 | 0 | 0.0 | 329 ms | 0 |
| 09:00 | 0 | 0.0 | 291 ms | 0 |
| 09:15 | 0 | 0.0 | 430 ms | 0 |
| 09:30 | 0 | 0.0 | 534 ms | 0 |
| 09:45 | 0 | 0.0 | 354 ms | 0 |
| 10:00 | 0 | 0.0 | 324 ms | 0 |
| 10:15 | 0 | 0.0 | 303 ms | 0 |
| 10:30 | 0 | 0.0 | 166 ms | 0 |
| 10:45 | 0 | 0.0 | 176 ms | 0 |
| 11:00 | 0 | 0.0 | 280 ms | 0 |
| 11:15 | 0 | 0.0 | 327 ms | 0 |
| 11:30 | 0 | 0.0 | 434 ms | 0 |
| 11:45 | 0 | 0.0 | 378 ms | 0 |
| 12:00 | 0 | 0.0 | 356 ms | 0 |
| 12:15 | 0 | 0.0 | 290 ms | 0 |
| 12:30 | 0 | 0.0 | 164 ms | 0 |
| 12:45 | 0 | 0.0 | 225 ms | 0 |
| 13:00 | 0 | 0.0 | 261 ms | 0 |
| 13:15 | 0 | 0.0 | 485 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Transcend 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 Transcend goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Transcend alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Transcend is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Transcend's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.