akardam.net network radio tools & info contact akardam.net homepage
the network

About the Network

We at akardam.net like to build things that people may find useful, and provide them for free. This requires some infrastructure. We believe the best way to excercise control over one's infrastructure is to own it and run it yourself - the "cloud" is very popular these days, but that term is just code for "someone else's computer". Doing it yourself is also a great way to learn - teach a man to fish, and all that.

This journey started many moons ago with a server in the garage on a DSL modem. Today, we operate an autonomous system, just one network of many that makes up the global internet. Pretty cool, eh? More information can be found in our PeeringDB entry

As alluded to above, we're always looking for ways to help the internet be a better place, so if you run a project that you think we may be interested in supporting, feel free to drop us a line

While we do run our own network, we're not an ISP, so please don't bother us with inquries or solicitations regarding such things as IP transit, colocation, general web & e-mail hosting, etc. (Those go 'ker-sploosh' right into the bit-bucket)


Is the network running?
 
akardam.net services status
 
The above page provides an overview of the status of services provided by the network, and is automatically updated on a regular basis. This page will indicate whether each group of services is okay, degraded, or completely offline. More information, including updates and resolution notes, may be made available on this page. This page is also used to advise of upcoming impacts to services (for example, due to planned maintenance).

For those who may be curious about the technical side: The status page is designed to be simple and resiliant, as it has one (and only one) job to do - tell you what's up (or not) with akardam.net. It uses no dynamic content mechanisms whatsoever, just plain old HTML, and is independent of all core akardam.net services.

Further, there is no secure/encrypted version of the status page, because there is nothing sensitive about the information made publicly available there, and HTTPS adds another layer of complexity that (no matter how unlikely) could break (and of course, according to Murphy, at the worst possible time). We know some browsers or browser extensions go to great lengths to enforce the use of HTTPS, and we sympathise with any users for which this makes accessing the status page more difficult, but on the other hand we cannot be responsible for the way those browsers or extensions are designed to operate.