Is reaper.fm down or not working?

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

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

reaper.fm outage reports in the last 24 hours

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

Technical information

Main page title:
REAPER | Audio Production Without Limits
Protocol:
http
Status code:
200
Page size:
22.2 KB
Response time:
0.301sec.
IP:
174.129.249.41
Response headers:
date: Tue, 01 Oct 2024 12:22:33 GMT
server: Apache/2.4.7 (Ubuntu)
x-powered-by: PHP/5.5.9-1ubuntu4.26
vary: Accept-Encoding
connection: close
transfer-encoding: chunked
content-type: text/html
DNS records:
A address174.129.249.41
ttl10800
MX exchangeASPMX2.GOOGLEMAIL.com
priority30
MX exchangeASPMX5.GOOGLEMAIL.com
priority30
MX exchangeALT1.ASPMX.L.GOOGLE.com
priority20
MX exchangeASPMX4.GOOGLEMAIL.com
priority30
MX exchangeALT2.ASPMX.L.GOOGLE.com
priority20
MX exchangeASPMX.L.GOOGLE.com
priority10
MX exchangeASPMX3.GOOGLEMAIL.com
priority30
NS valuens3.cockos.com
NS valuens1.cockos.com
NS valuens2.cockos.com
TXT entriesv=spf1 ip4:174.129.249.41 ip4:50.17.184.175 ip4:50.19.254.66 include:_spf.google.com ~all
SOA nsnamens1.cockos.com
hostmasterroot.ns1.cockos.com
serial2023030601
refresh10800
retry3600
expire604800
minttl3600

How to solve problems with reaper.fm

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