1. Home
  2. Services
  3. Banks & payments
  4. Ramp
Ramp ramp.com Live · Operational

Is Ramp down right now? Live status and outage tracker

No, Ramp is up.

No widespread outage detected. 5 user reports in the last hour is within the normal range.

Reports, last hour
5
Usual at this hour
Almost none
Vs the hour before
+150%

User reports, last 24 hours, one bar per 15 minutes. Dashed line: the usual level. 96 normal · 0 elevated · 0 outage

Not working for you?

Last spike · · Data refreshes every 5 minutes

01 · User reports
5 reports in the last hour

From a public outage-reporting feed, counted in 15-minute windows. The verdict above is based on these.

02 · Our check, Frankfurt
Answered in 475 ms

Our server loaded ramp.com 25 h ago. Behind Cloudflare.

03 · 12 cities, check-host.net
12 of 12 got an answer

Fastest from São Paulo (429 ms), slowest from Singapore (1,208 ms). 25 h ago.

Last 24 hours

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.

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.
  • 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
Reports, last hour
5
150% on the hour before
Uptime, 24 h
100.00%
No outage windows
Last outage
None
In the last 24 hours
Busiest 15 minutes
4
4 reports, 5 h ago
Ramp status card: No, Ramp is up. User reports over the last 24 hours.
Share this statusThe picture people see when this page is shared: the answer and the last 24 hours of reports.

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.

No problems detected in the last 24 hoursReports for Ramp stayed at their usual level the whole time.
This month

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
World map

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
Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.

Map outlines: Natural Earth.

Last 30 days

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:30
    Lasted 28 min
    48peak reports
  • Outage
    Wed 28 Oct, 19:56–20:16
    Lasted 21 min
    14peak reports
  • Elevated reports
    Wed 28 Oct, 19:05–19:21
    Lasted 16 min
    10peak 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

Troubleshooting

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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 it is down

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.
Same time

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.

A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.

Busiest times

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.

About

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.

Servers and network

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.

LocationResultTimeAddress reached
FrankfurtGermanyUp833 ms172.64.150.34
ViennaAustriaUp611 ms104.18.37.222
MilanItalyUp660 ms104.18.37.222
ParisFranceUp475 ms104.18.37.222
AmsterdamNetherlandsUp755 ms104.18.37.222
MadridSpainUp803 ms104.18.37.222
WarsawPolandUp964 ms104.18.37.222
DallasUSAUp435 ms104.18.37.222
Los AngelesUSAUp575 ms172.64.150.34
São PauloBrazilUp429 ms104.18.37.222
SingaporeSingaporeUp1,208 ms104.18.37.222
TokyoJapanUp625 ms172.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.

Questions

Ramp FAQ

Is ramp down right now?

The status at the top of this page shows whether user problem reports for the service are above their usual level, counted in 15-minute windows over the last 24 hours. The site does not monitor the service itself, so treat the report level as a signal from other people. To check your side, load the app on cellular and open the web dashboard on another device; if both fail while other sites work, restart your device and review your login.

Why was my Ramp card declined at checkout?

A decline usually comes from a locked card or a merchant category block on that card. Open the card in the app and check its controls before you retry. That part is quick. If the terminal still rejects it, use another payment method and ask your company admin to review the card.

Why does the Ramp app keep logging me out?

The app can sign you out after a session timeout, and a failed biometric check can do the same. Update the app and confirm your phone's clock is set automatically before you sign in again. If the loop continues, sign in on the web dashboard to see whether the account works there. That narrows the problem to the mobile app or the account.

Why won't my receipt upload in Ramp?

A failed upload can come from a weak connection or a file the app will not take. Try a smaller photo or a PDF on a stable network, then upload from the web dashboard if the mobile app still stalls. Check the transaction first. A receipt that is already matched to another charge can fail to attach, so remove the old match before you retry.

Why is my Ramp transaction still pending?

A pending charge is only an authorization; the merchant controls when it posts. That can take a few days. Wait for the merchant to capture it, then match the receipt to the card transaction. If the charge drops off the merchant side but stays in Ramp, ask your company admin to review the card account.
Official channels

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.

For your site

Put the Ramp status on your site

Paste one of these into a web page, a blog post or a README: a small badge, or a card with the chart. Both show the same status as this page, based on user problem reports, and link back here.

Ramp status badge, as it looks now

HTML
<a href="https://isitdownrightnow.app/services/ramp/"><img src="https://isitdownrightnow.app/badge/ramp.svg" alt="Ramp status" height="20"></a>
Markdown, for README files
[![Ramp status](https://isitdownrightnow.app/badge/ramp.svg)](https://isitdownrightnow.app/services/ramp/)

A live card with the chart

The status, reports in the last hour and the last 24 hours, updated every 5 minutes. Use the frame, or the image where frames are not allowed, such as newsletters.

Frame
<iframe src="https://isitdownrightnow.app/embed/ramp/" title="Ramp status" width="100%" height="230" style="border:0;max-width:560px" loading="lazy"></iframe> <p><a href="https://isitdownrightnow.app/services/ramp/">Ramp status</a> from IsItDownRightNow.app</p>
Image, updated about every 10 minutes
<a href="https://isitdownrightnow.app/services/ramp/"><img src="https://isitdownrightnow.app/share/ramp.png" alt="Ramp status: problem reports over the last 24 hours" width="600" height="315" loading="lazy"></a>
Markdown image, for README files
[![Ramp status](https://isitdownrightnow.app/share/ramp.png)](https://isitdownrightnow.app/services/ramp/)

Badge, frame and image load no scripts from other sites and set no cookies; people who see them on your page load them from our server. More for journalists.

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.

Elsewhere

Check other services