Is edge.ca down or not working?

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

Add comment

What to do if the site edge.ca is not available? Try our guide.

edge.ca outage reports in the last 24 hours

edge.ca - 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:

102.1 the Edge102.1 the Edge – 102.1 the Edge

Main page description:

102.1 the Edge

Protocol:

https

Status code:

200

Page size:

102.1 KB

Response time:

0.367sec.

IP:

192.0.66.104

Response headers:

server:	nginx
date:	Wed, 02 Oct 2024 03:36:08 GMT
content-type:	text/html; charset=UTF-8
transfer-encoding:	chunked
connection:	close
vary:	Accept-Encoding
x-powered-by:	Corus Entertainment 2024
host-header:	a9130478a60e5f9135f765b23f26593b
content-security-policy-report-only:	default-src blob: https:; img-src data: https:; script-src 'unsafe-inline' 'unsafe-eval' blob: https:; style-src 'unsafe-inline' https:; font-src data: https:; frame-src https:; media-src data: https:; object-src 'none'; connect-src https:; frame-ancestors 'self';
x-content-type-options:	nosniff
x-frame-options:	SAMEORIGIN
link:	<https://edge.ca/wp-json/>; rel="https://api.w.org/"
strict-transport-security:	max-age=86400
cache-control:	max-age=300, must-revalidate
accept-ranges:	bytes
x-rq:	ams7 111 253 443
x-cache:	MISS

DNS records:

A	address	192.0.66.104
A	ttl	60
MX	exchange	alt3.us.email.fireeyecloud.com
MX	priority	40
MX	exchange	alt1.us.email.fireeyecloud.com
MX	priority	20
MX	exchange	alt2.us.email.fireeyecloud.com
MX	priority	30
MX	exchange	primary.us.email.fireeyecloud.com
MX	priority	10
NS	value	ns-132.awsdns-16.com
NS	value	ns-1409.awsdns-48.org
NS	value	ns-1644.awsdns-13.co.uk
NS	value	ns-805.awsdns-36.net
TXT	entries	google-site-verification=la5RMcaGpzjO_ObsAFB-WzcYSTWKXxGZ6p_AP__pqFg
TXT	entries	WQCsepylPU2LKdQPrNoComezeGJkGPh2e7zdbQ0C4kwoey94Iolq8Ds5RfmNmlNUVLG1ZdNZQBDbsT456H8D+Q==
TXT	entries	MS=ms90441098
TXT	entries	v=spf1 include:spf.protection.outlook.com -all
SOA	nsname	ns-132.awsdns-16.com
	hostmaster	awsdns-hostmaster.amazon.com
	serial	1
	refresh	7200
	retry	900
	expire	1209600
	minttl	86400
CAA	critical	0
CAA	issue	amazon.com
CAA	critical	0
CAA	issue	letsencrypt.org
CAA	critical	0
CAA	issue	digicert.com

SEO headers

h1 102.1 the Edge

h2 The Latest

h2 Concerts and Events

h2 Playlist

h2 You May Also Like

How to solve problems with edge.ca

Errors on the edge.ca 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 edge.ca on your own.