How do Github Pages fare for serving static files?

Question

I have a site that is composed only of static files.

I just discovered how easy it is to host websites directly off Github. Any idea how do they fare in terms of latency, reliability, capacity...?

In general - for static content only at the moment - are they "production grade"? How do they compare to say Amazon S3 in terms of pure latency and uptime?

Answer 1

GitHub is indeed production ready. They use replication, clustering and load balancing to provide low latency and hight availability and I would say they are pretty good at doing that. You can have an idea about the latest issues by reading the status page.

However, they aren't a real hosting. Compared to Amazon S3, for example, Amazon provides the following advantages:

• An infrastructure about order of magnitude bigger
• Ability to use CDN (Amazon CloudFront) to reduce latency by serving the pages with the nearest node according to user's location

The advantages of using GitHub pages is normally for Ruby users that wants to use Jekyll (the tool behind GitHub pages) and wants to leave GitHub the effort to compile and host the site. Last but not least, it's free (as long as you keep your repository public).

But nothing prevents you to use Jekyll locally (or any other publishing tool), generate the pages statically and host them on Amazon. I'm doing this for several projects. There are several command line tools to sync your local copy with the Amazon folder.

Answer 2

As of 2018 GitHub Pages fully supports HTTPS, even for custom domains.

GitHub Pages also now uses a CDN, which is currently provided by Fastly.

So anything you host on GitHub Pages today will be secure, fast, and reliable.

Answer 3

This answer is obsolete => see Maximillian's answer

---

The big limitation is no end-to-end TLS/SSL support.

Pages are served over HTTP, not HTTPS, so you shouldn't use them for sensitive transactions, like sending passwords or credit card numbers.

-- https://help.github.com/articles/what-are-github-pages

https://foo.github.io does work, but is not entirely secure (excerpt from GitHub support reply, Feb 2014):

While HTTPS requests may appear to work, our CDN provider is adding and removing the encryption at their end, and then the request is transmitted over the open internet from our CDN provider to our GitHub Pages infrastructure, creating the appearance of trustability.

This is why we do not yet officially support HTTPS for GitHub Pages.

And there is no TLS/SSL support for custom domains at all [unofficial issue].

Many people have experimented with fronting HTTPS on a custom domain via e.g. Clouldflare. Clouldflare specifically isn't end-to-end secure ("Strict Full SSL" doesn't work here) but whatever you use in front, Github's own Pages–CDN link remains insecure as explained above.

Another small bug: some paths redirect back to http.