Active provider: supabase_postgres. Runtime URL: configured. Direct migration URL: configured.
GlobeIceService Status
GlobeIce launch status
A public status page for users and operators: green means available, yellow means needs attention, red means failed or blocked, and blue is neutral information.
Current posture
OK: public routes onlineOK: HockeyOS shell onlineINFO: source coverage expandingOK: Supabase Auth auth providerOK: Supabase Storage storageOK: Supabase Postgres databaseWARN: paid checkout gatedWARN: feeder/main handoff watch
Database provider gate
GlobeIce data remains Prisma/Postgres, with Supabase Postgres as the only approved live runtime. Neon and local Postgres are import/audit sources only.
DB role is main. Runtime pooler: likely. Supabase project-ref guard: configured.
Auth provider gate
Login is now tracked as a provider-backed launch dependency so Supabase, Clerk, or Auth.js readiness can be evaluated without hiding account-access risk.
Active provider: supabase. Browser env: configured. Server env: configured. Provider env: explicit.
Supabase browser env is present and admin/storage env is present. Supabase Auth is the primary launch lane again; Clerk/Auth.js remain explicit fallback providers only.
Storage provider gate
Attachments and governed media are tracked as a separate launch dependency from login so object-storage readiness does not hide inside the auth outage.
Active provider: supabase. Signed upload: implemented. Signed read: implemented. Provider env: explicit.
Supabase Storage env is present, and the active provider is supabase. Supabase Storage is the active attachment lane. Keep buckets private, use signed URL smoke checks, and monitor quota/egress; S3/R2 or NAS can remain later scale-out lanes. Upload/read signing will fail closed until the selected provider is configured.
Feeder and cost guard gate
The launch path keeps Supabase as the runtime target, while source polling and Main pull traffic remain explicit so provider capacity and review controls stay visible.
Timed out reading Main feeder pull posture for public status. Open Ops console or Feeder Bridge for live operational detail.
Cost guard: unknown. Control mode: unknown. Latest pull: not recorded.
Timed out reading feeder run-control posture for public status. Open Feeder Bridge for live operational detail.
Runtime: unknown. Profile: unknown. Source polling: unknown.
Launch operators can pause cost-heavy work in Control Panel, pull deliberately through Feeder Bridge, repair failed rows in Dead Letters, and route accepted hockey data through Intake before it reaches public pages.
Recommended action: Keep provider credentials in place and only resume source traffic deliberately.
OK
Public site
World, search, countries, leagues, clubs, teams, arenas, matchcenter, news, rules, sources, and contribution routes are available.
OK
HockeyOS
Personal and organization workspaces are available with navigation for calendar, documents, tasks, communications, arenas, games, and admin.
INFO
Feeder and governance
Admin feeder, intake, verification, automation, and source-trust routes are present for launch operations and smoke coverage.
Launch gate
This status page mirrors the launch checklist: available routes are not the same as broad unattended launch readiness.
OK
Scheduler and smoke
Launch requires cron posture, route/link audit, launch smoke, live public smoke, and cross-repo feeder verification to be understandable to operators.
WARN
Source coverage
Broad unattended launch waits until source coverage, dead-letter replay, and auto-write policy are strong enough to reduce manual guesswork.
INFO
Readiness criteria
Public pages are checked for resolved references, trust/provenance minimums, freshness, and no blocking moderation or incident flags.
Paid launch gate
Public pricing can be visible before live subscriptions are fully armed. These checks keep payment readiness explicit for users and operators.
Paid plans are currently routed through assisted checkout until self-service is enabled.
Stripe webhook signing is configured for entitlement updates.
Billing management is handled by GlobeIce support until the customer portal is enabled.
Public readiness states
Readiness is rule-driven and auditable, so public pages can move through review, publish, withdrawal, and repair without hiding operator risk.
not_readyready_for_reviewready_for_publishpublishedwithdrawn