User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Shopping
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 22 min ago. Last stored result reached it in 338 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 00 | 0 | 0.0 | 575 ms | 0 |
| Wed 02 | 0 | 0.0 | 626 ms | 0 |
| Wed 05 | 0 | 0.0 | 729 ms | 0 |
| Wed 07 | 0 | 0.0 | 581 ms | 0 |
| Wed 09 | 0 | 0.0 | 337 ms | 0 |
| Wed 11 | 0 | 0.0 | 276 ms | 0 |
| Wed 13 | 0 | 0.0 | 625 ms | 0 |
| Wed 15 | 0 | 0.0 | 447 ms | 0 |
| Wed 18 | 0 | 0.0 | 809 ms | 0 |
| Wed 20 | 0 | 0.0 | 960 ms | 0 |
| Wed 22 | 0 | 0.0 | 591 ms | 0 |
| Thu 00 | 0 | 0.0 | 463 ms | 0 |
| Thu 02 | 0 | 0.0 | 534 ms | 0 |
| Thu 04 | 0 | 0.0 | 334 ms | 0 |
| Thu 06 | 0 | 0.0 | 576 ms | 0 |
| Thu 08 | 0 | 0.0 | 632 ms | 0 |
| Thu 11 | 0 | 0.0 | 531 ms | 0 |
| Thu 13 | 0 | 0.0 | 450 ms | 0 |
| Thu 15 | 0 | 0.0 | 319 ms | 0 |
| Thu 17 | 0 | 0.0 | 467 ms | 0 |
| Thu 19 | 0 | 0.0 | 471 ms | 0 |
| Thu 21 | 0 | 0.0 | 331 ms | 0 |
| Thu 23 | 0 | 0.0 | 702 ms | 0 |
| Fri 01 | 0 | 0.0 | 441 ms | 0 |
| Fri 03 | 0 | 0.0 | 1157 ms | 0 |
| Fri 05 | 0 | 0.0 | 646 ms | 0 |
| Fri 07 | 0 | 0.0 | 320 ms | 0 |
| Fri 09 | 0 | 0.0 | 389 ms | 0 |
| Fri 11 | 0 | 0.0 | 428 ms | 0 |
| Fri 12 | 0 | 0.0 | 630 ms | 0 |
| Fri 14 | 0 | 0.0 | 709 ms | 0 |
| Fri 16 | 0 | 0.0 | 603 ms | 0 |
| Fri 18 | 0 | 0.0 | 672 ms | 0 |
| Fri 19 | 0 | 0.0 | 270 ms | 0 |
| Fri 21 | 0 | 0.0 | 867 ms | 0 |
| Fri 23 | 0 | 0.0 | 408 ms | 0 |
| Sat 01 | 0 | 0.0 | 738 ms | 0 |
| Sat 03 | 0 | 0.0 | 547 ms | 0 |
| Sat 06 | 0 | 0.0 | 613 ms | 0 |
| Sat 07 | 0 | 0.0 | 469 ms | 0 |
| Sat 09 | 0 | 0.0 | 380 ms | 0 |
| Sat 10 | 0 | 0.0 | 302 ms | 0 |
| Sat 12 | 0 | 0.0 | 379 ms | 0 |
| Sat 14 | 0 | 0.0 | 429 ms | 0 |
| Sat 17 | 0 | 0.0 | 579 ms | 0 |
| Sat 19 | 0 | 0.0 | 581 ms | 0 |
| Sat 20 | 0 | 0.0 | 795 ms | 0 |
| Sat 23 | 0 | 0.0 | 338 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 Hoopla Billetter 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 Hoopla Billetter goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
We track Hoopla Billetter (hoopla.no) as part of the Shopping group. Hos Hoopla kjøper du billetter til hundrevis av arrangementer for store og små. Festivaler, konserter, sport og mye mer.
Hoopla Billetter publishes an official status page at status.hoopla.no; when we can read it, its incident level is folded into the status shown here.
Common problems for shopping services: checkout and payment errors, carts not loading, and order tracking problems.
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: 509 ms average, 248–795 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 Hoopla Billetter incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
509 ms on average over the last 24 hours (248–795 ms).
Yes, at https://status.hoopla.no.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For shopping services, watch for checkout and payment errors, carts not loading, and order tracking problems. If many people report Hoopla Billetter here at once, the problem is on Hoopla Billetter'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 Hoopla Billetter. 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.