No one on my team is currently able to log in to Ramp.
5 Likes
I am having the same problem.
I am having the same problem.
Same here.
Have heard nothing from Ramp
login issues and employees are experiencing declined transactions.
Hi all! This issue was caused by a third-party service provider, and they identified the root cause yesterday.
You should now be able to access the app as expected. Our systems are currently processing a backlog of queued updates, so some recent activity – such as transactions made after 3:00 a.m. ET on October 20 – may appear with a short delay.
Please note that Ramp card authorizations and scheduled payments were not affected during this incident. 
Our engineering team will continue to monitor the situation to ensure full stability.
If anyone is still experiencing issues, please let me know, and I’ll help out. Thank you!
I’ve mentioned this before, but it continues to stand out. The pace of new feature releases seems to be outpacing platform stability. I understand that the recent “third-party” (Amazon) outage had a major impact, but it highlights a deeper issue: reliability. Whether through RAMPS’ own data centers or an alternative provider, stability has to be foundational.
We’re also seeing this imbalance in the rollouts of releases. New features go live, but we often find out after the fact. This leaves our teams confused about what changed, why something moved, or why new behaviors are suddenly appearing. Even the documentation is starting to lag behind, sometimes referencing outdated locations or workflows.
To give credit where it’s due, the rollout of the new AI feature was a great example of how it should be done. It had clear early communication, solid documentation, and the ability to enable when ready. That approach built confidence.
But stability and communication go hand in hand. This might be the moment for RAMP to take a “season of excellence”, to pause the rapid feature push and refocus on refining what’s already here: improving stability, tightening communication, enhancing workflows, and addressing the small but meaningful details that impact users daily.
Just my two cents, having been part of software teams and using software for over 35 years.