User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
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 26 min ago. Last stored result reached it in 486 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 09 | 0 | 0.0 | 451 ms | 0 |
| Tue 11 | 0 | 0.0 | 52 ms | 0 |
| Tue 13 | 0 | 0.0 | 409 ms | 0 |
| Tue 15 | 0 | 0.0 | 82 ms | 0 |
| Tue 18 | 0 | 0.0 | 603 ms | 0 |
| Tue 20 | 0 | 0.0 | 648 ms | 0 |
| Tue 22 | 0 | 0.0 | 615 ms | 0 |
| Wed 00 | 0 | 0.0 | 85 ms | 0 |
| Wed 03 | 0 | 0.0 | 49 ms | 0 |
| Wed 05 | 0 | 0.0 | 90 ms | 0 |
| Wed 07 | 0 | 0.0 | 590 ms | 0 |
| Wed 09 | 0 | 0.0 | 562 ms | 0 |
| Wed 12 | 0 | 0.0 | 57 ms | 0 |
| Wed 14 | 0 | 0.0 | 459 ms | 0 |
| Wed 16 | 0 | 0.0 | 447 ms | 0 |
| Wed 18 | 0 | 0.0 | 827 ms | 0 |
| Wed 20 | 0 | 0.0 | 369 ms | 0 |
| Wed 22 | 0 | 0.0 | 86 ms | 0 |
| Thu 01 | 0 | 0.0 | 456 ms | 0 |
| Thu 03 | 0 | 0.0 | 686 ms | 0 |
| Thu 05 | 0 | 0.0 | 561 ms | 0 |
| Thu 07 | 0 | 0.0 | 662 ms | 0 |
| Thu 09 | 0 | 0.0 | 602 ms | 0 |
| Thu 11 | 0 | 0.0 | 122 ms | 0 |
| Thu 13 | 0 | 0.0 | 480 ms | 0 |
| Thu 15 | 0 | 0.0 | 684 ms | 0 |
| Thu 17 | 0 | 0.0 | 478 ms | 0 |
| Thu 19 | 0 | 0.0 | 425 ms | 0 |
| Thu 21 | 0 | 0.0 | 74 ms | 0 |
| Thu 23 | 0 | 0.0 | 497 ms | 0 |
| Fri 01 | 0 | 0.0 | 460 ms | 0 |
| Fri 03 | 0 | 0.0 | 50 ms | 0 |
| Fri 06 | 0 | 0.0 | 411 ms | 0 |
| Fri 08 | 0 | 0.0 | 456 ms | 0 |
| Fri 10 | 0 | 0.0 | 192 ms | 0 |
| Fri 12 | 0 | 0.0 | 585 ms | 0 |
| Fri 14 | 0 | 0.0 | 595 ms | 0 |
| Fri 16 | 0 | 0.0 | 640 ms | 0 |
| Fri 17 | 0 | 0.0 | 65 ms | 0 |
| Fri 19 | 0 | 0.0 | 597 ms | 0 |
| Fri 21 | 0 | 0.0 | 350 ms | 0 |
| Fri 22 | 0 | 0.0 | 583 ms | 0 |
| Sat 00 | 0 | 0.0 | 366 ms | 0 |
| Sat 02 | 0 | 0.0 | 430 ms | 0 |
| Sat 04 | 0 | 0.0 | 347 ms | 0 |
| Sat 06 | 0 | 0.0 | 528 ms | 0 |
| Sat 07 | 0 | 0.0 | 602 ms | 0 |
| Sat 09 | 0 | 0.0 | 486 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 TicketCo AS 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 TicketCo AS goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send TicketCo AS alerts to Slack, Discord or a webhook — free.
We track TicketCo AS (ticketco.events) as part of the Money group. TicketCo is a unified platform for efficient event payments, minimising work and maximising sales
TicketCo AS publishes an official status page at status.ticketco.events; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with money services: login and two-factor problems, payments or transfers failing, and app errors.
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: 443 ms average, 44–662 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public TicketCo AS incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
443 ms on average over the last 24 hours (44–662 ms).
Yes, at https://status.ticketco.events.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report TicketCo AS here at once, the problem is on TicketCo AS'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 TicketCo AS. 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.