User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
tickettailor.com · 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 5 min ago. Last stored result reached it in 300 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 06 | 0 | 0.0 | 295 ms | 0 |
| Tue 08 | 0 | 0.0 | 281 ms | 0 |
| Tue 10 | 0 | 0.0 | 417 ms | 0 |
| Tue 12 | 0 | 0.0 | 370 ms | 0 |
| Tue 14 | 0 | 0.0 | 336 ms | 0 |
| Tue 17 | 0 | 0.0 | 598 ms | 0 |
| Tue 19 | 0 | 0.0 | 325 ms | 0 |
| Tue 21 | 0 | 0.0 | 287 ms | 0 |
| Tue 23 | 0 | 0.0 | 331 ms | 0 |
| Wed 02 | 0 | 0.0 | 335 ms | 0 |
| Wed 04 | 0 | 0.0 | 336 ms | 0 |
| Wed 06 | 0 | 0.0 | 305 ms | 0 |
| Wed 08 | 0 | 0.0 | 355 ms | 0 |
| Wed 11 | 0 | 0.0 | 256 ms | 0 |
| Wed 13 | 0 | 0.0 | 827 ms | 0 |
| Wed 15 | 0 | 0.0 | 352 ms | 0 |
| Wed 17 | 0 | 0.0 | 369 ms | 0 |
| Wed 19 | 0 | 0.0 | 371 ms | 0 |
| Wed 21 | 0 | 0.0 | 339 ms | 0 |
| Thu 00 | 0 | 0.0 | 350 ms | 0 |
| Thu 02 | 0 | 0.0 | 555 ms | 0 |
| Thu 04 | 0 | 0.0 | 322 ms | 0 |
| Thu 06 | 0 | 0.0 | 429 ms | 0 |
| Thu 08 | 0 | 0.0 | 275 ms | 0 |
| Thu 10 | 0 | 0.0 | 331 ms | 0 |
| Thu 12 | 0 | 0.0 | 353 ms | 0 |
| Thu 14 | 0 | 0.0 | 388 ms | 0 |
| Thu 16 | 0 | 0.0 | 349 ms | 0 |
| Thu 18 | 0 | 0.0 | 268 ms | 0 |
| Thu 20 | 0 | 0.0 | 312 ms | 0 |
| Thu 23 | 0 | 0.0 | 369 ms | 0 |
| Fri 01 | 0 | 0.0 | 293 ms | 0 |
| Fri 03 | 0 | 0.0 | 305 ms | 0 |
| Fri 05 | 0 | 0.0 | 336 ms | 0 |
| Fri 07 | 0 | 0.0 | 400 ms | 0 |
| Fri 09 | 0 | 0.0 | 427 ms | 0 |
| Fri 10 | 0 | 0.0 | 335 ms | 0 |
| Fri 11 | 0 | 0.0 | 321 ms | 0 |
| Fri 12 | 0 | 0.0 | 536 ms | 0 |
| Fri 14 | 0 | 0.0 | 333 ms | 0 |
| Fri 17 | 0 | 0.0 | 265 ms | 0 |
| Fri 18 | 0 | 0.0 | 332 ms | 0 |
| Fri 19 | 0 | 0.0 | 261 ms | 0 |
| Fri 21 | 0 | 0.0 | 431 ms | 0 |
| Fri 23 | 0 | 0.0 | 296 ms | 0 |
| Sat 01 | 0 | 0.0 | 250 ms | 0 |
| Sat 03 | 0 | 0.0 | 333 ms | 0 |
| Sat 06 | 0 | 0.0 | 300 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Ticket Tailor 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 Ticket Tailor goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Ticket Tailor alerts to Slack, Discord or a webhook — free.
Ticket Tailor is listed in our Cloud & developer category and checked at tickettailor.com. The world's most loved event ticketing platform. Whether it’s your first event ever, or your biggest event yet, we make it simple to sell tickets online.
Ticket Tailor publishes an official status page at status.tickettailor.com; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 350 ms average, 250–567 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 Ticket Tailor incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
350 ms on average over the last 24 hours (250–567 ms).
Yes, at https://status.tickettailor.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 Ticket Tailor here at once, the problem is on Ticket Tailor'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 Ticket Tailor. 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.