Is frieze.com down or not working?

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

What to do if the site frieze.com is not available? Try our guide.

frieze.com outage reports in the last 24 hours

frieze.com - 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:
Home | Frieze
Main page description:
Frieze is the definitive resource for contemporary art and culture, offering reviews, essays, interviews, videos and podcasts from around the world and three annual art fairs in London, New York and Los Angeles.
Protocol:
https
Status code:
200
Page size:
131.6 KB
Response time:
0.422sec.
IP:
18.173.187.58
Response headers:
content-type: text/html; charset=UTF-8
transfer-encoding: chunked
connection: close
report-to: {"group":"heroku-nel","max_age":3600,"endpoints":[{"url":"https://nel.heroku.com/reports?ts=1727788594&sid=c4c9725f-1ab0-44d8-820f-430df2718e11&s=ulkjPXbtBgVVYr4QAX172Z%2BMtWFTLJ7xPnQ3aJhqCps%3D"}]}
reporting-endpoints: heroku-nel=https://nel.heroku.com/reports?ts=1727788594&sid=c4c9725f-1ab0-44d8-820f-430df2718e11&s=ulkjPXbtBgVVYr4QAX172Z%2BMtWFTLJ7xPnQ3aJhqCps%3D
nel: {"report_to":"heroku-nel","max_age":3600,"success_fraction":0.005,"failure_fraction":0.05,"response_headers":["Via"]}
date: Tue, 01 Oct 2024 12:22:13 GMT
server: Apache
cache-control: max-age=31536000, public
content-language: en
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
expires: Sun, 19 Nov 1978 05:00:00 GMT
x-drupal-cache: HIT
last-modified: Tue, 01 Oct 2024 12:22:13 GMT
etag: "1727785333"
via: 1.1 vegur, 1.1 e3d75b6784ddc24c20248c83cdbce544.cloudfront.net (CloudFront)
vary: Cookie
x-cache: Miss from cloudfront
x-amz-cf-pop: MUC50-P5
x-amz-cf-id: 5slKeJkQ-260uOi9Je-U1-PrMr6PCi0BkZjV61svvKmA2cWyOMDUTw==
DNS records:
A address18.239.83.126
ttl60
A address18.239.83.87
ttl60
A address18.239.83.16
ttl60
A address18.239.83.90
ttl60
MX exchangeus-smtp-inbound-2.mimecast.com
priority10
MX exchangeus-smtp-inbound-1.mimecast.com
priority10
NS valuens-1282.awsdns-32.org
NS valuens-1987.awsdns-56.co.uk
NS valuens-66.awsdns-08.com
NS valuens-716.awsdns-25.net
TXT entries0ed1fe018a6605fa08ed9445fe8512ee6d09d2a104
TXT entriesatlassian-domain-verification=9B4OIeOHqnab/tFUEAx0sVWzd/p0KdS6oJmf8yhVvuXipVKg2yedbdPREQ5p/qDD
TXT entriesmandrill_verify.2JP0NB779CM7r1y5pjK1Ig
TXT entriesv=spf1 include:_netblocks.mimecast.com include:spf.protection.outlook.com include:spf.mandrillapp.com -all
TXT entriesMS=ms64651366
TXT entriesapple-domain-verification=dtwbg9TcYz4SBkiW
TXT entriesadobe-sign-verification=12813332ee86263cc54e9b1687e39677
TXT entriesbox-domain-verification=edb85437ca72f31e767911f841f439f89163c386727c3d540cd3d8bb219da6d1
TXT entriesciscocidomainverification=5cf93f80d58c7599c5a585cc85b304254af8071c9754d00f924e216a61bf1eb5
TXT entriesgoogle-site-verification=SPYyjaOBvktg7kugJDBayrDnUnG4YxY4Hvnzjb53ngo
TXT entriesdropbox-domain-verification=t5g1ms57q9ht
SOA nsnamens-716.awsdns-25.net
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

How to solve problems with frieze.com

Errors on the frieze.com 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 frieze.com on your own.