DNB help and reporting
Use the provider’s help for DNB personal banking, business access and payments. Keep the failed step and its timestamp ready.
Live Domain Check
Run a live reachability check for dnb.no. Compare the regional responses with the problem you see in DNB.
Find DNB help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
For DNB users in Norway, compare DNB personal banking, business access and payments with the public dnb.no website. A response from that hostname does not verify every signed-in account or app operation.
The checker above requests dnb.no from eight configured locations and shows the responses and measurement times. Compare those observations with the actual DNB action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Other checks in shopping & services: SpareBank 1 status check, FINN status check, Vy status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse shopping and payment checks.
Use the provider’s help for DNB personal banking, business access and payments. Keep the failed step and its timestamp ready.
Open the website in your browser and compare it with the result above.
Open DNB help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Banking channel, failed step, exact message and time; never share PINs, passwords, account numbers or verification codes.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to DNB.
These are troubleshooting comparisons, not claims that DNB is currently experiencing a particular incident.
Choose the relevant personal or business channel; a public DNB page does not confirm a specific account session.
Check the recorded account or payment state before retrying. Use the bank’s own help channel for verification or account restrictions.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Repeat the same action in a second browser or on another available connection, keeping the item and account the same. Change one thing at a time so the result is comparable. Leave required workplace or school security controls in place.
Follow the website troubleshooting guide for connection checks. Preserve any unsent work before refreshing a form or changing a session.
Choose the relevant personal or business channel; a public DNB page does not confirm a specific account session. Check the recorded account or payment state before retrying. Use the bank’s own help channel for verification or account restrictions.
Use the community buttons on this page to share whether the service works for you. For help from DNB, use the official help/reporting resource linked above. Use the provider’s help for DNB personal banking, business access and payments. Keep the failed step and its timestamp ready.
For DNB users in Norway, compare DNB personal banking, business access and payments with the public dnb.no website. A response from that hostname does not verify every signed-in account or app operation. Compare the original measurement time with the specific action that failed.
Banking channel, failed step, exact message and time; never share PINs, passwords, account numbers or verification codes.