Before choosing a maritime network, ask who handles the outage

The satellite link is only one part of a maritime connectivity order. Fieldbase's maritime connectivity page puts installation and ongoing support beside the connection. It is a supplier description, not an independent record of performance. Its useful starting point is a purchasing question: when the link fails, which part of the service takes over?

Three things to know

• A proposed backup connection, a monitoring team and a dispatched engineer are different parts of an arrangement.
• Fieldbase's support page lists a business-hours Standard tier despite its round-the-clock heading. Check the tier in the quotation.
• Ask for the route, configuration, escalation contacts and handover records, not a promise inferred from a webpage.

Name the connection and the fallback

Fieldbase's maritime connectivity page describes Starlink Maritime, traditional VSAT and a hybrid arrangement. It says the hybrid can switch traffic to VSAT when the Starlink link is unavailable or degraded. That is the company's description, not a failover result PING has observed. Do not treat a list of options as the configuration already installed on a particular vessel.

Ask the supplier to mark the intended operating route, primary connection, proposed fallback and applications expected to continue. Which equipment and subscription does each path require? What changes when the vessel moves beyond the assumptions in the proposal? Put the answers alongside the quoted configuration. This is a request for a clear design, not an invitation to interrupt a working vessel's systems.

Read the support tier beneath the headline

The NOC and field-support page separates remote troubleshooting from engineer dispatch. Its tiers also differ: Standard lists business-hours assistance, while Premium and Enterprise list round-the-clock support. The title alone cannot tell a buyer which arrangement they receive. Ask which named tier is included and which contact handles an incident outside normal hours.

Keep response and restoration as separate questions. Ask what starts the response clock, what the first response includes, who can authorise a site visit and what happens if remote diagnosis is insufficient. Request the actual terms rather than turn a response-time label into a repair deadline. PING has not timed the help desk or verified that an engineer can reach a particular port.

Follow the job, not just the alert

Fieldbase describes Tracker as a job-management platform with task assignment, engineer progress reports and stored installation reports. That makes documentation another useful conversation: who owns the open job, what evidence records the work and who confirms completion? A dashboard description is not proof that a specific fault has been repaired. Ask how the incident record reaches the person responsible for the vessel.

The maritime deployment page lists installation reports, network diagrams and user manuals at handover. Request a model of that handover pack before committing, and establish who receives updated records after a change. Record the difference between a proposed arrangement, equipment delivered and work accepted. Those are suggested purchasing checks, not documents PING has inspected for a real customer. Name the person trained to use the pack and the route for raising a fault after a crew change. Ask whether a configuration change creates a new diagram or leaves an older drawing in circulation. Request that responsibility in the proposal.

For an operator in Nigeria or a shore team in the UK, the important location is the vessel and its next support opportunity, not the website's domain. Confirm the actual port, contact, attendance conditions and replacement-equipment arrangement with the supplier. Nothing in this guide establishes service coverage, stock, local availability or endorsement. Explore more documented explainers on PING's Networks desk.