Is GOV down?
gov.uk · Reference
GOV has recorded 100.0% uptime over the last 2 days, with no outage. It answers our checks in 203 ms on average.
No problems detected
GOV answered our last automated check normally, 7 minutes ago. If it is not working for you, the problem is most likely local - Your connection, your DNS resolver, a cached page, or an extension.
GOV problem reports in the last 24 hours
Counted in 15-minute buckets from reports submitted on this site. This is a user signal - A tall bar means people are complaining, not that our check failed.
No reports in the last 24 hours.
If GOV is not working for you, tell us and the chart starts here.
Response time from our automated checks
The last 24 checks of https://www.gov.uk/ from our network. Bar height is the response time; the tallest bar is the slowest.
- Answered normally
- Slow to answer
- No usable answer
Having a problem with GOV?
Tell us what is not working. Reports go straight onto the 24-hour chart above and help other people see a problem before any company admits to one. 0 reports in the last 24 hours.
About GOV outages
GOV sits at number 67 on the worldwide traffic ranking with about 61.3M organic visits a month, and the address it resolves to belongs to Fastly, Inc. GOV publishes 12 addresses for the name, reachable over IPv6 as well as IPv4, and the responding server reports itself as nginx.
Gov.uk signs its zone with DNSSEC and sends an HSTS header, so browsers refuse it over plain HTTP. The certificate gov.uk presented to us was issued by GlobalSign nv-sa, covering 13 names, with 90 days left on it at first check, and negotiated over TLSv1.3. Our first check of gov.uk returned HTTP 200 in 84 ms, of which 2 ms was name resolution and 1 ms the connection. The request to gov.uk passed through 1 redirect before it settled on https://www.gov.uk/. Those figures are the baseline this page measures gov.uk against from now on, every 20 minutes.
What to do if GOV is not working for you
Is it them or you?
Our last check reached gov.uk normally, from a different network, resolver and route than yours. If it is broken for you, the fault is most likely local or too narrow for a single probe to see. Our next automated check runs within 20 minutes and this page updates with it.
The first thing worth trying
Try a search-engine cached copy. Reference content changes slowly, so a cached version is usually just as good for what you needed.
How reference services typically fail
Pages load from cache while anything dynamic - search, editing, the API - fails. Because so much of these sites is cacheable, partial availability is the normal presentation. The rest of the steps, and why this category breaks the way it does, are on our reference status page, with more background in how we record outage history.
The link below unfurls into a live card showing the verdict, so whoever you send it to sees the evidence rather than your word for it.
Put a live badge on your own site
An SVG that always shows GOV’s current state, updated from our checks. Works in a README, a status dashboard or a footer.
Free, no account, and it will keep working. We ask nothing in return beyond the link back.
GOV measured against its peers
How it compares with other reference services
Over the last 30 days GOV ranks 2 of 3 reference services we monitor, measured on recorded uptime. The category averages 100.0%, and GOV sits at 100.0%. The steadiest in this group is NAMU.
On speed, GOV answers our checks in about 203 ms against a category average of 191 ms - Slower than its peers. Response time is not availability, but a service drifting well above its own normal is often the first sign of trouble.
What the last 24 checks looked like
Across the most recent 24 checks, the quickest response was 70 ms and the slowest 692 ms, against a 30-day average of 203 ms. The chart above plots each one, so a widening spread is visible before it becomes an outage.
All figures are our own measurements, taken every 20 minutes from one network. What that can and cannot see is set out in the methodology, and every reference service is listed on the category page.
The server that answered Mostly hidden
- IP address
- 199.232.88.144 and 1 other
- Server
- Hidden until you sign in
- Powered by
- Hidden until you sign in
- Content type
- Hidden until you sign in
- Declared size
- Hidden until you sign in
- Transport and HSTS
- Hidden until you sign in
Five more fields about the server behind gov.uk.
Free, one click with Google, and nothing is posted or shared. We ask because the lookups behind this cost us real requests to other people’s servers.
Read from our last sweep of gov.uk, not requested when you opened this page.
Certificate Mostly hidden
- Status
- Valid
- Issued to
- Hidden until you sign in
- Issued by
- Hidden until you sign in
- Valid from
- Hidden until you sign in
- Expires
- Hidden until you sign in
- Protocol and cipher
- Hidden until you sign in
Who issued it, what it covers and exactly when it expires.
Free, one click with Google, and nothing is posted or shared. We ask because the lookups behind this cost us real requests to other people’s servers.
An expired certificate stops browsers loading a site entirely while the server itself stays perfectly healthy, which is why we track it beside the uptime figure.
.GOV status: Common questions
Is GOV down right now?
GOV is up and responding normally. This page is refreshed by an automated check that runs every 20 minutes from an independent network, and by reports from visitors.
Why can I not reach GOV when you say it is up?
Because an outage can be partial. Our check runs from one network and asks for one page. Your problem may be regional, may affect only the mobile app, or may be local to your connection, DNS resolver or browser cache.
How reliable is GOV?
GOV has been reachable for 100.0% of the last 2 days we have measured, with 0 seconds of recorded downtime.
Does GOV have an official status page?
GOV does not publish a public status page, which is why independent monitoring and user reports are the only external signal available during an incident.
GOV discussion
Useful comments say what broke, roughly where you are and roughly when it started - That is what turns a pile of complaints into something other people can act on. Links are shown as plain text and carry no SEO value, so there is nothing here worth spamming.