Notice scope
Published 13 October 2026. This date identifies the notice, not a successful health check. Check your own workflow and report failures.
STATUS · MANUAL NOTICE
Health unknown: live service health is not verified by this page. This is a manually maintained notice, not an automatic uptime monitor. No current incident assessment has been published here; that does not mean there are no incidents.
Published 13 October 2026. This date identifies the notice, not a successful health check. Check your own workflow and report failures.
Public signup remains closed while launch-readiness work is completed. Existing account access and feature availability depend on the account and the current service state.
Ask about accessContact support with the page, observed result, time and timezone, and a request ID if one is shown.
Report an incidentThis page gives you a public contact path and space for manual incident communication. Its availability alone does not establish that sign-in, conversations, billing, storage, or integrations are healthy.
Describe the affected feature and when the issue began. Keep existing request IDs so support can correlate the report. Avoid repeatedly submitting payments or destructive actions when their outcome is uncertain.
Any incident update should state its observation time, affected features, known limitations, and what has actually been verified. Until such evidence is published, treat service health as unknown rather than assuming recovery.