Is discourse.org down or not working?

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

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

discourse.org outage reports in the last 24 hours

discourse.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:
Discourse is the place to build civilized communities | Discourse - Civilized Discussion
Main page description:
Discourse is modern forum software for your community. Use it as a mailing list, discussion forum, long-form chat room, and more!
Protocol:
https
Status code:
200
Page size:
31.4 KB
Response time:
0.175sec.
IP:
18.239.18.24
Response headers:
content-type: text/html
content-length: 32191
connection: close
last-modified: Tue, 24 Sep 2024 15:23:28 GMT
x-amz-server-side-encryption: AES256
accept-ranges: bytes
server: AmazonS3
date: Thu, 03 Oct 2024 09:02:13 GMT
etag: "d681025529fe7f4a121c420ea0bbcbf1"
vary: Accept-Encoding
x-cache: Hit from cloudfront
via: 1.1 e14614617e85116e937d5168b35a94de.cloudfront.net (CloudFront)
x-amz-cf-pop: PRG50-C1
alt-svc: h3=":443"; ma=86400
x-amz-cf-id: _Ln9mz556mZTvmYxWCM9gfeUFaFNNBhMGIQTHG2c38RFGMuE7l8wsg==
age: 2637
x-frame-options: DENY
strict-transport-security: max-age=31536000; includeSubDomains; preload
DNS records:
A address18.239.18.38
ttl60
A address18.239.18.10
ttl60
A address18.239.18.24
ttl60
A address18.239.18.9
ttl60
MX exchangeaspmx2.googlemail.com
priority10
MX exchangealt1.aspmx.l.google.com
priority5
MX exchangeaspmx.l.google.com
priority1
MX exchangeaspmx3.googlemail.com
priority10
MX exchangealt2.aspmx.l.google.com
priority5
NS valuens-292.awsdns-36.com
NS valuens-1022.awsdns-63.net
NS valuens-1966.awsdns-53.co.uk
NS valuens-1205.awsdns-22.org
TXT entriesintacct-esk=D4F4987BDE4B635AE0539A220D0A21CF
TXT entriesv=spf1 include:metal._spf.discoursemail.com include:_spf.google.com include:amazonses.com include:_spf.intacct.com include:mailgun.org -all
TXT entriesgoogle-site-verification=Pu_UqH5gBStNMnQ5aBXZAm1JNSNRua45Vwzb3vMdXfU
TXT entries1password-site-verification=NALL2ULKKFFGTMZI2JGUTGBMHQ
TXT entriesh1-domain-verification=dbqPB1RbBB8dKpav6behQHW6te9fqkgYxh5j6KBT8WvAYk4K
TXT entriesgoogle-site-verification=fyWra9soC_wB9i_x1f1bLZ_u0shq84TdHC8ZHndxtHs
SOA nsnamens-1205.awsdns-22.org
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400
CAA critical0
issueletsencrypt.org
CAA critical0
issueamazonaws.com

SEO headers

h1 The online home for your community
h2 You’re in good company
h2 Thriving communities made easy
h2 A community you own
h4 Fully open source
h4 Truly portable data
h4 Unlimited conversation history
h3 Managed forum hosting from $20/month
h3 Trusted by Enterprise customers
h2 World-class hosted customer support
h3 Over 3.8 million posts created and 827 million page views served in August on our hosting!
h3 Sign up for our newsletter!
h5 Discourse is 100% free, open-source forum software. Forever. Meet the team that builds it.
h6 Features & Pricing
h6 Company
h6 Community & Support

How to solve problems with discourse.org

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