Are you having issues? Provide feedback to Premier by selecting the option you are having issues with.
HTTP/2 200 server: nginx/1.16.1 date: Wed, 09 Feb 2022 14:21:48 GMT content-type: text/html; charset=utf-8 content-length: 22063 last-modified: Tue, 08 Feb 2022 17:21:29 GMT etag: "6202a699-562f" expires: Wed, 09 Feb 2022 14:21:47 GMT cache-control: no-cache pragma: no-cache cache-control: no-store, no-cache, must-revalidate, post-check=0 pre-check=0 accept-ranges: bytes strict-transport-security: max-age=31536000 access-control-allow-credentials: true access-control-allow-headers: Accept,Authorization,Cache-Control,Content-Type,DNT,If-Modified-Since,Keep-Alive,Origin,User-Agent,X-Requested-With,X-Ally,cache,X-CSRFToken,Date,X-USER-PROFILE-ID,X-Region access-control-expose-headers: Date access-control-allow-methods: GET,POST,OPTIONS,PUT,DELETE,PATCH x-frame-options: DENY
The DNS is up. We have tried pinging Premier.one. There are no DNS Issues detected!
We have tried pinging Premier.one using our servers and the Premier.one server responded on time, indicating that there are no current Premier.one problems today.
If Premier.one 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 Premier.one is UP for us but you cannot access it, try these solutions: