I Deployed a Blog on a Raspberry Pi in a Moving Car – Here’s the Uptime Graph

I Deployed a Blog on a Raspberry Pi in a Moving Car – Here’s the Uptime Graph

By Ebuka Onah

Most people think hosting is something that belongs in a data center. Stable power, fiber internet, climate control—the usual assumptions.

So I decided to break that assumption completely: I hosted a live blog on a Raspberry Pi running inside a moving car.

If your infrastructure only works when conditions are perfect, it is not infrastructure—it is a demo.

The Goal of the Experiment

I didn’t want “best case performance.” I wanted chaos:

  • Mobile network switching
  • Power fluctuations
  • Physical vibration
  • Unstable latency zones

In short: real-world edge computing conditions.

Hardware Setup

  • Raspberry Pi 4 (8GB)
  • Portable 10,000mAh power bank
  • LTE router (SIM-based internet)
  • NGINX web server
  • Uptime monitoring script

Nothing exotic. Just deliberately minimal infrastructure.

System Architecture

Mobile Device (Car)
      ↓
LTE Router (SIM Network)
      ↓
Raspberry Pi (NGINX Server)
      ↓
Static Blog (HTML + Markdown)
      ↓
Uptime Monitor Logs

No cloud fallback. No redundancy. Just raw exposure.

What Actually Happened on the Road

The first 10 minutes were stable. Then reality kicked in.

  • Network latency spiked at intersections
  • Cell tower switching caused brief downtime
  • Power bank voltage dips triggered micro-restarts
  • CPU throttling increased under heat exposure
The system didn’t fail all at once. It degraded in layers.

Uptime Behavior (Real Pattern)

Instead of a clean uptime curve, I got this pattern: 

Uptime (%)
100 ────────╮
            │  stable highway segment
 95 ───────╯╲____
                ╲  intermittent drops (city zones)
 85 ─────────────╲___
                    ╲___ brief outages (network switching)

The interesting part wasn’t downtime—it was predictability of failure zones.

Key Insight: Mobility Breaks Assumptions

Traditional servers assume:

  • Stable IP
  • Stable power
  • Stable network path

A moving system breaks all three assumptions at once.

Edge computing is not about speed. It is about surviving instability.

Unexpected Observations

  • City traffic created worse uptime than highways
  • 5G was not consistently better than 4G due to switching overhead
  • Thermal throttling correlated with signal instability
  • Static content recovered faster than dynamic endpoints

What Failed First

  • Auto-reconnect scripts during network switching
  • Session persistence under IP changes
  • DNS resolution caching under roaming conditions

The weakest layer was not hardware—it was network expectation logic.

What Actually Worked

  • NGINX static file serving
  • Local caching
  • Lightweight HTML blog rendering
  • Simple uptime logging script
The simpler the system, the more resilient it became.

What This Means for Real Infrastructure

This experiment reflects real-world constraints in:

  • Rural connectivity systems
  • Vehicle-based IoT platforms
  • Mobile healthcare systems
  • Field data collection tools

The “internet” is not a fixed environment. It is a moving one.

Final Insight

Hosting a blog in a moving car sounds like a stunt, but it exposes a deeper truth about modern systems.

Most software is not designed for movement—it is designed for stillness.

The future of computing is not just cloud or edge. It is mobility-aware infrastructure.