Is thecurrent.org down or not working?

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

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

thecurrent.org outage reports in the last 24 hours

thecurrent.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:
The Current | Great Music Lives Here
Main page description:
The Current, from Minnesota Public Radio, Great Music Lives Here
Protocol:
https
Status code:
200
Page size:
56.6 KB
Response time:
0.557sec.
IP:
52.202.186.183
Response headers:
content-type: text/html; charset=utf-8
content-length: 57987
connection: close
date: Tue, 01 Oct 2024 11:59:45 GMT
server: Apache
x-apm: AWS
x-nextjs-cache: STALE
x-powered-by: Next.js
cache-control: s-maxage=120, stale-while-revalidate
strict-transport-security: max-age=86400
x-content-type-options: nosniff
etag: "1mlv8xh9jy18o9"
vary: RSC,Next-Router-State-Tree,Next-Router-Prefetch,Accept-Encoding
x-cache: Hit from cloudfront
via: 1.1 edd6d90087c4f2b49e182778a2273adc.cloudfront.net (CloudFront)
x-amz-cf-pop: AMS54-C1
x-amz-cf-id: 2l4paZJpMgAPXNZIyVKC8net30_6qNoDKvn2XFB_EwXJUiYfUg_XxA==
age: 40
DNS records:
A address52.202.186.183
ttl300
MX exchangethecurrent-org.mail.protection.outlook.com
priority10
NS valuens1.mpr.org
NS valuens2.mpr.org
TXT entriesv=spf1 ip4:192.203.201.30 include:www.elabs7.com include:spf.protection.outlook.com -all
TXT entriesgoogle-site-verification=EUFRBxDSKcBG4GeS730AlDC8KCdUh8AeJFFYC-ACbuo
TXT entriesRQJjumMlLmw4owz0+zvkzTenUrHAXcHhzYV6xRJd7qkSm+Eg0BtLymWA/98vMJ+5HHn78RjHllHAXDA7j5BWSQ==
TXT entriesMS=ms36291408
TXT entriesfacebook-domain-verification=af27aen3v03z2dndeupdls5hjbi1fh
SOA nsnamens1.mpr.org
hostmasterunixadmin.mpr.org
serial2024010900
refresh3600
retry900
expire2419200
minttl3600

SEO headers

h1
h2 Now Playing - The Current
h2 We’re Powered by You!

How to solve problems with thecurrent.org

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