Mini-guide: what to screenshot before opening any ticket

Mini-guide because I just watched a ticket go sideways for lack of evidence. Before you open any ticket with any provider, screenshot:

• Your control panel showing service status
• Your last payment confirmation
• Your current resource usage graphs
• Any error message in full (not cropped)

Memory-safe documentation practices matter. This is basically zero-cost abstraction for dispute resolution. Rewrite your habits in Rust, not chaos.

I also archive the page source because HTML can change. Zero trust applies to hosting support too.

$ yabs.sh -ig
fio test:
  read:  284 MB/s
  write: 197 MB/s
iperf3:
  send:    892 Mbits/sec
  recv:    734 Mbits/sec

Decent disk IO, meh network

Screenshot your benchmark dates too, providers "optimize" after tickets (I used https://github.com/masonr/yet-another-bench-script)

Back in source engine days we screenshot everything, tickrate disputes, wallbang evidence, admin abuse. Kids play valorant now, no demo system, no accountability. Same decay happened to hosting.

I still have 2007 forum posts archived on a P4. Screenshot your dns records too, theyll blame your config. Communities die when trust dies

And I learned this the hard way because I had a dispute with RackNerd back in march (or was it april, time blurs) and I opened the ticket with just "my site is down" and they came back with "works on their end" and then it was my word against theirs and I had no proof of what I was seeing and the error was intermittent (of course it was intermittent, they always are) and I spent three days going back and forth and they kept asking for more details and I kept providing different screenshots because the error kept changing and they used that against me saying I was changing my story and I lost a client over it (a real paying client, not a hobby site) and ever since then I screenshot everything before I even think about opening a ticket and I screenshot the ticket form itself before I submit and I screenshot their reply and I screenshot my reply and I keep it all in a folder named by date an

Cloud? Someone elses computer, someone elses rules. systemd journal logs vanish on reboot if you dont configure persistence. Screenshot your uptime before you reboot for their "troubleshooting" or youll never prove it wasnt you. DEC equipment never lied to you, just slowly failed in predictable ways