Current service status,
without guesswork.
Degraded Performance
One active incident is affecting Reporting & Exports in the EU region. All other verified components are Operational. One component cannot currently be verified and is shown as Unknown — it is not assumed healthy.
Overall status is derived from the current public component set under approved impact policy — it is not an unweighted average, and Unknown health on a critical component prevents an Operational overall state. No uptime percentage appears on this page.
Four Destinations, Four Different Jobs
Marketing and reliability pages link here rather than restating current state. A second copy of an incident is a stale copy.
System Status
This page. Current incidents, maintenance, component state, timestamps, updates, and history.
Authoritative for current operational state.
Platform Reliability
Evidence-gatedDefinitions, indicators, measurement methods, exclusions, and recovery evidence.
Held until maintained measures and history exist.
Enterprise Support
Customer-specific impact, account diagnostics, and private cases — through authenticated channels.
Trust Center
Cross-domain trust claims and the evidence directory.
Two Independent Events
Ordered by public impact and critical journey. Unrelated incidents are not merged merely because they share a component.
Report exports delayed or failing in EU region
Scheduled and on-demand report exports are queuing and some are failing. Viewing reports in-product is unaffected. Time capture, approvals, and record processing are unaffected.
- Components
- Reporting & Exports
- Scope
- EU region · production
- Started
- 07 Aug 06:18 UTC
- Detected
- 07 Aug 06:31 UTC
- First public update
- 07 Aug 06:52 UTC
- Latest update
- 07 Aug 09:20 UTC
- Workaround
- Reports remain viewable in-product; retry exports after resolution
Next update expected by 11:00 UTC. Cause is not yet stated publicly because it has not been established at a level we can support.
Notification delivery delays
Email notifications for approval events are delayed. In-product state is accurate and unaffected — the interface always shows the current state even when a notification is late.
- Components
- Notifications
- Scope
- All regions · production
- Started
- 07 Aug 04:05 UTC
- Latest update
- 07 Aug 09:35 UTC
Mitigation is active and health is being observed. This is Monitoring, not Resolved — recovery has not yet been verified.
Seven Public States, Stated in Text
Severity is never conveyed by colour alone. Each component shows its state, last verified time, and relationship to any active event.
Access & sign-in
Authentication and session establishment
Time capture
Recording work-time inputs across supported clients
Record processing
Classification and record assembly
Approvals
Review queues and approval decisions
Evidence Ledger
History, versions, and evidence references
Reporting & exports
Affected by INC-2026-0814 · EU region
Notifications
Affected by INC-2026-0815 · all regions
Integrations
Health sources stale since 06:10 UTC — state cannot be verified
Integrations shows Unknown, not Operational. Its health sources have been stale beyond policy since 06:10 UTC. The last known verified state was Operational, but we cannot confirm current state — so we do not claim it.
Region and environment selectors appear only where states genuinely differ and the public scope is approved. A region appearing in a status filter does not mean that region exists as a data-residency option — see Trust Center. No internal host, cluster, provider account, or infrastructure identifier appears here.
Published Separately From Incidents
Six maintenance states. We do not promise that all maintenance is impact-free.
Record processing upgrade
Scheduled- ID
- MNT-2026-0091
- Window
- 10 Aug 01:00 – 03:00 UTC
- Scope
- Record processing · all regions
- Expected effect
- Brief queuing; no data entry loss expected
- Owner
- Platform operations
Export service migration
In Progress- ID
- MNT-2026-0088
- Started
- 07 Aug 05:00 UTC
- Scope
- Reporting & exports · EU
- Expected effect
- Export delays during window
- Related
- Linked to INC-2026-0814
Unexpected user impact met incident policy, so a related incident was opened rather than the impact being absorbed into the maintenance record.
Notification provider change
Cancelled- ID
- MNT-2026-0086
- Was scheduled
- 05 Aug 02:00 – 04:00 UTC
- Scope
- Notifications
- Reason
- Prerequisite verification incomplete
Cancellation history is preserved. The future-impact implication is removed.
INC-2026-0814 — an attributable linear record
Newest first by default, with an accessible oldest-first option. Prior updates are never silently edited — corrections are versioned and marked.
Export processing capacity has been increased and the queue is draining. Some exports submitted between 06:18 and 08:40 UTC may still fail and require resubmission. Next update by 11:00 UTC.
A fault in the export processing path has been identified. Mitigation is in progress.
Correction (08:22 UTC): the original update stated all regions were affected. The confirmed scope is the EU region only. The prior wording is preserved above this correction rather than replaced.
We are investigating reports of delayed and failing report exports. Viewing reports in-product appears unaffected. Scope is not yet confirmed.
Why an incident can be called resolved
What a resolution states
- Resolution time and verification scope
- Approved health indicators and reconciliation categories, at a safe level
- Known residual effects, backlogs, or actions you may need to take
- Post-incident review state
Post-incident review states
“Pending” does not imply a public report will necessarily be published.
No universal “no data was lost” statement without verified reconciliation and approved evidence. And public resolution never means all customer-specific remediation is complete — account-specific reconciliation routes to Enterprise Support.
Resolved Events, Completed Work, and Corrections
An operational record for inspection — not a service-credit report.
| Event | Type | Scope | Start – end | Final state | Review |
|---|---|---|---|---|---|
| INC-2026-0811Approval queue latency | Incident | Approvals · APAC | 02 Aug 11:20 – 13:05 UTC | Resolved | Published |
| MNT-2026-0084Ledger index rebuild | Maintenance | Evidence Ledger · all | 31 Jul 01:00 – 02:40 UTC | Completed | Not required |
| INC-2026-0809Sign-in delays | Incident | Access · EU, US | 28 Jul 07:44 – 08:31 UTC | Resolved | Pending |
| COR-2026-0012Scope correction to INC-2026-0809 | Correction | Access | 28 Jul 09:15 UTC | Correction recorded | — |
| MNT-2026-0086Notification provider change | Maintenance | Notifications | Cancelled 04 Aug | Cancelled | — |
What This Page Does When It Cannot Tell You
The failure mode of most status pages is optimism. Ours is designed to be honest instead.
What you will see
- Unknown state, with the last known verified state and its time
- Whether sources are stale, unavailable, incomplete, or conflicting
- Which component or scope is affected
- Refresh, subscribe, support, and reliability-evidence routes
- On route failure: the last safely cached state with an explicit freshness warning
What will never happen
- A silent default to Operational
- An optimistic fallback when the source is unreachable
- A green overall state while a critical component is Unknown
- “Resolved” while recovery is only being monitored
- Internal diagnostic detail exposed while explaining uncertainty
Operational Notifications, Not Marketing
No organization, job title, or procurement-stage fields. Marketing consent is separate, optional, and never preselected.
What do you want to hear about?
Scope
Channel and delivery
Channels that are not currently supported do not appear here as options.
Confirm
You will receive a verification step before any notification is sent. Unsubscribe is one action from every message, and your selections never appear in URLs or analytics.
View
Your selected components, regions, event types, channel, and locale.
Pause
Temporarily stop delivery without losing your selections.
Modify
Change scope or channel, with the effective state confirmed back to you.
Unsubscribe
One clear action. No dark pattern, no hidden link, no retention flow.
Route Your Question Correctly
Platform Reliability
Evidence-gatedDefinitions, measurement, exclusions, and recovery controls.
Enterprise Support
Authenticated, customer-specific impact and account diagnostics.
Help Center
Common client and device troubleshooting.
Trust Center
Broader evidence navigation across security, privacy, and governance.
Never disclose worker records, customer data, or credentials in a public status form. Public status is not a substitute for emergency or contractual support channels — if you have a contractual escalation path, use it.