Resolved after 1 hour 25 minutes, affecting Japan - e-Bunsho for Expense, on January 19, 2026.
In the US2, EU2, and APJ1 data centers, generating an eBunsho timestamp was unavailable for 85 minutes. Affected users experienced an error “Timestamp: Requested,” when attempting to attach an image in Concur Expense. The root cause of the incident has been identified to be a service disruption within our third party Japanese Trust timestamp provider. Corrective Actions: N/A
Affected components
Update timeline
- resolved Jan 21, 2026, 10:15 PM UTC
A system outage caused a delay in posting incident communications. The issue has since been resolved, and communications for incidents that occurred during the outage are now being published. In the US2, EU2, and APJ1 data centers, generating an eBunsho timestamp was unavailable for 85 minutes. Affected users experienced an error “Timestamp: Requested,” when attempting to attach an image in Concur Expense. As the Incident Response Team (IRT) was being assembled, services self recovered. We have verified that service performance is stable and will now resolve this incident. A continued investigation into the root cause of this incident will be conducted, and a root cause analysis report provided when that investigation is complete.
- resolved Jan 21, 2026, 10:24 PM UTC
In the US2, EU2, and APJ1 data centers, generating an eBunsho timestamp was unavailable for 85 minutes. Affected users experienced an error “Timestamp: Requested,” when attempting to attach an image in Concur Expense. The root cause of the incident has been identified to be a service disruption within our third party Japanese Trust timestamp provider. Corrective Actions: N/A
Your product runs on more than SAP Concur
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services