Is bruyere.org down or not working?

What happened to bruyere.org, why did the website go down and not work? Here you can see who else is having the same problem with bruyere.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, bruyere.org is working fine, but single failures are possible. If bruyere.org does not work for you, then report your problem and write a comment.

Add comment

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

bruyere.org outage reports in the last 24 hours

bruyere.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.

Your name:

Message:

Technical information

Main page title:

Bruyère - Home

Main page description:

Bruyère plays a unique role in the region’s health care system providing specialized hospital care, primary care, long-term care, and assisted and independent living for seniors.

Main page keywords:

Bruyère

Protocol:

https

Status code:

200

Page size:

123.9 KB

Response time:

2.656sec.

IP:

199.212.80.11

Response headers:

cache-control:	private
content-type:	text/html; charset=utf-8
server:	Microsoft-IIS/10.0
set-cookie:	ASP.NET_SessionId=niaautqxztx4vizbiqzeests; path=/; HttpOnly; SameSite=Lax
x-aspnet-version:	4.0.30319
x-ua-compatible:	IE=edge
x-frame-options:	SAMEORIGIN
strict-transport-security:	max-age=31536000
x-content-type-options:	nosniff
referrer-policy:	same-origin
date:	Wed, 02 Oct 2024 23:20:42 GMT
connection:	close
content-length:	127436

DNS records:

A	address	199.212.80.11
A	ttl	21600
MX	exchange	ca-smtp-inbound-2.mimecast.com
MX	priority	10
MX	exchange	ca-smtp-inbound-1.mimecast.com
MX	priority	10
NS	value	dns2.easydns.net
NS	value	dns1.easydns.com
NS	value	ns2.d-zone.ca
NS	value	ns1.d-zone.ca
NS	value	dns3.easydns.org
TXT	entries	v=spf1 ip4:199.212.81.14 include:spf.protection.outlook.com include:spf.mandrillapp.com include:spf.constantcontact.com include:gifttool.com include:_spf.ultipro.com include:ca._netblocks.mimecast.com include:media2.akaraisin.com -all
SOA	nsname	dns1.easydns.com
	hostmaster	zone.easydns.com
	serial	1727795204
	refresh	3600
	retry	600
	expire	604800
	minttl	300
CAA	critical	0
CAA	issue	entrust.net
CAA	critical	0
CAA	issuewild	entrust.net
CAA	critical	0
CAA	issue	letsencrypt.org
CAA	critical	0
CAA	issue	amazon.com
CAA	critical	0
CAA	issuewild	letsencrypt.org

SEO headers

h1 Quick Links

h1 Join our Team

h1 Find a Service

h2 NEWS

h3 Welcoming Bruyère’s 2024-25 Board of Directors

h3 Celebrating Rehabilitation Day with a story of hope and recovery

h3 The Terminal Diner

h3 Annual public information meeting Thursday September 26, 2024

h3 Seniors need support to discontinue inappropriate use of sleeping pills, shares Barbara Farrell, PharmD

h3 Care through Connection: Access to Resources in the Community

h3 Brain stimulation: the future of stroke rehab

h3 Bruyère teams with Carefor in newly expanded Bruyère@Home program

h3 People with opioid use disorder less likely to receive palliative care at end of life

h3 The effects of multiple medications

How to solve problems with bruyere.org

Errors on the bruyere.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 bruyere.org on your own.