Pipeline watch

A fishing vessel at trawl speed (0.8–5.5 kn) inside a 1 km corridor, by its own “engaged in fishing” AIS status, or by type and speed.

A vessel of 40 m or more stationary near a line, confirmed over 15 minutes. Platform standby and terminal anchorages are excluded.

A non-fishing vessel of 50 m or more at 0.5–3 kn tracking a line’s bearing, confirmed over two passes. The post-Nord Stream pattern.

Yes: power-from-shore and the offshore fiber backbone, same detectors. Public cable routes are schematic, so the corridor is 2 km and every alert says so.

Norwegian practice, Gassco’s published rule: activity within 500 m of a line needs a formal agreement with the operator, and within 2 nautical miles an interaction. An event badged with a zone is not just close, it is inside somebody’s paperwork.

Yes. Private geometry on your subscription, your cables, umbilicals, known high-risk corridors. Same detectors; never visible to anyone else or on the public map.

A monthly, quarterly or yearly summary for your lines: event counts, 500 m and 2 nm zone statistics, and measured trawl-crossing frequencies from our logged history. Reports and custom alerts are part of the paid subscription.

Email, or webhooks: CloudEvents v1.0 batches (Azure Event Grid ingests them natively) or Slack/Teams text. At most one alert per vessel and line every six hours. Contract: JSON Schema · AsyncAPI 3.0. Types are versioned; AIS report time and detection time travel separately.

Positions are AIS self-reports, a dark vessel is invisible, structurally. Burial and free-span state is not public; depth is the proxy, your own geometry the fix. Gear size is not broadcast; vessel size is, in every alert.

AIS-gap detection (going dark near infrastructure), safety-zone approaches, weather windows, the UK side. Ask for one below, it moves up.