Outage in SAP Concur

Incident in Japan - e-Bunsho for Expense,Japan - e-Bunsho for Invoice on US2, EU2

Resolved Minor
April 01, 2024 - Started about 2 months ago - Lasted about 1 hour

Need to monitor SAP Concur outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including SAP Concur, and never miss an outage again.
Start Free Trial

Outage Details

In the US2 and EU2 Data Centers, submitting expense reports and invoices utilizing E-bunsho time stamp was below expected level. Affected users may have received the "Timestamp: Requested" when attaching an image on Expense or click Timestamp button on Invoice. As the Incident Response Team was being assembled, service self-recovered. We have verified that service performance is stable and will now resolve this incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete.
Latest Updates ( sorted recent to last )
ISSUE RESOLVED about 2 months ago - at 04/01/2024 04:10AM

In the US2 and EU2 Data Centers, submitting expense reports and invoices utilizing E-bunsho time stamp was below expected level. Affected users may have received the "Timestamp: Requested" when attaching an image on Expense or click Timestamp button on Invoice.

As the Incident Response Team was being assembled, service self-recovered.

We have verified that service performance is stable and will now resolve this incident. An investigation into the root cause of this incident will now be conducted, and a root cause analysis report provided when that investigation is complete.

ISSUE STATUS UPDATE about 2 months ago - at 04/01/2024 04:08AM

In the US2 and EU2 Data Centers, submitting expense reports and invoices utilizing E-bunsho time stamp was below expected level. Affected users may have received the "Timestamp: Requested" when attaching an image on Expense or click Timestamp button on Invoice.

Services have returned to normal operating levels. We will continue monitoring performance for the next 15-30 minutes to verify stability. Once verified as stable the incident will be resolved. conducted, and a root cause analysis report provided when that investigation is complete.

ISSUE IDENTIFIED about 2 months ago - at 04/01/2024 03:27AM

We are working to determine the user impact and will provide information as it becomes available.

Easily monitor SAP Concur and all your third-party status pages

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 3170 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook

Setup in 5 minutes or less

How much time you'll save your team, by having the outages information close to them?

14-day free trial · No credit card required · Cancel anytime