Perigee

Service status

Read the instruments, not a green light.

This page runs small public checks from your browser and explains the boundaries behind them. It deliberately avoids claiming that every station, provider, account, email, or payment path is healthy from one synthetic request.

Live checks from your browser

These lightweight checks are point-in-time diagnostics, not an uptime guarantee or service-level agreement.

Web experience

This status page was delivered successfully. Individual cached or account-only paths can still behave differently.

Available

NOAA station data path

Checking the public station directory through Perigee…

Checking

Hosted MCP transport

Checking the public MCP endpoint…

Checking

Checks in progress

What the checks cover

  • Web experience: this page reaching your browser proves only that its current delivery path answered.
  • NOAA station data path:a same-origin request exercises Perigee's public station route and NOAA metadata dependency. It does not prove every observation, forecast, station, or product is available.
  • MCP transport: a lightweight HEAD probe checks whether the public hosted transport answers without running a tool.

Authentication, email delivery, Stripe checkout, billing portal access, user entitlements, and provider-specific products cannot be safely proven by an anonymous public probe. Check those in the relevant account workflow and report a reproducible failure.

Provider boundaries

Perigee relies on NOAA CO-OPS for tides, water levels, currents, station metadata, and related measurements; NWS for marine-weather products; Firebase for accounts and application storage; Stripe for subscription billing; Resend for application email; Vercel for hosting and analytics; and OpenFreeMap for the station map. A provider may be partially degraded while the Perigee site itself remains reachable.

Perigee uses cached data and partial results in some paths, but an available page can contain stale, partial, or unknown values. Always read timestamps, source labels, and missing-data warnings.

Known limitations

  • Not every NOAA station exposes every sensor or forecast product.
  • Great Lakes stations and non-tidal gauges can have different products and meanings than coastal tide-prediction stations.
  • NOAA or NWS maintenance, upstream throttling, network failures, and delayed observations can produce gaps or stale results.
  • Email timing depends on valid source data, address state, provider acceptance, mailbox filtering, and scheduled-job execution.
  • Browser extensions, privacy tools, blocked popups, denied location, or blocked map origins can affect one visitor without a platform incident.

Report an issue

Email ryandcardin@gmail.com with the affected URL or endpoint, station ID, approximate time and time zone, status code, expected result, actual result, and whether the problem reproduces. Do not include passwords or secrets. Security issues belong on the security reporting path.

Product changes and resolved user-facing improvements are summarized in the changelog. Perigee is not an emergency, weather-warning, or navigation service.