Is cnv.org down or not working?

What happened to cnv.org, why did the website go down and not work? Here you can see who else is having the same problem with cnv.org, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, cnv.org is working fine, but single failures are possible. If cnv.org does not work for you, then report your problem and write a comment.

What to do if the site cnv.org is not available? Try our guide.

cnv.org outage reports in the last 24 hours

cnv.org - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.
  • No registration required.
  • Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
  • Active links in the text of the message are not published, but displayed in plain text.
  • It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.

Technical information

Main page title:
City of North Vancouver
Main page description:
Official website of the City of North Vancouver, British Columbia, Canada.
Protocol:
https
Status code:
200
Page size:
441.2 KB
Response time:
3.513sec.
IP:
69.10.145.88
Response headers:
cache-control: no-cache, no-store
pragma: no-cache
content-type: text/html; charset=utf-8
expires: -1
server: Microsoft-IIS/10.0
set-cookie: shell#lang=en; path=/; secure; SameSite=None
content-security-policy: default-src https:; script-src https: 'unsafe-inline' 'unsafe-eval' https://*.flickr.com; style-src https: 'unsafe-inline' https://*.flickr.com; img-src https: data: blob:; media-src https: data: blob:; font-src https: data:; connect-src https: wss:
permissions-policy: fullscreen=(self), geolocation=*, camera=()
referrer-policy: strict-origin
strict-transport-security: max-age=31620000
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
date: Wed, 02 Oct 2024 00:38:14 GMT
connection: close
content-length: 451778
DNS records:
A address69.10.145.88
ttl14700
MX exchangemail.cnv.org
priority10
MX exchangemail2.cnv.org
priority10
NS valuens56.st.vc.shawcable.net
NS valuens5.no.cg.shawcable.net
NS valuewombat.cnv.org
NS valuens6.so.cg.shawcable.net
NS valuedns2.bigpipeinc.com
TXT entriesMS=ms78262902
TXT entriesgoogle-site-verification=ejQiINYJjZNbrfdxhzvhjsdmJwNRaqIc3ruMYM6wcF0
TXT entriesapple-domain-verification=e6c3IgdqZc7Wz0rD
TXT entriesmGMgg4TrF0CJchVOVxMveBdldYMwJNsqM2UCUIDJ7YmBuTxwEXyTx3FoQOQQOVRntY0CLFjA5pLzcxikO8ofaw==
TXT entriesfacebook-domain-verification=9k2etc3wr4sgjtga77l069k26j948b
TXT entriesv=spf1 ip4:208.98.201.64/26 ~all
TXT entrieslogmein-verification-code=c50e84d5-6601-4f60-b048-82c72376f950
TXT entriessecuremail._
TXT entriescisco-ci-domain-verification=52d3c9ebd73091a3fe3394dccca4dbe348e263f7445042ad4f413ac00136db10
TXT entriesapple-domain-verification=tx2y1gsTIxMROiL8
SOA nsnamewombat.cnv.org
hostmastersysadmin.cnv.org
serial892
refresh14400
retry3600
expire1209600
minttl300

SEO headers

h1

How to solve problems with cnv.org

Errors on the cnv.org website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of cnv.org on your own.