Is near.org down or not working?

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

Add comment

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

near.org outage reports in the last 24 hours

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

Main page title:

NEAR | Blockchains, Abstracted

Main page description:

NEAR is the chain abstraction stack, empowering builders to create apps that scale to billions of users and across all blockchains.

Protocol:

https

Status code:

200

Page size:

40.9 KB

Response time:

0.140sec.

IP:

76.76.21.21

Response headers:

accept-ranges:	bytes
access-control-allow-origin:	*
age:	243961
cache-control:	public, max-age=0, must-revalidate
content-disposition:	inline
content-length:	41840
content-type:	text/html; charset=utf-8
date:	Tue, 01 Oct 2024 16:13:17 GMT
etag:	"ac82f3998f97fe0f18baf62fe83decd2"
referrer-policy:	strict-origin-when-cross-origin
server:	Vercel
strict-transport-security:	max-age=63072000
x-matched-path:	/
x-vercel-cache:	HIT
x-vercel-id:	fra1::vw7kq-1727799197287-4521fa697c96
connection:	close

DNS records:

A	address	76.76.21.21
A	ttl	3600
MX	exchange	alt1.aspmx.l.google.com
MX	priority	10
MX	exchange	alt2.aspmx.l.google.com
MX	priority	10
MX	exchange	aspmx.l.google.com
MX	priority	10
MX	exchange	aspmx2.googlemail.com
MX	priority	10
MX	exchange	aspmx3.googlemail.com
MX	priority	10
NS	value	ns-cloud-b4.googledomains.com
NS	value	ns-cloud-b2.googledomains.com
NS	value	ns-cloud-b1.googledomains.com
NS	value	ns-cloud-b3.googledomains.com
TXT	entries	firebase=pagoda-oboarding-dev
TXT	entries	airtable-verification=791df4e56c51602a6455772c164502e1
TXT	entries	knowbe4-site-verification=d12beda41529af4f156c57cd5cb851f5
TXT	entries	atlassian-domain-verification=lJhJEaavNaAd7TO764wCu4sGUx3xEXIjd4dMLNzWiq1wpmJypabadKoA2E8lp7rD
TXT	entries	docusign=c9682d28-029c-4732-91af-79ff89ce583b
TXT	entries	v=spf1 include:_spf.google.com include:_spf.firebasemail.com -all
TXT	entries	ZOOM_verify_nyqc71LEk3M7osSupR2iAg
TXT	entries	google-site-verification=6ffovOmHVTm-4vkK5dLfrB7tF9zBPv-RzTwI53FLazU
TXT	entries	11705AE39E
TXT	entries	MS=ms58296365
TXT	entries	miro-verification=0b44ddf2b3b7680dad19996edf6684f5f1701ea8
TXT	entries	firebase=near-fastauth-prod
SOA	nsname	ns-cloud-b1.googledomains.com
	hostmaster	cloud-dns-hostmaster.google.com
	serial	453
	refresh	21600
	retry	3600
	expire	259200
	minttl	300

SEO headers

h1 Blockchains, Abstracted.

h2 There's a better way to build.

h2 Web3 development made easy

h2 Greater discoverability. Easier onboarding.

h2 Be part of a global open source community.

h2 Learn, connect, & collaborate.

How to solve problems with near.org

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