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
James Barnes
Share this
More from StatusCake
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
James Barnes
March 25, 2026
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026
Buy vs Build in the Age of AI (Part 2)
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
James Barnes
March 11, 2026
Buy vs Build in the Age of AI (Part 1)
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
James Barnes
March 4, 2026
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026