Ryver Outage History
Ryver is up right nowPingoru has recorded 52 incidents for Ryver: 2 in the last 12 months and 2 in the last 90 days.
Incidents, newest first
Minor November 2, 2026 Some users are receiving "This site cannot be reached", 13h 15m Chat Server, Ryver.com Website
Started Nov 02, 2026, 08:08 PM UTC· resolved Nov 03, 2026, 09:23 AM UTC
- investigating Nov 02, 2026, 08:08 PM UTC
We are researching the issue.
- investigating Nov 02, 2026, 09:08 PM UTC
On Monday, November 2, some of you had trouble reaching your Ryver and saw messages like "organization not found." This was caused by a DNS issue affecting ryver.com web addresses, and it has been resolved. Ryver itself kept running the whole time. Your messages, files and settings were not affected. If you still can't reach Ryver: some networks take a little longer to pick up the fix, but it should clear up shortly. To speed it up: Close and reopen your browser or the Ryver app. Restart your computer, or your office router if several people are affected. If you're still having trouble, reply to this email and we'll help you right away. We're sorry for the disruption, and thank you for your patience. The Ryver Team
- resolved Nov 03, 2026, 09:23 AM UTC
The DNS issue has been resolved.
Notice October 21, 2026 File Upload support has been deactivated due to a security vulnerability in PHP. 19h 34m Chat Server, API, Signup Site, Ryver.com Website
Started Oct 21, 2026, 01:04 PM UTC· resolved Oct 22, 2026, 08:39 AM UTC
- investigating Oct 21, 2026, 01:04 PM UTC
Per our CEO, Joe Faherty [email protected]: I wanted to let you know personally about some maintenance we did on Ryver last night and into this morning. A security weakness/vulnerability was recently found in PHP, a widely used programming tool used by millions of other websites, including some parts of Ryver. It's an internet-wide problem, not something specific to Ryver. As soon as we learned about it, we moved quickly to protect your account and your data. We have found no sign that anyone used this weakness to get at your data. You don't need to do anything. What we did: Last night and into this morning, we updated the affected parts of Ryver to a fixed version and restarted our servers. Out of an abundance of caution, we have turned off the ability to upload files. What it means for you: The update is currently being deployed and with the exception of file uploads, Ryver is working normally. As soon as the deployment is finished, we will be turning on the ability to upload files. I'm sorry for the disruption to your team's day. We chose to fix this right away rather than wait for a quieter time because keeping your conversations safe comes first. We know how much your team relies on Ryver, so we don't take that decision lightly. If anyone on your team noticed anything unusual, or if you have any questions, please reply to me directly.
- investigating Oct 21, 2026, 01:09 PM UTC
Affects the APIs only
- investigating Oct 22, 2026, 08:38 AM UTC
Ryver has been updated. "File Upload" service has been resolved.
- resolved Oct 22, 2026, 08:39 AM UTC
This incident has been resolved.
Notice December 9, 2024 Users receiving 503/504 Error messages. Performance slow. 21h 27m Chat Server
Started Dec 09, 2024, 01:50 PM UTC· resolved Dec 10, 2024, 11:17 AM UTC
- investigating Dec 09, 2024, 01:50 PM UTC
We are currently investigating this issue.
- monitoring Dec 10, 2024, 12:36 AM UTC
A fix has been implemented that relieved the stress on the database server. Additionally, we will be adding database indexes to the user notification area to improve alerting and notification receipt. We are continuing to monitor this issue to ensure performance and reliability are maintained. Thank you for your patience!
- monitoring Dec 10, 2024, 11:05 AM UTC
Maintenance is complete. Service has been restored.
- resolved Dec 10, 2024, 11:17 AM UTC
This incident has been resolved.
Major December 6, 2024 Users are receiving a "503 Service Temporarily Unavailable" message 3h 22m Chat Server
Started Dec 06, 2024, 07:36 PM UTC· resolved Dec 06, 2024, 10:58 PM UTC
- investigating Dec 06, 2024, 07:36 PM UTC
We are currently investigating this issue
- investigating Dec 06, 2024, 07:48 PM UTC
We are continuing to investigate this issue.
- investigating Dec 06, 2024, 08:53 PM UTC
The issue is outstanding. The initial reboot of the database server appeared to resolve but did not fully. We are continuing to investigate.
- investigating Dec 06, 2024, 09:01 PM UTC
We are continuing to investigate this issue.
- resolved Dec 06, 2024, 10:58 PM UTC
The issue has been resolved. We will continue to monitor this issue to ensure the root cause is resolved.