I am currently traveling in mostly remote areas until sometime in April 2024. Consequently DM's sent to me will go unanswered during this time.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
I previously mentioned one of our IPv4 providers being upset regarding abuse reports. It seems like the situation is continuing to escalate even though we're doing everything we can to prevent it. We have increased minimum plan prices as you may have noticed on our site, to reduce abusive signups. We've had someone go through orders manually. Coinpayments was gotten rid of (coincidentally but we were considering it either way) and only Coinbase which has also reduced shady signups. We've replied to every abuse report, even the many duplicates that people like sending.
The provider is re-selling Cogent IPv4 which we were not initially aware of and implemented an abuse fee, I assume after Cogent did and with Cogent forwarding reports to this provider who forwards it to us, it slows down the process and adds in additional frustrating work for everyone I'm sure. We've paid for the fees even though initially we were told there'd be no other fees, which is fine.
Over the last 31 days, we've received a total of 40x IPv4 addresses reported, with the majority being poorly secured servers sending out attacks, with 59 additional duplicate emails. So this is 40 reported out of 32,768 IP block. I don't know if they truly believe 40 reports in a month on a /17 IPv4 block is excessive compared to other leases.
They've continued to threaten termination, usually after an abuse report they particularly do not like (something more serious, a few of these have occurred.)
I'm going to try to speed up IPv6 deployments and I'm hoping they are reasonable. I'm just providing this for the sake of transparency. It's obviously going to be very very bad if they decide to terminate that many IPv4 addresses and it would be difficult to replace them on short notice. I personally do not feel like this would be fair and we would of course have another company we would have to take to court over but I just wanted to paint a full picture/update for you guys here.
@VirMach said: Coinpayments was gotten rid of (coincidentally but we were considering it either way) and only Coinbase which has also reduced shady signups.
That is interesting. Some years ago providers were leery of crypto payments but a few took a chance on them and were pleasantly surprised to find very little abuse. I guess that didn't last. Thanks for keeping us informed.
@VirMach said: Coinpayments was gotten rid of (coincidentally but we were considering it either way) and only Coinbase which has also reduced shady signups.
That is interesting. Some years ago providers were leery of crypto payments but a few took a chance on them and were pleasantly surprised to find very little abuse. I guess that didn't last. Thanks for keeping us informed.
They stopped doing business in the US and pretty much force closed our account in any case, but with that news, it means they're in some way possibly legally in trouble (this is just speculation) with the US compliance. And of course it's not that cryptocurrency is inherently bad or abusive, we've just noticed with Coinbase at least some criminals stopped using it as I assume that's in some way better logged and investigated for crimes (once again just speculation.)
I believe it's possible that we became one of the providers people preferred, and Coinpayments was ones of the payment methods they preferred, and it kind of combined together to create a negative situation.
@mayiprint said: @VirMach VPS has not been available since June. There is no information to know the progress of the processing.
Node: LA10GKVM14
The plan for the old nodes that failed is to at the very least refund everyone for the unused time since it went offline. We were discussing internally how we wanted to proceed in the coming days and once it's finalized, an announcement will be made, most likely via e-mail.
These were the nodes:
LAKVM9, LAKVM26, LA10GKVM14.
As far as I remember, they were all part of a mass power failure event that caused PSU to die and data was lost from RAID controller and other failures and/or human error by datacenter techs. Since these occurred at the worst possible time while we were doing everything else at peak workloads, and were already falling behind, it wasn't possible to work them into the schedule and I do apologize for it having taken such a long time (and the lack of official updates) but we have been working on it more recently. We haven't forgot about them.
@AlwaysSkint said: @Virmach Purely being nosy, approx. how many Tickets are open, since the latest merging & closing?
(Might put things in perspective for some.)
This is an estimate as I don't have an exact figure for this anymore, but 2600-5000 tickets were "merged" into 1300-1500 tickets (as in some people made 2 tickets, some people made way more.)
We made approximately 5000 replies over the last 30 days, and approximately 5000 tickets were created over the last 30 days.
2,500 tickets were left over as of yesterday, and about 150 tickets created over the last 12 hours.
100 priority tickets were left over as of yesterday.
The majority of tickets are created between 6PM-8AM PST (Pacific Standard Time), which is between 1AM-3PM GMT (Greenwich Mean Time), or 9AM-11PM CST (China Standard Time.)
The following numbers match these keywords for remaining tickets:
550 "Migration" (Mostly Tokyo paid migration requests.)
300 "Offline" or "Outage" (Mostly reporting outages already discussed.)
160 "Refund" (Mostly refund requests for migration request.)
350 "Connection" (Mostly older already-resolved IP or network issues.)
We're going to try to clear out migration related tickets today, and refund requests. The current plan is to auto credit and close them for the stuck migrations. Then new migration requests will exclude Tokyo location selection and also have the new built-in auto credit system if it fails.
Comments
LoooooL
@Mason You've got a hammer; you know you want to.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Mason is Thor ???
Or
jane ?
———-
blog | exploring visually |
I couldn't possibly comment.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Recusals and disclaimers galore
Or plain ol plausible deniability
———-
blog | exploring visually |
How does the 'murican 5th amendment go?
[Edit]Mason is YABS God. Simples.
[/EDIT]
In other news: I finally got around to changing the timezone on the AMS VPS. And, DALZ to CHIZ didn't work.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
everyone just chill; disputes can be settled with YABS frenzies on the bench thread.
I bench YABS 24/7/365 unless it's a leap year.
My wife wishes.
In reality, I'm more like a Yoshi that accidentally picked up a hammer in Super Smash.
Head Janitor @ LES • About • Rules • Support
I would but my Virmach VPs are down and Greencloud discouraged BMs :-(
Maybe I will bench my raspberry pi
———-
blog | exploring visually |
aside from vyas with broken vps everyone else can go benchbomb !
I bench YABS 24/7/365 unless it's a leap year.
YABS?
quadranet LAX
I bench YABS 24/7/365 unless it's a leap year.
Posting a ticket instead of BM. The latter to follow upon resolution. Consider this a "BM in the (Low End) Spirit"
Cheers
Ticket #189699
———-
blog | exploring visually |
NYC Metro (AKA New Jersey): Dedipath@INAP NJ1
I am currently traveling in mostly remote areas until sometime in April 2024. Consequently DM's sent to me will go unanswered during this time.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
Risky!
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Business
Risks will be have been taken.
(h/t to OGF a recent memefest)
———-
blog | exploring visually |
All the service in TYOC035 is still offline now?
I previously mentioned one of our IPv4 providers being upset regarding abuse reports. It seems like the situation is continuing to escalate even though we're doing everything we can to prevent it. We have increased minimum plan prices as you may have noticed on our site, to reduce abusive signups. We've had someone go through orders manually. Coinpayments was gotten rid of (coincidentally but we were considering it either way) and only Coinbase which has also reduced shady signups. We've replied to every abuse report, even the many duplicates that people like sending.
The provider is re-selling Cogent IPv4 which we were not initially aware of and implemented an abuse fee, I assume after Cogent did and with Cogent forwarding reports to this provider who forwards it to us, it slows down the process and adds in additional frustrating work for everyone I'm sure. We've paid for the fees even though initially we were told there'd be no other fees, which is fine.
Over the last 31 days, we've received a total of 40x IPv4 addresses reported, with the majority being poorly secured servers sending out attacks, with 59 additional duplicate emails. So this is 40 reported out of 32,768 IP block. I don't know if they truly believe 40 reports in a month on a /17 IPv4 block is excessive compared to other leases.
They've continued to threaten termination, usually after an abuse report they particularly do not like (something more serious, a few of these have occurred.)
I'm going to try to speed up IPv6 deployments and I'm hoping they are reasonable. I'm just providing this for the sake of transparency. It's obviously going to be very very bad if they decide to terminate that many IPv4 addresses and it would be difficult to replace them on short notice. I personally do not feel like this would be fair and we would of course have another company we would have to take to court over but I just wanted to paint a full picture/update for you guys here.
Please do not harass this company.
@VirMach ; i have a billing ticket #975541 , i will appreciate if it can be looked after soon. Thank you.
When will the migration plan of SJCZ004 be implemented. Can you help me with this order if it takes a long time. Thanks!
Ticket #461588
@VirMach
That is interesting. Some years ago providers were leery of crypto payments but a few took a chance on them and were pleasantly surprised to find very little abuse. I guess that didn't last. Thanks for keeping us informed.
They stopped doing business in the US and pretty much force closed our account in any case, but with that news, it means they're in some way possibly legally in trouble (this is just speculation) with the US compliance. And of course it's not that cryptocurrency is inherently bad or abusive, we've just noticed with Coinbase at least some criminals stopped using it as I assume that's in some way better logged and investigated for crimes (once again just speculation.)
I believe it's possible that we became one of the providers people preferred, and Coinpayments was ones of the payment methods they preferred, and it kind of combined together to create a negative situation.
@VirMach VPS has not been available since June. There is no information to know the progress of the processing.
Node: LA10GKVM14
The plan for the old nodes that failed is to at the very least refund everyone for the unused time since it went offline. We were discussing internally how we wanted to proceed in the coming days and once it's finalized, an announcement will be made, most likely via e-mail.
These were the nodes:
LAKVM9, LAKVM26, LA10GKVM14.
As far as I remember, they were all part of a mass power failure event that caused PSU to die and data was lost from RAID controller and other failures and/or human error by datacenter techs. Since these occurred at the worst possible time while we were doing everything else at peak workloads, and were already falling behind, it wasn't possible to work them into the schedule and I do apologize for it having taken such a long time (and the lack of official updates) but we have been working on it more recently. We haven't forgot about them.
@VirMach How about the TYOC035?
https://billing.virmach.com/serverstatus.php
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
@Virmach Purely being nosy, approx. how many Tickets are open, since the latest merging & closing?
(Might put things in perspective for some.)
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
This is an estimate as I don't have an exact figure for this anymore, but 2600-5000 tickets were "merged" into 1300-1500 tickets (as in some people made 2 tickets, some people made way more.)
We made approximately 5000 replies over the last 30 days, and approximately 5000 tickets were created over the last 30 days.
2,500 tickets were left over as of yesterday, and about 150 tickets created over the last 12 hours.
100 priority tickets were left over as of yesterday.
The majority of tickets are created between 6PM-8AM PST (Pacific Standard Time), which is between 1AM-3PM GMT (Greenwich Mean Time), or 9AM-11PM CST (China Standard Time.)
The following numbers match these keywords for remaining tickets:
We're going to try to clear out migration related tickets today, and refund requests. The current plan is to auto credit and close them for the stuck migrations. Then new migration requests will exclude Tokyo location selection and also have the new built-in auto credit system if it fails.
What provider (or at least what location(s)) so we will know that IP change is still on the cards there ;')
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png