Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021



According to the Wall Street Journal last week search engine behemoth Google has set its sights beyond the North American and European markets and is looking to Africa and South-east Asia.
One of the issues facing Google’s march into sub-Saharan Africa, and for the continent as a whole as it aims to get online, is infrastructure. Just as infrastructure projects such as building roads and bridges have long been been seen as a key driver of economic growth for traditional industries in developing countries, Google likewise sees building online infrastructure as important to drive the online economies of Africa
Google however is hoping to approach its network building in Africa differently. Faced by difficult terrain, a lack of traditional infrastructure and vast areas to cover laying fibre-optic cable simply won’t work. Instead the company aims to connect almost a million people to the Internet by offering them low-cost, low-power Android smartphones with the Internet being available to them through transmitters stowed on high-altitude blimps.
Using balloons and drones to send data is not a new idea, and for those involved in high-frequency share trading, where getting your trade in quicker than anyone else can be the difference between making and losing millions of dollars, the race to build a data super-highway in the sky is on.
Sending trades between New York and Chicago via traditional fibre optic cable takes around 14.5 milliseconds for the round-trip. Sending trades between the two cities via microwave beams through the air, a service offered by companies such as TradeWorx, takes just 8.5 milliseconds. The price for such gaining such a competitive advantage? Rumoured to be around $250,000 a year.
James Barnes, StatusCake.com
Share this
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
4 min read Why strong reviews, accountability, and monitoring matter more in an AI-assisted world Artificial intelligence has become the latest fault line in software development. For some teams, it’s an obvious productivity multiplier. For others, it’s viewed with suspicion. A source of low-quality code, unreviewable pull requests, and latent production risk. One concern we hear frequently goes

3 min read IPFS is a game-changer for decentralised storage and the future of the web, but it still requires active monitoring to ensure everything runs smoothly.
Find out everything you need to know in our new uptime monitoring whitepaper 2021