HTTP/1.1 200 OK Date: Wed, 09 Feb 2022 10:58:58 GMT Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16 Strict-Transport-Security: max-age=63072000; includeSubDomains; preload X-Content-Type-Options: nosniff Vary: Accept-Encoding X-Powered-By: Article Publisher (http://www.arsidian.com/) - 000000-000000 Set-Cookie: articles-visitor=h6t6cvv1tm39u252qcslm5p2m7; path=/ Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Set-Cookie: VisID=719187; expires=Sat, 04-Feb-2023 10:58:58 GMT; path=// Transfer-Encoding: chunked Content-Type: text/html; charset=utf-8
The DNS is up. We have tried pinging Sonet.uz. There are no DNS Issues detected!
We have tried pinging Sonet.uz using our servers in diverse locations and the server response showed there are no current Sonet.uz problems today.
If Sonet.uz is down for you too there is nothing you can do except waiting. Probably the server is overloaded, down or unreachable because of a network problem, outage or website maintenance is in progress.
If the site is UP for us but you cannot access it, try one of our following solutions:
To solve Browser related issues that might make the site/server down for you, do a full Browser refresh of this site. You can do this by holding down CTRL + F5 keys at the same time on your browser.
This trick works perfectly on Chrome, Firefox, Brave, Opera, Safari and whatever default browser comes with your Windows nowadays lol.
The contents of all modern sites and apps today are usually cached. This means a copy is stored in your browser as long as you have visited that page before. This is to make it easier to access when next you visit that page. This might be a problem especially if the page was down last time you checked.
You might need to clear that out of your browser memory for the site to load properly.
Domain Name System (DNS) is what allows a site IP address (192.168.x.x) to be identified with words ( e.g .com, .us) in order to be remembered easily. This is usually provided by your Internet Service Provider.
To fix this, clear your local DNS cache to make sure that you grab the most recent cache that your ISP has.
Still having issues? Try sending your complaints or troubleshooting issues to the channels below: