Stratospheric Cell Service and the Rupiah: Ordinary Phones, Disaster Continuity, and the Archipelago Operating Ledger

Rupiah Stability Watch · 2026-10-03

The signal

Sceye and SoftBank have moved high-altitude platform service from a concept slide into a serious field test. In September 2026, Sceye said its Service Test 1 mission flew more than 15,000 km from New Mexico to Japan in the stratosphere over 13 days, then demonstrated mobile broadband to unmodified devices through SoftBank’s core network, edge computing, and communications with drones.[^sceye-softbank] SoftBank’s own release said the trial confirmed voice calls, emergency calls, text messaging, high-capacity data services such as video streaming and video calls, and an emergency alert messaging system designed for large-scale disasters.[^softbank]

New Atlas’ account gives the plain-language importance: this was a cell tower in the sky reaching ordinary phones from around the stratospheric layer, not a service requiring each user to carry a special satellite terminal.[^newatlas] Sceye later said the round trip lasted 30 days, covered nearly 30,000 km, and included about a week operating over Japan.[^sceye-return]

That is the rupiah-relevant fact. Not the novelty of an airship. Not a near-term USD/IDR forecast. The meaningful question is whether Indonesia can keep more of its operating ledger visible during flood, quake, haze, wet-season, and island-logistics disruption.

What this did not prove

The test should not be inflated into commercial readiness.

SoftBank described communications trials with “limited durations, areas and devices,” while working toward HAPS services from 2027 onward.[^softbank] That matters. A trial over a target area off Cape Muroto, with a cooperating mobile operator and controlled test objectives, is not the same thing as an Indonesian archipelago service that works through monsoon weather, aviation permissions, spectrum coordination, maintenance cycles, emergency congestion, cyber incident response, and local public-service workflows.

The evidence supports four narrower claims:

• A HAPS platform can be positioned in the stratosphere after a long trans-Pacific flight.
• It can connect ordinary smartphones through an operator core network in a trial setting.
• It can support emergency-alert and drone-communications scenarios.
• It can carry some network and compute functions closer to the user, reducing dependence on distant routing in the tested configuration.

It does not yet prove:

• Indonesia-scale economics.
• Reliable degraded-mode operation through repeated disasters.
• Local maintainability.
• Affordable public-service contracts in rupiah.
• Auditability of the control stack.
• A substitute for terrestrial towers, fiber, radio, satellite backhaul, community sirens, and public drills.

For Rupiah Stability Watch, that distinction is the whole point. A technology can be impressive and still be financially fragile if the country buys visibility it cannot inspect, repair, price, or govern.

Where it fits beside satellites and towers

Our earlier piece, “Satellite Infrastructure and the Rupiah: Launch Capacity, Archipelago Operations, and the Confidence Ledger,” treated satellite capacity as part of Indonesia’s operating infrastructure: useful when it connects schools, clinics, local offices, and remote islands, but not a currency shield by itself. HAPS sits in a different layer.

A simplified map looks like this:

Indonesia already has a satellite-connectivity agenda. ANTARA reported that SATRIA-1 was serving 31,803 public service locations by early June 2026, including 21,718 schools, 6,353 government offices, 1,880 health-care centers, 528 defense and security facilities, and other public sites.[^antara-equal] Another ANTARA report said 30,000 public-service points had been connected to SATRIA-1 receivers by December 2025, with up to 10 Mbps at each location and most sites in education, government, and health.[^antara-bakti]

That is not replaced by stratospheric direct-to-phone service. It is complemented by it. SATRIA-1 is better understood as institutional connectivity: schools, clinics, offices, ground stations, and fixed service points. HAPS direct-to-phone would be a continuity layer for moving people, moving vehicles, emergency queues, temporary shelters, fishing routes, ferry corridors, tourist areas, and neighborhoods where the tower is down but the handset remains.

The rupiah channel: fewer invisible days

A currency does not weaken only because of a chart. It weakens when households, firms, local governments, and outside capital cannot see whether the operating system still works.

Indonesia’s disaster exposure makes that visibility practical, not abstract. BNPB reported 1,730 disasters between January 1 and September 7, 2026, including 543 floods, 324 extreme-weather events, 105 landslides, 101 drought cases, 13 major earthquakes, and three volcanic eruptions. The same report cited 111,533 homes affected and damage to educational, medical, office, worship, and bridge infrastructure.[^bnpb]

In that setting, ordinary-phone continuity can become rupiah-relevant through several channels.

1. Warnings become actionable, not merely issued

“One More Day of Warning: AI Weather Forecasting, Port Readiness, and Rupiah Climate-Risk Transmission” argued that forecast value depends on whether the warning reaches the people who can change behavior. HAPS direct-to-phone would not make BMKG warnings better by itself. It could make warning delivery less brittle when terrestrial networks fail.

The test’s emergency-alert component is therefore more important than the video-call demonstration. If a coastal district, ferry operator, port office, SPPG kitchen, clinic, and tourist zone can all receive the same official degraded-mode message, rumor has less room to set prices, hoard fuel, cancel trips, or freeze local trade.

2. Payments and records stay closer to current reality

A rupiah operating ledger is partly a ledger in the literal sense. QR payments, aid lists, kitchen delivery records, clinic referrals, port manifests, ferry manifests, fuel dispatches, and village-office records all depend on communications being available enough to keep timestamps and status updates credible.

If ordinary phones continue to work during local tower outages, the gain is not convenience. It is that fewer records go dark at the exact moment when public money, emergency supplies, and household liquidity are under stress.

This connects directly to “Contestable Records and the Rupiah” and the weekly monitor’s operating-guarantee test: public confidence improves when records can be checked, corrected, and reconciled quickly. A dark ledger forces later reconstruction. Reconstruction is where leakage, rumor, and dispute become expensive.

3. Ports, ferries, clinics, kitchens, and tourism can degrade more gracefully

“Wet-Season Operating Ledger,” “GNSS Integrity and the Rupiah,” and the Flores/Banda–Timor work all point to the same mechanism: Indonesia’s archipelago economy loses confidence when local disruptions become unknowable.

A direct-to-phone stratospheric layer could help keep degraded-mode status visible:

• ferry delay and routing notices;
• port queue and berth updates;
• clinic referral and stock messages;
• MBG/SPPG kitchen operating status;
• fuel-truck and emergency-generator dispatch;
• tourist-area evacuation and reopening notices;
• BPBD field updates that do not wait for a damaged terrestrial backhaul route.

This is not a heroic story of technology “saving” the rupiah. It is the smaller, more plausible story: fewer hours of confusion, fewer duplicate trips, less emergency fuel waste, less rumor-based cancellation, and a faster return from emergency mode to normal commerce.

The external-balance risk

The same technology can weaken the ledger if Indonesia buys it badly.

The liabilities are clear:

• Imported platforms and payloads may mean large hard-currency procurement.
• Service contracts may be priced in dollars or yen while public benefits arrive in rupiah.
• Insurance, replacement, spares, helium or lifting-gas logistics, control systems, and specialist maintenance may sit offshore.
• Spectrum and aviation approvals may be technically domestic but operationally shaped by foreign platform constraints.
• Cyber and control risks are harder to audit if the flight system, radio stack, network functions, and edge-compute layer are proprietary.
• Public-service SLAs may hide the one number that matters: whether the system works during an Indonesian disaster, not during a vendor demonstration.

This is why the predecessor satellite piece matters. Imported resilience can still be resilience. But it becomes rupiah-positive only when it reduces disrupted days more than it adds foreign-currency obligations, operational opacity, and repair dependence.

The Indonesia watchlist

The practical test is not whether Indonesia announces a HAPS partnership. Announcements are cheap. The watchlist should be operational.

Pilot design

Look for pilots involving Komdigi/BAKTI, BNPB, BMKG, BPBD, mobile operators, ferry/port authorities, and district governments. A telecom-only pilot is too narrow. A rupiah-relevant pilot should test warnings, public-service records, payments, and logistics status under degraded conditions.

Ordinary-phone proof

The pilot should publish whether unmodified phones worked across realistic Indonesian conditions: indoors, under trees, in shelters, near hills, along coastlines, on ferries, and during network congestion. The Sceye/SoftBank demonstration is useful precisely because it centered ordinary devices; Indonesia should preserve that discipline.

Outage minutes avoided

The core metric is not peak speed. It is outage minutes avoided for specific public functions:

• official alerts delivered;
• emergency calls completed;
• QR/payment fallback continuity;
• BPBD field reports submitted;
• clinic referral messages delivered;
• kitchen, port, ferry, and fuel status records updated.

Contract currency and local capability

Ask what is denominated in rupiah, what is denominated in foreign currency, and what Indonesia can maintain locally. If every meaningful repair, software update, spares decision, and mission-planning change requires offshore approval, the service may buy continuity at the cost of dependence.

Incident reporting

The public should see a simple incident register: outages, interference, failed alerts, cyber events, aviation constraints, aborted flights, latency under load, and post-disaster drill results. A resilience system without incident reporting is a confidence instrument with no confidence record.

The least-harm path

The least-harm path is not to reject stratospheric service because it is foreign, nor to adopt it because it is new.

It is to treat HAPS direct-to-phone as a bounded disaster-continuity experiment:

1. Test it first in one or two high-risk corridors, such as a quake/tsunami-exposed coastal area and a wet-season island-logistics corridor.
2. Require ordinary-phone performance metrics, not only institutional-terminal metrics.
3. Tie the pilot to BMKG/BNPB/BPBD workflows and mobile-operator networks from the beginning.
4. Publish public-service continuity measures: alerts, calls, payment fallback, clinic/kitchen/port/ferry status updates.
5. Disclose contract currency, local maintenance obligations, data/control audit arrangements, and incident reporting.
6. Keep terrestrial towers, radio, satellite backhaul, community warning systems, and local drills as the base layer.

The rupiah test is blunt: does the technology make Indonesia’s operating ledger more visible during disruption, in a way Indonesia can afford, inspect, and sustain?

If yes, stratospheric cell service belongs in the same family as weather-warning readiness, GNSS integrity, distributed batteries, and SATRIA-1: not currency defenses, but operating guarantees that reduce uncertainty. If no, it is another imported platform whose resilience value is smaller than its dependency bill.

What I am uncertain about

The most important uncertainty is cost. The public sources show a strong technical demonstration, but not Indonesian procurement economics, contract currency, insurance, maintenance, or lifecycle cost.

The second uncertainty is Indonesian regulatory fit. HAPS service would cross telecom, spectrum, aviation, disaster-management, cybersecurity, and possibly defense governance. A system that takes too long to authorize in an emergency is not an emergency system.

The third uncertainty is congestion behavior. A disaster does not create a neat test load. It creates thousands or millions of people trying to call, message, pay, verify, and leave at once.

The fourth uncertainty is whether public agencies would use the layer for record continuity, not just alerts. The larger rupiah benefit comes from keeping the ledger current: who needs help, which kitchen is operating, which ferry is moving, which clinic has capacity, which road or port is open.

That is where the Sceye/SoftBank signal becomes useful for Indonesia. It is not a promise that airships defend the rupiah. It is a prompt to ask a sharper question: when the ground network is broken, can ordinary phones still keep the public ledger alive?

[^newatlas]: Omar Kardoudi, New Atlas, “Sceye's cell tower in the sky beams mobile service from the stratosphere,” October 2, 2026. [^sceye-softbank]: Sceye, “Sceye and SoftBank Corp. Complete Stratospheric Connectivity Demonstration in Japan, Advancing Towards HAPS Commercialization,” September 1/2, 2026. [^softbank]: SoftBank Corp., “SoftBank Corp. Achieves Japan’s First HAPS Trial Service in Preparation for Commercialization,” September 2, 2026. [^sceye-return]: Sceye, “Sceye’s Stratospheric Platform Re-enters United States After Record-Breaking Roundtrip Stratospheric Flight Between U.S. and Japan,” September 9, 2026. [^antara-bakti]: ANTARA News, “BAKTI connects 30,000 public services points via SATRIA-1,” December 10, 2025. [^antara-equal]: ANTARA News, “Expanding equal development through digital space,” June 27, 2026. [^bnpb]: ANTARA News, “BNPB reports 1,730 natural disasters across Indonesia in 2026,” September 8, 2026.