Is 1.fm down or not working?

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

Add comment

What to do if the site 1.fm is not available? Try our guide.

1.fm outage reports in the last 24 hours

1.fm - 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:

1.FM - Online internet radio | The music starts here!

Main page description:

Free Online Radio, Listen to your favorite music genres like Chillout, Trance, Dance, 80s, 90s, 60s, dubstep, psytrance, techno and much more

Protocol:

https

Status code:

200

Page size:

14.2 KB

Response time:

0.629sec.

IP:

185.33.21.21

Response headers:

server:	nginx/1.8.1
date:	Sun, 12 May 2024 19:43:19 GMT
content-type:	text/html; charset=utf-8
content-length:	14511
connection:	close
vary:	Accept-Encoding, Accept-Encoding
x-powered-by:	Express
etag:	"-1645887492"
set-cookie:	newone.sid=s%3AKl7LkVtjZfh918pCIco01rMmsjgzQS0_.vXcjUuNN7GKxcCXncHZWFUpmm07erJ%2BFIwantHRuaSg; Path=/; Expires=Fri, 08 Nov 2024 19:43:19 GMT; HttpOnly
access-control-allow-origin:	*
access-control-allow-credentials:	true
access-control-allow-methods:	GET, POST, OPTIONS
access-control-allow-headers:	DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type

DNS records:

A	address	185.33.21.21
A	ttl	300
MX	exchange	mail.1.fm
MX	priority	10
NS	value	ns2.techli.li
NS	value	ns1.techli.li
TXT	entries	google-site-verification=EHcivU9-DU6y1HpTUaNJgo61I3KWKzemuhemFBsCP6I
TXT	entries	v=spf1 a mx a:help.1.fm a:newsletter.1.fm include:_spf.google.com ?all
TXT	entries	j2h2xnw5n2jgst0kyxmlsygvwfc9ttp3
SOA	nsname	ns1.techli.li
	hostmaster	help.1.fm
	serial	348658788
	refresh	1200
	retry	600
	expire	604800
	minttl	10800

SEO headers

h1 Privacy Notice

h3 {{curretstfullname | uppercase}} STATION

How to solve problems with 1.fm

Errors on the 1.fm 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 1.fm on your own.