User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Entertainment
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 min ago. Last stored result reached it in 573 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 21 | 0 | 0.0 | 795 ms | 0 |
| Tue 23 | 0 | 0.0 | 522 ms | 0 |
| Wed 01 | 0 | 0.0 | 801 ms | 0 |
| Wed 03 | 0 | 0.0 | 576 ms | 0 |
| Wed 05 | 0 | 0.0 | 598 ms | 0 |
| Wed 07 | 0 | 0.0 | 615 ms | 0 |
| Wed 10 | 0 | 0.0 | 559 ms | 0 |
| Wed 12 | 0 | 0.0 | 753 ms | 0 |
| Wed 14 | 0 | 0.0 | 1813 ms | 0 |
| Wed 16 | 0 | 0.0 | 605 ms | 0 |
| Wed 18 | 0 | 0.0 | 550 ms | 0 |
| Wed 20 | 0 | 0.0 | 691 ms | 0 |
| Wed 23 | 0 | 0.0 | 937 ms | 0 |
| Thu 01 | 0 | 0.0 | 824 ms | 0 |
| Thu 03 | 0 | 0.0 | 676 ms | 0 |
| Thu 05 | 0 | 0.0 | 547 ms | 0 |
| Thu 07 | 0 | 0.0 | 481 ms | 0 |
| Thu 09 | 0 | 0.0 | 729 ms | 0 |
| Thu 11 | 0 | 0.0 | 534 ms | 0 |
| Thu 13 | 0 | 0.0 | 690 ms | 0 |
| Thu 15 | 0 | 0.0 | 638 ms | 0 |
| Thu 16 | 0 | 0.0 | 677 ms | 0 |
| Thu 18 | 0 | 0.0 | 807 ms | 0 |
| Thu 20 | 0 | 0.0 | 629 ms | 0 |
| Thu 22 | 0 | 0.0 | 616 ms | 0 |
| Fri 00 | 0 | 0.0 | 543 ms | 0 |
| Fri 02 | 0 | 0.0 | 597 ms | 0 |
| Fri 04 | 0 | 0.0 | 730 ms | 0 |
| Fri 06 | 0 | 0.0 | 540 ms | 0 |
| Fri 08 | 0 | 0.0 | 681 ms | 0 |
| Fri 10 | 0 | 0.0 | 553 ms | 0 |
| Fri 12 | 0 | 0.0 | 803 ms | 0 |
| Fri 14 | 0 | 0.0 | 552 ms | 0 |
| Fri 16 | 0 | 0.0 | 551 ms | 0 |
| Fri 18 | 0 | 0.0 | 570 ms | 0 |
| Fri 20 | 0 | 0.0 | 551 ms | 0 |
| Fri 21 | 0 | 0.0 | 558 ms | 0 |
| Fri 23 | 0 | 0.0 | 597 ms | 0 |
| Sat 01 | 0 | 0.0 | 616 ms | 0 |
| Sat 02 | 0 | 0.0 | 615 ms | 0 |
| Sat 03 | 0 | 0.0 | 587 ms | 0 |
| Sat 05 | 0 | 0.0 | 594 ms | 0 |
| Sat 07 | 0 | 0.0 | 725 ms | 0 |
| Sat 09 | 0 | 0.0 | 551 ms | 0 |
| Sat 12 | 0 | 0.0 | 510 ms | 0 |
| Sat 14 | 0 | 0.0 | 572 ms | 0 |
| Sat 16 | 0 | 0.0 | 594 ms | 0 |
| Sat 19 | 0 | 0.0 | 573 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 NTB 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 NTB 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 NTB (ntb.no) as part of the Entertainment group. NTB er totalleverandør av nyheter, bilder og video, kommunikasjonstjenester og teknologi.
NTB publishes an official status page at status.ntb.no; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with entertainment services: streams buffering or not starting, playback errors, and app sign-in problems.
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: 588 ms average, 510–725 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public NTB incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
588 ms on average over the last 24 hours (510–725 ms).
Yes, at https://status.ntb.no.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For entertainment services, watch for streams buffering or not starting, playback errors, and app sign-in problems. If many people report NTB here at once, the problem is on NTB'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 NTB. 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.