Are you having issues? Provide feedback to Akwam by selecting the option you are having issues with.
HTTP/2 200 date: Wed, 09 Feb 2022 19:54:54 GMT content-type: text/html cache-control: max-age=0, no-cache, no-store, must-revalidate expires: Wed, 11 Jan 1984 05:00:00 GMT vary: Accept-Encoding,Accept-Encoding x-powered-by: O2 CMS/v 5.0 pragma: no-cache x-turbo-charged-by: LiteSpeed cf-cache-status: DYNAMIC expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=V%2B49IQNW%2FddWJdBqCR8UOYcKS%2B4gD4mMvZ3SVY3I%2BqeBo9LcgnuSAfxrVEicFpFaWW5s0cRAxW7NYPP1D7jRqpweoIjWalbzl7FIEIrj%2Fl8QYZrGAk2mIUUEf5h7FGRThGV2UDYA9w%3D%3D"}],"group":"cf-nel","max_age":604800} nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800} strict-transport-security: max-age=2592000; includeSubDomains; preload x-content-type-options: nosniff server: cloudflare cf-ray: 6dafa6faec01196c-EWR alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
The DNS is up. We have tried pinging Akwam.io. There are no DNS Issues detected!
Type | Name | Value | Class | TTL |
A | akwam.io | 172.67.173.46 | IN | 300 |
A | akwam.io | 104.21.30.149 | IN | 300 |
NS | akwam.io | IN | 86400 | |
NS | akwam.io | IN | 86400 |
We have tried pinging Akwam.io using our servers and the Akwam.io server responded on time, indicating that there are no current Akwam.io problems today.
If Akwam.io is down for you too, the server might be overloaded or unreachable because of network problems, outages or a website maintenance is in progress.
If Akwam.io is UP for us but you cannot access it, try these solutions:
ar