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 2 hr ago. Last stored result reached it in 138 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 173 ms | 0 |
| Mon 22 | 0 | 0.0 | 186 ms | 0 |
| Tue 00 | 0 | 0.0 | 149 ms | 0 |
| Tue 02 | 0 | 0.0 | 189 ms | 0 |
| Tue 04 | 0 | 0.0 | 286 ms | 0 |
| Tue 07 | 0 | 0.0 | 226 ms | 0 |
| Tue 09 | 0 | 0.0 | 143 ms | 0 |
| Tue 11 | 0 | 0.0 | 153 ms | 0 |
| Tue 13 | 0 | 0.0 | 163 ms | 0 |
| Tue 15 | 0 | 0.0 | 273 ms | 0 |
| Tue 17 | 0 | 0.0 | 81 ms | 0 |
| Tue 20 | 0 | 0.0 | 256 ms | 0 |
| Tue 22 | 0 | 0.0 | 415 ms | 0 |
| Wed 00 | 0 | 0.0 | 412 ms | 0 |
| Wed 02 | 0 | 0.0 | 202 ms | 0 |
| Wed 05 | 0 | 0.0 | 174 ms | 0 |
| Wed 07 | 0 | 0.0 | 260 ms | 0 |
| Wed 09 | 0 | 0.0 | 176 ms | 0 |
| Wed 11 | 0 | 0.0 | 274 ms | 0 |
| Wed 14 | 0 | 0.0 | 482 ms | 0 |
| Wed 16 | 0 | 0.0 | 299 ms | 0 |
| Wed 18 | 0 | 0.0 | 278 ms | 0 |
| Wed 20 | 0 | 0.0 | 338 ms | 0 |
| Wed 22 | 0 | 0.0 | 274 ms | 0 |
| Thu 00 | 0 | 0.0 | 105 ms | 0 |
| Thu 03 | 0 | 0.0 | 287 ms | 0 |
| Thu 05 | 0 | 0.0 | 220 ms | 0 |
| Thu 07 | 0 | 0.0 | 249 ms | 0 |
| Thu 09 | 0 | 0.0 | 243 ms | 0 |
| Thu 11 | 0 | 0.0 | 156 ms | 0 |
| Thu 13 | 0 | 0.0 | 249 ms | 0 |
| Thu 15 | 0 | 0.0 | 185 ms | 0 |
| Thu 17 | 0 | 0.0 | 238 ms | 0 |
| Thu 19 | 0 | 0.0 | 271 ms | 0 |
| Thu 21 | 0 | 0.0 | 167 ms | 0 |
| Thu 22 | 0 | 0.0 | 170 ms | 0 |
| Fri 01 | 0 | 0.0 | 279 ms | 0 |
| Fri 03 | 0 | 0.0 | 212 ms | 0 |
| Fri 05 | 0 | 0.0 | 296 ms | 0 |
| Fri 07 | 0 | 0.0 | 197 ms | 0 |
| Fri 09 | 0 | 0.0 | 106 ms | 0 |
| Fri 10 | 0 | 0.0 | 172 ms | 0 |
| Fri 12 | 0 | 0.0 | 163 ms | 0 |
| Fri 14 | 0 | 0.0 | 177 ms | 0 |
| Fri 16 | 0 | 0.0 | 309 ms | 0 |
| Fri 17 | 0 | 0.0 | 173 ms | 0 |
| Fri 19 | 0 | 0.0 | 172 ms | 0 |
| Fri 20 | 0 | 0.0 | 138 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 Tixly 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 Tixly goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Tixly alerts to Slack, Discord or a webhook — free.
We track Tixly (tixly.com) as part of the Cloud & developer group. A fully integrated suite of event ticketing solutions that helps you deliver better experiences for your ticket buyers and drive box office results.
Tixly publishes an official status page at status.tixly.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 191 ms average, 62–309 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 Tixly incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
191 ms on average over the last 24 hours (62–309 ms).
Yes, at https://status.tixly.com.
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 Tixly here at once, the problem is on Tixly'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 Tixly. 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.