Is wbez.org down or not working?

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

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

wbez.org outage reports in the last 24 hours

wbez.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:
WBEZ Chicago - WBEZ ChicagoclockCST_Donation Inline
Protocol:
https
Status code:
200
Page size:
690.1 KB
Response time:
0.471sec.
IP:
65.9.95.12
Response headers:
content-type: text/html;charset=UTF-8
transfer-encoding: chunked
connection: close
date: Tue, 01 Oct 2024 07:56:07 GMT
server: istio-envoy
strict-transport-security: max-age=31536000; includeSubDomains
x-powered-by: Brightspot
x-envoy-upstream-service-time: 588
x-envoy-decorator-operation: brightspot-frontend-verify.cst-web.svc.cluster.local:80/*
vary: Accept-Encoding
x-cache: Hit from cloudfront
via: 1.1 1d04caaed0a43993076e404ebf3738da.cloudfront.net (CloudFront)
x-amz-cf-pop: PRG50-C1
x-amz-cf-id: _EJ24daeUyZG7EH_GRRaI3DLBWiPl2A4tWfB2GkAhX5cfI3R0zIVjg==
age: 109
DNS records:
A address18.245.60.6
ttl60
A address18.245.60.31
ttl60
A address18.245.60.56
ttl60
A address18.245.60.23
ttl60
MX exchangealt3.aspmx.l.google.com
priority10
MX exchangealt2.aspmx.l.google.com
priority5
MX exchangeaspmx.l.google.com
priority1
MX exchangealt1.aspmx.l.google.com
priority5
MX exchangealt4.aspmx.l.google.com
priority10
NS valuens-1527.awsdns-62.org
NS valuens-1006.awsdns-61.net
NS valuens-348.awsdns-43.com
NS valuens-1820.awsdns-35.co.uk
TXT entriesgoogle-site-verification=NKdkUShVt_jo28Yb1aPVcktcsiwCmjmIDs0zn3KQw8U
TXT entriesnotion-domain-verification=c3mGkWFZTNjiKTdGYzEQ03dLTnxxxbxLXrAealcuaBp
TXT entriesgoogle-site-verification=j_tXFA7TUNArlOxyo_ekQ3KT7xhgkpnwya0eqB_JaN8
TXT entriesv=spf1 ip4:208.117.55.132 ip4:70.34.134.132 include:_spf.psm.knowbe4.com include:amazonses.com include:_spf.google.com include:_spf.intacct.com include:sendgrid.net include:cust-spf.exacttarget.com -all
SOA nsnamens-348.awsdns-43.com
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

SEO headers

h3 News
h3 Listen
h3 More
h3 News
h3 Listen
h3 More
h2 Latest from Reset with Sasha-Ann Simons
h2 The Rundown Podcast & Featured Audio
h2 Arts & Culture from WBEZ
h2 Accurate Information. Reliable Reporting. Diverse Perspectives.
h2 More News
h2 Curious City
h2 What's That Building?
h2 In Case You Missed It
h2 Upcoming WBEZ Events

How to solve problems with wbez.org

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