Gaza: preserving connectivity and checking an internet outage

Preserve a connection that already works

If you can send a message, keep that connection available while preparing alternatives. Save essential contacts and information offline, and agree a short check-in plan with people you trust. A queued or undelivered message does not by itself establish what happened to the recipient or prove a territory-wide outage.

Follow local safety instructions. Do not move toward an unfamiliar hotspot, enter a damaged building, climb onto a roof or leave shelter solely to obtain reception. This guide does not identify safe travel routes or operating public hotspots.

Distinguish Wi-Fi, mobile service and internet

1. Wi-Fi connects but nothing loads: the local access point may be working while its upstream connection or power supply has failed. Compare a small, familiar service on another device already using the network.

2. Only one device fails: record its error and check whether it is using the intended network. Do not change a shared router to fix a single-device problem.

3. A SIM shows signal but data fails: check the plan, balance and provider’s instructions when possible. Signal bars do not guarantee an active data connection.

4. Several connections fail: preserve the observations and check a trusted provider or local organization’s update when available. Do not dismantle working equipment based on an assumed cause.

For a managed satellite connection, give the administrator the exact terminal model and error. Our satellite internet checklist helps separate local equipment observations from a service fault; it is not evidence of service availability in Gaza.

An eSIM or satellite device is not guaranteed access

An eSIM installs a mobile subscription; it does not itself create a satellite connection. Before paying for a plan, confirm the handset supports the required eSIM, the plan covers your intended location, a compatible network is reachable and the provider supports the intended use. Keep a working SIM profile unless the provider’s recovery instructions require a change. We have not verified an eSIM offer that will work for you.

Similarly, a satellite device needs a supported service, appropriate account and any necessary permissions. Do not assume that equipment used by an aid organization is available for household use, or that a roaming kit imported from elsewhere will activate. We have not established a generally available consumer Starlink service for Gaza. This guide does not recommend importing equipment or bypassing access restrictions.

Understand what humanitarian reports describe

Official Logistics Cluster meeting minutes from 18 June 2026 describe communications work in Gaza, including network support, fuel planning and barriers to obtaining equipment. They are a dated operational snapshot, not a current coverage map or an invitation to use a humanitarian facility.

If an organization already assists you, ask through its established local contact whether a communications or charging service is offered, who is eligible, and what current access arrangements apply. Do not assume a hospital, aid warehouse or coordination office provides public internet. Humanitarian staff should use their organization’s communications procedures and designated administrator.

Read the dated official communications update. Avoid treating a report about one operational site as proof of access elsewhere.

Make limited power and bandwidth count

Prioritize brief essential messages. Pause nonessential video, automatic media downloads and cloud synchronization. Save useful instructions in a format you can read offline. If sharing a connection, agree priorities with its operator rather than repeatedly running speed tests.

Use only the correct charger and supported power arrangement. Do not charge a wet or damaged device, use a swollen battery or attempt improvised wiring. On a shared installation, the router, modem and upstream equipment may have separate supplies; a phone charger cannot be assumed to support them. Ask the administrator before adding load or restarting a system.

Protect shared access: do not post passwords, terminal identifiers, account documents or precise installation locations publicly. For a technical fault, keep a private note of the model, message, time and safe checks completed. Our manual library links original equipment documentation.

Sources and limits

• Logistics Cluster: 18 June 2026 meeting minutes, including the ETC update, published 30 June 2026.

• WFP: what the Emergency Telecommunications Cluster does—general context, not local availability.

We have not verified an operating public access point, current local network coverage or an individual service offer. This English-language guide is not an emergency service or live outage feed. No purchase is needed. Report a correction.