docs: update links

README.md

@@ -170,7 +170,7 @@ Default: `new Keyv({ namespace: 'ssr' })`
 
 The cache instance used for backed your pre-calculated server side response copies.
 
-The library delegates in [keyv](https://github.com/lukechilds/keyv), a tiny key value store with [multi adapter support](https://github.com/lukechilds/keyv#official-storage-adapters).
+The library delegates in [keyv](https://keyvhq.js.org/), a tiny key value store with [multi adapter support](https://keyvhq.js.org/#/?id=storage-adapters).
 
 If you don't specify it, a memory cache will be used.
 
@@ -297,7 +297,7 @@ If your server domain is connected with CloudFlare you can take advantage of hav
 
 ![](https://i.imgur.com/2BCHVzh.png)
 
-For doing that, you need to setup a `Page Rule` over your domain specifing you want to enable cache. [Read more how to do that](https://support.cloudflare.com/hc/en-us/articles/115000150272-How-do-I-use-Cache-Everything-with-Cloudflare-).
+For doing that, you need to setup a `Page Rule` over your domain specifing you want to enable cache. [Read more how to do that](https://web.archive.org/web/20190915000000*/https://support.cloudflare.com/hc/en-us/articles/115000150272-How-do-I-use-Cache-Everything-with-Cloudflare-).
 
 Next time you query about a resource, a new `cf-cache-status` appeared as part of your headers response.
 
@@ -310,7 +310,7 @@ x-cache-expired-at: 1h 59m 60s
 cf-cache-status: MISS
 ```
 
-CloudFlare will [respect your `cache-control` policy](https://support.cloudflare.com/hc/en-us/articles/202775670-How-Do-I-Tell-Cloudflare-What-to-Cache-), creating another caching layer reflected by `cf-cache-status`
+CloudFlare will [respect your `cache-control` policy](https://web.archive.org/web/20190323033009/https://support.cloudflare.com/hc/en-us/articles/202775670-How-Do-I-Tell-Cloudflare-What-to-Cache-), creating another caching layer reflected by `cf-cache-status`
 
 ```bash
 HTTP/2 200