Is odb.org down or not working?

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

Add comment

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

odb.org outage reports in the last 24 hours

odb.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.

Your name:

Message:

Technical information

Protocol:

https

Status code:

200

Page size:

3.3 KB

Response time:

0.561sec.

IP:

65.9.95.124

Response headers:

content-type:	text/html
content-length:	3345
connection:	close
x-amz-id-2:	5Cdx2obhwT9EOWs5ErM4qvgpKg8z9Tj+x9bPwJfXYxPzttBaE7oJOaUGDAZ0/I23w/Qo/JDO9L4=
x-amz-request-id:	GQEBSS9Y2VDZK7MC
date:	Tue, 01 Oct 2024 08:51:39 GMT
last-modified:	Tue, 17 Sep 2024 14:46:53 GMT
x-amz-server-side-encryption:	AES256
cache-control:	max-age=0, public
x-amz-version-id:	BPY3u0L_4JmAt3iivXdPgoPek8qonjgx
accept-ranges:	bytes
server:	AmazonS3
x-country:	NL
set-cookie:	country=NL; Path=/
access-control-allow-origin:	*
access-control-expose-headers:	Set-Cookie, X-Country
etag:	"b6e0d414b0334848b7c693a056227bda"
vary:	Accept-Encoding
x-cache:	Miss from cloudfront
via:	1.1 490623df85c571a18ba7da1511cc969e.cloudfront.net (CloudFront)
x-amz-cf-pop:	AMS1-P1
x-amz-cf-id:	lyZlDFnPorRVy9vNmBGMcn12A4AbIe0efWc_2DBB70BJdhSnYEV8Hw==

DNS records:

A	address	18.65.39.100
A	ttl	60
A	address	18.65.39.66
A	ttl	60
A	address	18.65.39.83
A	ttl	60
A	address	18.65.39.70
A	ttl	60
MX	exchange	mx1.hc3508-85.iphmx.com
MX	priority	70
MX	exchange	alt4.aspmx.l.google.com
MX	priority	10
MX	exchange	aspmx.l.google.com
MX	priority	1
MX	exchange	alt3.aspmx.l.google.com
MX	priority	10
MX	exchange	alt1.aspmx.l.google.com
MX	priority	5
MX	exchange	mx2.hc3508-85.iphmx.com
MX	priority	80
MX	exchange	alt2.aspmx.l.google.com
MX	priority	5
NS	value	ns-430.awsdns-53.com
NS	value	ns-1361.awsdns-42.org
NS	value	ns-938.awsdns-53.net
NS	value	ns-1666.awsdns-16.co.uk
TXT	entries	v=spf1 ip4:204.225.122.80 ip4:108.166.21.147 ip4:166.78.228.18 ip4:107.20.210.250 include:_spf.google.com include:_spf.psm.knowbe4.com include:spf.mailjet.com include:email.freshemail.com include:amazonses.com ~all
TXT	entries	apple-domain-verification=by01Z2RlElQ0Glcp
TXT	entries	shopify-verification-code=IBums5lk3s6VJh4WVOb6DRNE09jlT6
SOA	nsname	ns-1361.awsdns-42.org
	hostmaster	awsdns-hostmaster.amazon.com
	serial	1
	refresh	7200
	retry	900
	expire	1209600
	minttl	86400

How to solve problems with odb.org

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