New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Client area up again , vm still up.
wow. Their response below. When will this nightmare end...
Internal Management Staff
Apr 18, 2026, 12:07 AM
Unfortunately its been 208 days and a refund is not possible.
Just thinking about what I should responce
This is a PayPal limitation, after 180 days refunds can no longer be issued.
So you state to honor refunds/cancellations but then say this?
Internal Management Staff
Apr 18, 2026, 04:55 PM
Unfortunately PayPal does not allow refunds after 180 days, take it up with PayPal not us
I have filed a resolution case with Paypal. Hoping for quick resolution.
Well, I got my resolution. Paypal won't issue a refund because it's been beyond 180 days. Perfect. A company who has no control over their own finances, holds no accountability for their issues, and can't issue refunds to their own customers. Love it.
But you were offering refunds for your emergency uhaul trip to Atlanta, what does paypal have to do with this? Man you guys sure are working hard at tanking what little reputation you have here.
Can't wait for your next sale thread, lol.
They really should be banned from LEB/LET.
It’s not logical to expect the same service quality with 1/5th of the price that you would get from big players. One should always expect downtime and problems, especially with cheap hosting services.
I honestly dont understand the level of drama enacted here, just get on with it.
They're the ones that priced it at 1/5th of the price. The hosting services can't just throw their hands up in the air and say what did you expect without any pushback.
Update: received my refund.
This is the last update and closure from me with regards to this RAVNIX mess. I was requesting to resume my service since I wasn't getting a refund but they pulled through, today, of all days. "Upon management approval, we have issued the reimbursement to your PayPal account via Friends and Family." As the saying goes, better late than never. Given that they did follow through, I'm both relieved and grateful to put this all behind. I wish them best of luck in their future.
Anyone else server is down?
Downtime 21 May 06:43 Ongoing...
Again? 🤯🤬
⚠️ The server 74.50.11.xx has been offline since 8:43 AM Berlin time (2:43 AM NY time).
Same. 23.129.180.x/24 Down since 2:39amEDT. Client portal dead as well.
Yeah, fully dead clientarea and supportarea. Seems that this is the end
Probably not renewed the IP Ranges I guess
I was under the impression that people learned from their mistakes.
it happened twice (was it 3 times?) before the emergency uhaul trip so i dunno. these guys probably mean well and have good intentions but they're either not good at bills or they're shoestring. spent too much on all the cute gg domains maybe.
Hey @Ravnix, can you clear this up?
Downtime for hours. Client area dead. Update?
My vps up now 😏 13 hours of downtime
Mine came back also after 13 hours
Dear RAVNIX Customers,
We sincerely apologize for the extended downtime experienced earlier today.
Our upstream carrier, FiberLight, performed scheduled maintenance overnight between approximately 3:00 AM and 7:00 AM. Unfortunately, because our circuit was recently deployed, we were not included in the maintenance notification list and did not receive advance notice of the work.
As part of the maintenance, our upstream provider replaced an older router with two new routers as part of a network upgrade. During this migration, our services were placed on one of the newly deployed routers, which only had connectivity to NTT. Unfortunately, the router experienced connectivity issues toward NTT, resulting in a full traffic loss for our network.
At approximately 11:00 AM Eastern Time, our upstream provider migrated our services onto an alternate router utilizing Arelion connectivity. However, an additional routing policy issue caused our BGP prefixes to be improperly rejected, preventing a majority of our network from being fully restored until the issue was identified and corrected by their engineering team.
The outage lasted from approximately 2:47 AM until 3:46 PM Eastern Time.
We know outages like this are extremely frustrating, especially one of this duration, and we truly appreciate everyone's patience while both our team and our upstream provider worked through the issue.
To help improve redundancy moving forward, we are actively working on bringing online a second upstream provider so that events like this can be mitigated much more effectively in the future.
At this time, services have been restored and routing appears stable. If you continue to experience any issues, please open a support ticket so we can investigate immediately.
If you would like to request SLA credits related to this outage, please open a billing ticket and we will be happy to assist.
Thank you again for your patience and understanding.
RAVNIX LLC
Dear @RAVNIX,
We all know that things happen, and no network is 100% immune to force majeure or upstream carrier errors. Thank you for providing such a detailed post-mortem regarding the root cause of the incident.
However, moving forward, it is absolutely crucial for us to receive notifications about scheduled maintenance well in advance. This is essential so that clients can plan ahead, prepare a "Plan B," and ensure business continuity on our end during the downtime.
I truly hope @Ravnix takes this feedback into account, automates the SLA credit process, and speeds up the deployment of the second upstream provider for better redundancy. Wishing you the best with the infrastructure upgrades!
A few months ago, we had an issue with IPXO. Our email was on their bounce list causing none of the invoices to be sent to us, we have also setup autopay after the few incidents with them and we are slowly moving out of those subnets and using our own IP space, and contracted IP space instead of month-to-month renting.
In a normal situation, we would've had time to send out a notification. Unfortunately the upstream didn't tell us it was maintenance until 3 hours after the outage started. Before that they were blaming us saying we were the only ones affected.
We are working on redoing the ticket system to add in much more automation for simple tasks, including SLA credits.
Unfortunately this will still probably take a month or 2, most of the upstream providers need 60-90 days to deploy a circuit.
Dear @RAVNIX,
Please help me resolve the issue in the ticket I submitted:
Support Tickets: TEC-25964861-116
The specific issue is:
Why can't I use IPv4?
Before migration: IPv4: 38.247..*** **
After migration: IPV4: 74.50..*** **
Neither can be used！