Ramp outages and problems
User reports, last 24 hours
30 reports in total, counted in 15-minute windows
In the last hour, 5 problem reports came in for Ramp, and at this time of day there are usually almost none. Over the last 24 hours there were 30 reports. The last spike in reports was 28 h ago and lasted 28 min. These are user reports from the US, where most people report Ramp problems.
- NormalClose to the usual level24 h · 30 reports
- ElevatedMore than 1.5 times the usual levelNone in this chart
- OutageMore than twice the usual level and far above the day's averageNone in this chart
- Usual levelWhat a usual day sees at that timeAlmost none at this time of day
In the past 24 hours, 30 user reports came in for Ramp. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 4 reports, about 5 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Ramp in November 2026
- Problem reports in November
- 208
- Outage spikes
- 1
- Periods of elevated reports
- 0
Monthly report for November 2026
People who report a problem with Ramp to the outage-report feed behind this page can tag what is affected. These are the categories they can pick; the feed shows no counts per category:
- Website
- Funds Transfer
- Login
- Payments
- App
- File Access
Where Ramp problem reports come from
The map shows where recent problem reports for Ramp came from in the US. Big cities always send the most, so dots in many places point to a widespread problem, and one area far ahead of the rest can mean a regional one.
- Outage now
- Problems now
- Normal
Map outlines: Natural Earth.
Ramp problem spikes, last 30 days
Since 28 October, Ramp had 2 outage spikes and 1 period of elevated reports. The longest lasted 28 min, on 16 November.
- Mon 19 Oct: no data
- Tue 20 Oct: no data
- Wed 21 Oct: no data
- Thu 22 Oct: no data
- Fri 23 Oct: no data
- Sat 24 Oct: no data
- Sun 25 Oct: no data
- Mon 26 Oct: no data
- Tue 27 Oct: no data
- Wed 28 Oct: 105 reports (outage spike that day)
- Thu 29 Oct: 14 reports
- Fri 30 Oct: 0 reports
- Sat 31 Oct: 0 reports
- Sun 1 Nov: 13 reports
- Mon 2 Nov: 1 report
- Tue 3 Nov: 13 reports
- Wed 4 Nov: 9 reports
- Thu 5 Nov: 4 reports
- Fri 6 Nov: 23 reports
- Sat 7 Nov: 5 reports
- Sun 8 Nov: 1 report
- Mon 9 Nov: 10 reports
- Tue 10 Nov: 1 report
- Wed 11 Nov: 2 reports
- Thu 12 Nov: 14 reports
- Fri 13 Nov: 8 reports
- Sat 14 Nov: 2 reports
- Sun 15 Nov: 2 reports
- Mon 16 Nov: 72 reports (outage spike that day)
- Tue 17 Nov: 28 reports
-
Outage
Mon 16 Nov, 19:02–19:30Lasted 28 min48peak reports
-
Outage
Wed 28 Oct, 19:56–20:16Lasted 21 min14peak reports
-
Elevated reports
Wed 28 Oct, 19:05–19:21Lasted 16 min10peak reports
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 28 October 2026. Monthly reports for all services
How to fix Ramp not working
Ramp is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach ramp.com over your own connection, right now. Nothing is sent to us or stored.
Check the Ramp report level
The status note at the top of the page shows whether user problem reports for the service are above their usual level, counted in 15-minute windows over the last 24 hours. A spike points to a shared problem; no spike means the issue likely sits on your side.
Reload the Ramp tab or app
Press Ctrl+R on Windows or Command+R on Mac to reload the browser tab, or force-quit the mobile app and reopen it. Sign in again if the screen still hangs; a fresh session clears stale login state without touching your card or account settings.
Test Ramp on a clean connection
A VPN or content blocker can break the login flow, so turn both off and repeat the action on Wi-Fi and on cellular data. On iPhone, check Settings > Cellular and confirm the Ramp app is allowed to use cellular data; on Android, open Settings > Network & internet > Internet and switch between Wi-Fi and mobile data.
Reinstall the Ramp mobile app
Delete the app and reinstall it from the App Store or Google Play. Sign in once it opens. If the problem is only in a browser, open a private window and sign in there; Chrome uses Ctrl+Shift+N, Edge uses Ctrl+Shift+N, Firefox uses Ctrl+Shift+P, and Safari uses Command+Shift+N.
While Ramp is down: what to use instead
- Web dashboard Open the service in a desktop browser if the mobile app will not load; it can handle expense entry and card balance checks.
- Physical card Use the card itself for a purchase; keep the receipt for later entry.
- Card issuer phone line Call the number printed on the back of your card to report a lost card or ask about a declined charge when the app is unavailable.
- Expensify If a report is due and the app will not open, Expensify can capture receipts and build the report for you.
Problems at the same time as Ramp
Since 28 October, all 3 of Ramp's spikes in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
Most often at the same time
How many of Ramp's spikes overlapped one of theirs.
During the latest spike
Ramp: Mon 16 Nov, 19:02 to 19:30
- Microsoft Outlook, outage,12 Nov 17:42 to 17 Nov 23:51
- Microsoft 365, outage,12 Nov 17:59 to 17 Nov 23:51
- Belastingdienst, outage,09:51 to 17 Nov 00:43
- GOV.BR, outage,11:04 to 17 Nov 03:54
- Pix, outage,11:15 to 17 Nov 03:01
- Sefaz, outage,11:15 to 17 Nov 00:27
- Caixa Econômica Federal, outage,11:49 to 21:55
- Microsoft Teams, outage,12:50 to 17 Nov 04:20
126 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
When people report Ramp problems
The busiest hour for reports about Ramp is 19:00 to 20:00 Central European time, and the busiest day is Wednesday.
By hour of the day
- 00:00 to 01:00: 0.24 reports on an average day
- 01:00 to 02:00: 0.04 reports on an average day
- 02:00 to 03:00: 0.05 reports on an average day
- 03:00 to 04:00: 0.07 reports on an average day
- 04:00 to 05:00: 0.03 reports on an average day
- 05:00 to 06:00: 0.02 reports on an average day
- 06:00 to 07:00: 0 reports on an average day
- 07:00 to 08:00: 0 reports on an average day
- 08:00 to 09:00: 0.02 reports on an average day
- 09:00 to 10:00: 0 reports on an average day
- 10:00 to 11:00: 0 reports on an average day
- 11:00 to 12:00: 0 reports on an average day
- 12:00 to 13:00: 0.33 reports on an average day
- 13:00 to 14:00: 0.05 reports on an average day
- 14:00 to 15:00: 0.08 reports on an average day
- 15:00 to 16:00: 0.24 reports on an average day
- 16:00 to 17:00: 0.21 reports on an average day
- 17:00 to 18:00: 0.47 reports on an average day
- 18:00 to 19:00: 0.85 reports on an average day
- 19:00 to 20:00: 1.4 reports on an average day
- 20:00 to 21:00: 0.59 reports on an average day
- 21:00 to 22:00: 0.77 reports on an average day
- 22:00 to 23:00: 0.74 reports on an average day
- 23:00 to 00:00: 0.8 reports on an average day
By day of the week
- Monday: 11 reports on an average Monday
- Tuesday: 6.1 reports on an average Tuesday
- Wednesday: 19 reports on an average Wednesday
- Thursday: 6.3 reports on an average Thursday
- Friday: 5.1 reports on an average Friday
- Saturday: 1.2 reports on an average Saturday
- Sunday: 2.6 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 41 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
What happens when Ramp goes down
Ramp is a spend management app for company cards, expenses, bill payments, and accounting sync. Finance teams and employees rely on it for receipt capture, spend approvals, transaction reconciliation, and ledger updates, so an outage interrupts daily money tasks.
Sign-in and dashboard loading usually fail first. Receipt uploads from the mobile app and approval queues can stall, and card transaction feeds and bill payment scheduling can fail. Some employees keep working. Accounting sync can lag or show stale data; because the status page only counts user problem reports in 15-minute windows over the last 24 hours, partial or regional trouble can appear as a cluster of reports without a full outage.
Ramp IP address, servers and network
- IPv4 addresses
- 104.18.37.222
Show all 2
- 172.64.150.34
- IPv6 addresses
- 2606:4700:4407::ac40:9622
Show all 2
- 2a06:98c1:3100::6812:25de
- Network
- AS13335 · Cloudflare, Inc., registered in the United States
- Served through
- Cloudflare · our check was answered by its Frankfurt (FRA) data centre
- DNS hosted by
- Cloudflare
- HTTPS certificate
- Issued by Google Trust Services, valid until 11 Feb 2027 (85 days)
- HTTP/3
- Supported
- Our check
- Answered in 475 ms
Checked from our server in Frankfurt, Germany, 25 h ago, for ramp.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 12 places around the world
All 12 locations got an answer from ramp.com. Fastest from São Paulo (429 ms), slowest from Singapore (1,208 ms). Every location connected through Cloudflare, Inc. (AS13335), using 2 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up | 833 ms | 172.64.150.34 |
| ViennaAustria | Up | 611 ms | 104.18.37.222 |
| MilanItaly | Up | 660 ms | 104.18.37.222 |
| ParisFrance | Up | 475 ms | 104.18.37.222 |
| AmsterdamNetherlands | Up | 755 ms | 104.18.37.222 |
| MadridSpain | Up | 803 ms | 104.18.37.222 |
| WarsawPoland | Up | 964 ms | 104.18.37.222 |
| DallasUSA | Up | 435 ms | 104.18.37.222 |
| Los AngelesUSA | Up | 575 ms | 172.64.150.34 |
| São PauloBrazil | Up | 429 ms | 104.18.37.222 |
| SingaporeSingapore | Up | 1,208 ms | 104.18.37.222 |
| TokyoJapan | Up | 625 ms | 172.64.150.34 |
Checked with check-host.net from its servers in these cities 25 h ago, for ramp.com. Time is how long each server took to load the page.
Ramp FAQ
Is ramp down right now?
Why was my Ramp card declined at checkout?
Why does the Ramp app keep logging me out?
Why won't my receipt upload in Ramp?
Why is my Ramp transaction still pending?
Service updates from @tryramp
No posts about problems from @tryramp in the last 14 days. The latest is from .
Contact Ramp support
Tip: Ramp doesn't list a public status page that we know of, so its help centre and the report chart on this page are the best places to check.
How we track Ramp
The status on this page comes from user-submitted problem reports for Ramp, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Ramp, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. Ramp doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.