Is SAP Concur down in the US?
Checks passingin the US, measured from Ashburn and San Jose
All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked SAP Concur at Nov 7, 2026, 6:03 PM UTC.
Over the last 24 hours we completed 90 checks from Ashburn and San Jose and 90 answered cleanly, 100.00% availability.
Of the 2 other regions we check SAP Concur from, all 2 read checks passing right now.
Email me the next time we see SAP Concur go down
What our Ashburn and San Jose probes measured
Last checked Nov 7, 2026, 6:03 PM UTC.
SAP Concur from Ashburn and San Jose over the last 30 days
Over the last 30 days, SAP Concur answered our Ashburn probe in 3,120 ms on average, and 1 check in 20 took longer than 4,356 ms.
Over the last 30 days, SAP Concur answered our San Jose probe in 3,302 ms on average, and 1 check in 20 took longer than 4,593 ms.
Ranked by average response time across the 4 cities we check SAP Concur from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 2,741 ms and Tokyo slowest at 3,719 ms.
From Ashburn and San Jose we ran 447 checks of SAP Concur in 6 days, and 447 answered cleanly: 100.00% availability.
Every one of those days was clean: not one failed check.
In Ashburn local time (EST), SAP Concur was slowest around 10 PM, at 3,810 ms on average over the last 14 days, and quickest around 11 AM, at 2,453 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Sat, Nov 7 | 69 | 100.00% | 3,163 ms |
| Fri, Nov 6 | 86 | 100.00% | 3,394 ms |
| Thu, Nov 5 | 85 | 100.00% | 3,215 ms |
| Wed, Nov 4 | 87 | 100.00% | 3,038 ms |
| Tue, Nov 3 | 84 | 100.00% | 3,076 ms |
| Mon, Nov 2 | 36 | 100.00% | 3,482 ms |
SAP Concur outages measured from the US
Our Ashburn and San Jose probes measured no confirmed SAP Concur outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check SAP Concur from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 40 checks |
| Tokyo | Checks passing | 100.00% of 24 checks |
Other countries we check SAP Concur from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against SAP Concur's public endpoints. They are not user reports, and they are not SAP Concur's own status page.
See SAP Concur's full check readings, the 90-day history by region, or the outage tracker methodology.
The US readings here are taken from that country and show the time of the last one, but SAP Concur has not yet accumulated enough continuous history for us to publish this page to search engines.
Check your own site from Ashburn
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter