@VirMach said: (Edit2) I just went through all of them, they're ALL the same as last time.
Just ask them where is the legacy legacy ticket system that you need to answer for those because seems like answering via legacy ticket system is not enough, not even talking about current ticket system.
Please someone read what I posted, this is just one instance of us answering them, let me know if it's unclear. I explained everything thoroughly, no? If you disagree then feel free to critique it and let me know how it should be done instead. Was it not clear? If it wasn't let me know and I'll pull up some other times we answered them so we can see if those are clear.
I find that when people keep asking me for the same thing over and over again it is normally not because I was previously unclear, but because I did not tell them what they wanted to hear.
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
Tagging you @yoursunny since one of their C-level people tried to insinuate that we don't handle abuse reports.
Since I don't have time to screenshot everything, this is the case for the first IP address I posted the screenshot to earlier, let's go step by step.
The IP: 47.87.220.105
We respond to this ticket.
We get an email from a random email from someone's Hivelocity email, not from their ticket system or support email. Keep in mind I don't have much time so it's possible they're slightly off chronological order.
We receive another copy.
We receive a confirmation it has been closed.
The same person that confirmed it as resolved a day ago makes a new request.
We receive another copy of his new message from another email.
Someone else chimes in.
Someone else chimes in referencing all the tickets they made about this including the one where they confirm it is resolved. We respond again.
Then all the other stuff happens you guys already know about.
(edit) Remember, this is all for one instance of abuse, that was handled at the beginning. It doesn't include the follow-up emails we get asking to rate them and such.
@VirMach said:
Tagging you @yoursunny since one of their C-level people tried to insinuate that we don't handle abuse reports.
Since I don't have time to screenshot everything, this is the case for the first IP address I posted the screenshot to earlier, let's go step by step.
The IP: 47.87.220.105
We respond to this ticket.
We get an email from a random email from someone's Hivelocity email, not from their ticket system or support email. Keep in mind I don't have much time so it's possible they're slightly off chronological order.
We receive another copy.
We receive a confirmation it has been closed.
The same person that confirmed it as resolved a day ago makes a new request.
We receive another copy of his new message from another email.
Someone else chimes in.
Someone else chimes in referencing all the tickets they made about this including the one where they confirm it is resolved. We respond again.
Then all the other stuff happens you guys already know about.
We're going to try something different for NYC changes. When we make tickets it spams people and in this case there's no advanced notice on the IP change really, we already sent out an email asking to check status page and provided updates there.
There will be a pop-up you can't get rid of when you load your service details page instead telling you what happened.
Tracing route to tailscale.com [76.223.15.28]
over a maximum of 30 hops:
1 2 ms 4 ms 5 ms 46.233.44.1
2 11 ms 20 ms 20 ms 172.16.0.0
3 <1 ms <1 ms <1 ms hosted-by.royalehosting.net [45.59.169.176]
4 <1 ms <1 ms <1 ms 223.165.7.148
5 <1 ms <1 ms <1 ms po1.nyc-eqxny2-bb1.globalsecurelayer.com [206.148.25.61]
6 <1 ms <1 ms <1 ms ny.gslnetworks.com [198.32.118.59]
7 * * * Request timed out.
8 * * * Request timed out.
9
@hike said:
NY routing not going well lot of ASN unreachable.
Tracing route to tailscale.com [76.223.15.28]
over a maximum of 30 hops:
1 2 ms 4 ms 5 ms 46.233.44.1
2 11 ms 20 ms 20 ms 172.16.0.0
3 <1 ms <1 ms <1 ms hosted-by.royalehosting.net [45.59.169.176]
4 <1 ms <1 ms <1 ms 223.165.7.148
5 <1 ms <1 ms <1 ms po1.nyc-eqxny2-bb1.globalsecurelayer.com [206.148.25.61]
6 <1 ms <1 ms <1 ms ny.gslnetworks.com [198.32.118.59]
7 * * * Request timed out.
8 * * * Request timed out.
9
It'll be like this until the prefixes are RPKI validated. Basically Dedipath is still announcing the blocks even though they're not supposed to, and because of this some carriers that filter invalid RPKI will drop you at the edge. https://isbgpsafeyet.com/ explains this a little better than I am. This is also why some of Dedipath's IPs were accessible even though they were taken back by the prefix owners.
@hike said:
NY routing not going well lot of ASN unreachable.
Tracing route to tailscale.com [76.223.15.28]
over a maximum of 30 hops:
1 2 ms 4 ms 5 ms 46.233.44.1
2 11 ms 20 ms 20 ms 172.16.0.0
3 <1 ms <1 ms <1 ms hosted-by.royalehosting.net [45.59.169.176]
4 <1 ms <1 ms <1 ms 223.165.7.148
5 <1 ms <1 ms <1 ms po1.nyc-eqxny2-bb1.globalsecurelayer.com [206.148.25.61]
6 <1 ms <1 ms <1 ms ny.gslnetworks.com [198.32.118.59]
7 * * * Request timed out.
8 * * * Request timed out.
9
It'll be like this until the prefixes are RPKI validated. Basically Dedipath is still announcing the blocks even though they're not supposed to, and because of this some carriers that filter invalid RPKI will drop you at the edge. https://isbgpsafeyet.com/ explains this a little better than I am. This is also why some of Dedipath's IPs were accessible even though they were taken back by the prefix owners.
@JoeMerit said:
What does that mean? I have ATL & DEN servers. Does that mean youve restored them to another DC? You said LAX for DEN, where would you move ATL?
I'm not spending a lot of time on this, but from one of the many systems I have that are unreachable, you're probably seeing this:
Notice the "RPKI State Invalid" part. You might get partial reachability behind those networks that don't enforce ROV (route origin validation), which is a relatively small portion of the entire Internet these days when you're a low-end provider. In a word, routing is FUBAR'd until the cooperating parties are in sync on who can legitimately announce what and populate the respective IRRs and RPKI repository with that info.
If you have your own address space, you're not at the mercy of third party address brokers, but presumably that is not an easy/cheap solution. But, it is something I increasing pay attention to these days or ask about.
@VirMach said:
Since I don't have time to screenshot everything, this is the case for the first IP address I posted the screenshot to earlier, let's go step by step.
This reminds me of most of my conversations with providers about IPv6 issues.
Comments
Just ask them where is the legacy legacy ticket system that you need to answer for those because seems like answering via legacy ticket system is not enough, not even talking about current ticket system.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
Please someone read what I posted, this is just one instance of us answering them, let me know if it's unclear. I explained everything thoroughly, no? If you disagree then feel free to critique it and let me know how it should be done instead. Was it not clear? If it wasn't let me know and I'll pull up some other times we answered them so we can see if those are clear.
I find that when people keep asking me for the same thing over and over again it is normally not because I was previously unclear, but because I did not tell them what they wanted to hear.
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
Tagging you @yoursunny since one of their C-level people tried to insinuate that we don't handle abuse reports.
Since I don't have time to screenshot everything, this is the case for the first IP address I posted the screenshot to earlier, let's go step by step.
The IP: 47.87.220.105
We respond to this ticket.
We get an email from a random email from someone's Hivelocity email, not from their ticket system or support email. Keep in mind I don't have much time so it's possible they're slightly off chronological order.
We receive another copy.
We receive a confirmation it has been closed.
The same person that confirmed it as resolved a day ago makes a new request.
We receive another copy of his new message from another email.
Someone else chimes in.
Someone else chimes in referencing all the tickets they made about this including the one where they confirm it is resolved. We respond again.
Then all the other stuff happens you guys already know about.
(edit) Remember, this is all for one instance of abuse, that was handled at the beginning. It doesn't include the follow-up emails we get asking to rate them and such.
I dun't knows nuffin and it is better that way.
Free Hosting at YetiNode | Cryptid Security | URL Shortener | LaunchVPS | ExtraVM | Host-C | In the Node, or Out of the Loop?
Bonus, I like this email I just sent out like 30 minutes ago.
I genuinely started highlighting them to see what new report was there to handle it and then this happened.
But... you should colour code group the same ticket numbers together!
How is he supposed to figure it out if everything is red. :-D
Oh update, I didn't handle this and I've been too busy to check communications.
ATLZ006, ATLZ005, DENZ001 and partial DENZ002 have been loaded in from backups.
Not sure red was a good color choice.
I'm thinking of things like:
Making them see red
Waving a red cloth in front of a bull
We're going to try something different for NYC changes. When we make tickets it spams people and in this case there's no advanced notice on the IP change really, we already sent out an email asking to check status page and provided updates there.
There will be a pop-up you can't get rid of when you load your service details page instead telling you what happened.
My VPS in San Jose is offline, I love the node and I'll wait quietly for it to come back online.
Some praying might help too.
I can imagine this gonna be perfect for mobile users - whole screen ruined.
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
Operation Timed Out After 90001 Milliseconds With 0 Bytes Received
What does that mean? I have ATL & DEN servers. Does that mean youve restored them to another DC? You said LAX for DEN, where would you move ATL?
NY routing not going well lot of ASN unreachable.
Tracing route to tailscale.com [76.223.15.28]
over a maximum of 30 hops:
1 2 ms 4 ms 5 ms 46.233.44.1
2 11 ms 20 ms 20 ms 172.16.0.0
3 <1 ms <1 ms <1 ms hosted-by.royalehosting.net [45.59.169.176]
4 <1 ms <1 ms <1 ms 223.165.7.148
5 <1 ms <1 ms <1 ms po1.nyc-eqxny2-bb1.globalsecurelayer.com [206.148.25.61]
6 <1 ms <1 ms <1 ms ny.gslnetworks.com [198.32.118.59]
7 * * * Request timed out.
8 * * * Request timed out.
9
It'll be like this until the prefixes are RPKI validated. Basically Dedipath is still announcing the blocks even though they're not supposed to, and because of this some carriers that filter invalid RPKI will drop you at the edge. https://isbgpsafeyet.com/ explains this a little better than I am. This is also why some of Dedipath's IPs were accessible even though they were taken back by the prefix owners.
tldr give it a little bit
Thanks, let see how fast they get validated.
VirMach'd fast!
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
alright bro. hope data is safe
I'm not spending a lot of time on this, but from one of the many systems I have that are unreachable, you're probably seeing this:
Notice the "RPKI State Invalid" part. You might get partial reachability behind those networks that don't enforce ROV (route origin validation), which is a relatively small portion of the entire Internet these days when you're a low-end provider. In a word, routing is FUBAR'd until the cooperating parties are in sync on who can legitimately announce what and populate the respective IRRs and RPKI repository with that info.
If you have your own address space, you're not at the mercy of third party address brokers, but presumably that is not an easy/cheap solution. But, it is something I increasing pay attention to these days or ask about.
Dataplane.org's current server hosting provider list
5 more months and I'm VirTrash free ! inshallah!
↪️ Service Transfers
You can get rid of VirmAche faster.
HostBrr aff best VPS; VirmAche aff worst VPS.
Unable to push-up due to shoulder injury 😣
This reminds me of most of my conversations with providers about IPv6 issues.
dnscry.pt - Public DNSCrypt resolvers hosted by LowEnd providers • Need a free NAT LXC? -> https://microlxc.net/
I like to feel the pain for a few months
NYCB022 can be acessed via VNC but i cant ping in or out, should i try the fix network button?
Better off fixing it manually, IME, due to network interface naming - especially if you use static IP, which you should on a server.
[Edit for clarity.]
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
didn't worked for me
LMFTFY
See above.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)