Is public.app down or not working?

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

What to do if the site public.app is not available? Try our guide.

public.app outage reports in the last 24 hours

public.app - 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:
Public App - local news videos
Main page description:
View latest news videos in your language with Public App in less than 2 minutes, related to business, sports, Politics, Crime, Bollywood and technology in India and around the world.
Main page keywords:
news, today news, latest news, news online, breaking news, local news, लोकल न्यूज, सिटी न्यूज, pablic ap news, pablic, pablik
Protocol:
https
Status code:
200
Page size:
77.0 KB
Response time:
0.547sec.
IP:
65.9.95.97
Response headers:
content-type: text/html; charset=utf-8
content-length: 78877
connection: close
cache-control: private, max-age=0
date: Thu, 03 Oct 2024 09:43:13 GMT
via: 1.1 google, 1.1 644a5a573cbbd5ac03f5c40fa8642914.cloudfront.net (CloudFront)
vary: Accept-Encoding
x-cache: Miss from cloudfront
x-amz-cf-pop: AMS58-P3
x-amz-cf-id: t33RBzUaxZ2h6-Jix054_PeOy3lvoNDTrytfwGEsfezPNTILEbKU3w==
DNS records:
A address18.239.50.15
ttl60
A address18.239.50.105
ttl60
A address18.239.50.112
ttl60
A address18.239.50.93
ttl60
MX exchangealt1.aspmx.l.google.com
priority5
MX exchangealt4.aspmx.l.google.com
priority10
MX exchangealt3.aspmx.l.google.com
priority10
MX exchangeaspmx.l.google.com
priority1
MX exchangealt2.aspmx.l.google.com
priority5
NS valuens-579.awsdns-08.net
NS valuens-1942.awsdns-50.co.uk
NS valuens-1486.awsdns-57.org
NS valuens-430.awsdns-53.com
TXT entriesgoogle-site-verification=RhgspGruyUvX7ZKodlJTLN3lPDg8mpIAeJsR86gN0CA
TXT entriesfacebook-domain-verification=rfj6g3pnved7c2xrzcckh7a6evbmaf
TXT entrieszoho-verification=zb57231941.zmverify.zoho.com
TXT entriesgoogle-site-verification=F7T_b_WwC0HtVrgdZoZkkkh0fg6bcTbSytrCy6QuCPY
TXT entriesMS=ms28860721
TXT entriesv=spf1 include:_spf.google.com ~all
SOA nsnamens-1486.awsdns-57.org
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

How to solve problems with public.app

Errors on the public.app 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 public.app on your own.