Prolixium dot com: News >> Blog >> Who hosts your cloud provider's status page?

I thought this was a little funny. Here are the links to a few of the top cloud providers' status pages:

https://status.ctl.io/ (CenturyLink)
https://status.aws.amazon.com/ (Amazon Web Services)
https://azure.microsoft.com/en-us/status/ (Microsoft Azure)
https://ocistatus.oraclecloud.com/ (Oracle Cloud)
https://status.cloud.google.com/ (Google Cloud)
https://status.linode.com/ (Linode)
https://status.vultr.com/ (Vultr)
https://status.apps.rackspace.com/ (Rackspace)

Now, here's who hosts the status page (courtesy of ipin, which is truly hideous Perl code that you should not read):

CenturyLink

(destiny:20:00:PDT)% ipin status.ctl.io.
  A record #1
4 Address: 172.217.6.211
4 PTR: lga25s54-in-f19.1e100.net.
4 PTR: lga25s54-in-f211.1e100.net.
4 Prefix: 172.217.6.0/24
4 Origin: AS15169 [GOOGLE - Google LLC, US]
  AAAA record #1
6 Address: 2607:f8b0:4006:804::2013
6 PTR: lga25s54-in-x13.1e100.net.
6 Prefix: 2607:f8b0:4006::/48
6 Origin: AS15169 [GOOGLE - Google LLC, US]

Amazon Web Services

(destiny:20:00:PDT)% ipin status.aws.amazon.com.
  A record #1
4 Address: 52.94.241.74
4 Prefix: 52.94.240.0/22
4 Origin: AS16509 [AMAZON-02 - Amazon.com, Inc., US]

Microsoft Azure

(destiny:20:01:PDT)% ipin azure.microsoft.com.  
  A record #1
4 Address: 13.82.93.245
4 Prefix: 13.64.0.0/11
4 Origin: AS8075 [MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US]

Oracle Cloud

(destiny:20:02:PDT)% ipin ocistatus.oraclecloud.com.
  A record #1
4 Address: 18.234.32.149
4 PTR: ec2-18-234-32-149.compute-1.amazonaws.com.
4 Prefix: 18.232.0.0/14
4 Origin: AS14618 [AMAZON-AES - Amazon.com, Inc., US]

Google Cloud

(destiny:20:02:PDT)% ipin status.cloud.google.com.  
  A record #1
4 Address: 172.217.6.206
4 PTR: lga25s54-in-f14.1e100.net.
4 PTR: lga25s54-in-f206.1e100.net.
4 Prefix: 172.217.6.0/24
4 Origin: AS15169 [GOOGLE - Google LLC, US]
  AAAA record #1
6 Address: 2607:f8b0:4006:804::200e
6 PTR: lga25s54-in-x0e.1e100.net.
6 Prefix: 2607:f8b0:4006::/48
6 Origin: AS15169 [GOOGLE - Google LLC, US]

Linode

(destiny:20:03:PDT)% ipin status.linode.com.      
  A record #1
4 Address: 18.234.32.150
4 PTR: ec2-18-234-32-150.compute-1.amazonaws.com.
4 Prefix: 18.232.0.0/14
4 Origin: AS14618 [AMAZON-AES - Amazon.com, Inc., US]

Vultr

(destiny:20:03:PDT)% ipin status.vultr.com. 
  A record #1
4 Address: 104.20.23.240
4 Prefix: 104.20.16.0/20
4 Origin: AS13335 [CLOUDFLARENET - Cloudflare, Inc., US]
  A record #2
4 Address: 104.20.22.240
4 Prefix: 104.20.16.0/20
4 Origin: AS13335 [CLOUDFLARENET - Cloudflare, Inc., US]
  AAAA record #1
6 Address: 2606:4700:10::6814:16f0
6 Prefix: 2606:4700:10::/44
6 Origin: AS13335 [CLOUDFLARENET - Cloudflare, Inc., US]
  AAAA record #2
6 Address: 2606:4700:10::6814:17f0
6 Prefix: 2606:4700:10::/44
6 Origin: AS13335 [CLOUDFLARENET - Cloudflare, Inc., US]

Rackspace

(destiny:20:04:PDT)% ipin status.apps.rackspace.com.
  A record #1
4 Address: 152.195.12.244
4 Prefix: 152.195.12.0/24
4 Origin: AS15133 [EDGECAST - MCI Communications Services, Inc. d/b/a Verizon Business, US]

I'm not gonna lie, I had a chuckle when I saw who hosted Oracle Cloud's status page. Other takeaways:

Everyone here uses HTTPS. That's nice.
Only Google, Vultr, and CenturyLink seem to care about providing IPv6 connectivity to their status pages.
Most cloud providers here seem to self-host except for CenturyLink (Google), Linode (AWS), Rackspace (Edgecast), and Oracle (AWS).
Vultr might be worried about DDoS so they use Cloudflare as a front-end.

Really, this isn't indicitive of anything. I'd probably host my status page elsewhere if I ran a hosting service, TBQH.