Is kooapp.com down or not working?

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

What to do if the site kooapp.com is not available? Try our guide.

kooapp.com outage reports in the last 24 hours

kooapp.com - 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:
Koo says goodbye
Main page description:
Koo was the world's second largest microblogging platform in multiple native languages.
Protocol:
https
Status code:
200
Page size:
358.6 KB
Response time:
0.341sec.
IP:
185.230.63.107
Response headers:
content-type: text/html; charset=UTF-8
link: <https://static.parastorage.com/>; rel=preconnect; crossorigin;,<https://static.parastorage.com/>; rel=preconnect;,<https://static.wixstatic.com/>; rel=preconnect; crossorigin;,<https://static.wixstatic.com/>; rel=preconnect;,<https://siteassets.parastorage.com>; rel=preconnect; crossorigin;,
html-cacheable: true
etag: W/"451f151b56ac4398081433a24b929773"
content-language: en
strict-transport-security: max-age=86400
x-wix-request-id: 1727762278.4655234272653820136
cache-control: public,max-age=0,must-revalidate
server: Pepyaka
x-content-type-options: nosniff
accept-ranges: bytes
age: 209129
date: Tue, 01 Oct 2024 05:57:58 GMT
x-served-by: cache-ams2100119-AMS
x-cache: MISS
vary: Accept-Encoding
server-timing: cache;desc=hit, varnish;desc=hit_miss, dc;desc=fastly_84_g
set-cookie: ssr-caching=cache#desc=hit#varnish=hit_miss#dc#desc=fastly_84_g; max-age=20
x-seen-by: yvSunuo/8ld62ehjr5B7kA==,WD1HRWp6HtwVKpzxLkVT7rxkNjrXdwdgtu6E0yACibU=,m0j2EEknGIVUW/liY8BLLnPGwo7BcC7ggvhmnBFvpa7JftmKrOReD3ukbbas4YDo,2d58ifebGbosy5xc+FRalvrhSEcFrcThErVNkk3OuihjMwiEOIh1S9Og/XoFIhnBeLul/h3JuQYan4apVlD2sA==,2UNV7KOq4oGjA5+PKsX47NAyUNYijOXLVpL50aLzshK8ZDY613cHYLbuhNMgAom1
transfer-encoding: chunked
via: 1.1 google
glb-x-seen-by: bS8wRlGzu0Hc+WrYuHB8QIg44yfcdCMJRkBoQ1h6Vjc=
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
connection: close
DNS records:
A address185.230.63.107
ttl3600
A address185.230.63.171
ttl3600
A address185.230.63.186
ttl3600
MX exchangealt4.aspmx.l.google.com
priority50
MX exchangealt3.aspmx.l.google.com
priority40
MX exchangeaspmx.l.google.com
priority10
MX exchangealt2.aspmx.l.google.com
priority30
MX exchangealt1.aspmx.l.google.com
priority20
NS valuens3.wixdns.net
NS valuens2.wixdns.net
TXT entriesv=spf1 include:_spf.google.com ~all
TXT entriesv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrBRQMEhgk60BW/oY56RVrD901hNBcBBnENtX2il2gYsAdo1h9q7XgLE9GOzR6efGzbxJIjs/4r2Yr4W+OihlAf2VgekjS373YajmjFTkVrjRbB5GJkNWONl2+lkLsbfn+6WUpbXGSnRm10D8+ljhlbfCIXHxnFn9VUlwX9utPxQIDAQAB
SOA nsnamens2.wixdns.net
hostmastersupport.wix.com
serial2024070310
refresh10800
retry3600
expire604800
minttl3600

How to solve problems with kooapp.com

Errors on the kooapp.com 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 kooapp.com on your own.