Status source
Public page plus internal monitoring and incident response references. Automated public uptime feed is not connected yet.
Current Public Status Snapshot
This snapshot is intentionally careful. It does not create uptime, SLA, or no-incident claims.
Public incident register
Created 2026-05-30. No active public incident entry is posted here as of this update.
Uptime and SLA
TrueLink does not publish an uptime percentage or incident-free history until monitored evidence exists.
Next evidence source
Connect public status automation, synthetic checks, historical incident entries, and owner review workflow.
Service Areas
Each service area is listed with the current public evidence boundary. Status wording must stay conservative until live monitoring is published.
| Service area | Public status wording | Evidence source | Current limitation |
|---|---|---|---|
| Public website, Trust Center, blog, and landing pages | Manual public snapshot only | Static public pages and sitemap entries | No public synthetic uptime series connected yet. |
| Member, creator, and admin SaaS surfaces | Internal monitoring references exist | docs/OBSERVABILITY_AND_MONITORING_ROADMAP.md | Public status feed must not infer runtime health from internal roadmap notes. |
| Authentication and account security | Governed by security and incident response controls | docs/ISMS_INCIDENT_RESPONSE_PLAN.md | External audit and public incident evidence are still pending. |
| AI, SEO, and blog generation workflows | Governed by AI review and quality gates | docs/AI_GOVERNANCE_AND_DISCLOSURE_STANDARD.md | Provider-specific outages are disclosed only when they materially affect users. |
| Payments, email, and external integrations | Subprocessors are labeled separately | docs/DATA_PROCESSING_SUBPROCESSORS.md | Third-party incident status must be verified against provider evidence. |
Incident History Register
Public history entries are added only when the event is confirmed, customer-impacting or security-relevant, and safe to summarize.
| Date | Severity | Public status | Summary | Evidence note |
|---|---|---|---|---|
| 2026-05-30 | Initial register | Published | The public status and incident history surface was created. | This row is not a no-incident or uptime claim. |
| Future confirmed incidents | P1/P2/P3/P4 | Active, monitoring, resolved, or post-incident review | Customer-impacting incidents should receive a concise public summary after triage. | Do not expose sensitive operational detail, secrets, personal data, or exploit steps. |
Public Update Cadence
These are operating rules for future incidents, not historical performance claims.
When to publish
Publish a public entry after customer impact is confirmed and a safe, non-sensitive summary can be shared.
Update rhythm
For an unresolved public incident, update on material changes and target at least one public note per business day.
Closure note
Publish resolution state, user impact, mitigation, and follow-up action when disclosure is safe and reviewed.
What not to say
Do not publish exact uptime, no-incident claims, breach conclusions, or root cause certainty without reviewed evidence.
Report A Security Or Availability Issue
Responsible reports help us confirm impact and protect users.
Send security or availability concerns to security@truelink-group.com. Include the affected URL or workflow, time observed, account context if relevant, reproduction steps, screenshots or logs that do not expose unrelated personal data, and expected impact.