Decorative SLA. I'm stealing that.
I use DigitalOcean for personal stuff. No latency SLA at all. Just "we try." More honest than this backbone/backdoor nonsense.
Your latency SLA excludes the route you actually use
steveipw
Member OP
I should have stayed with my gut. The rep actually said "most customers don't notice the difference." I'm a video editor. I notice 34 ms when my proxy streams stutter. That's why I read the SLA three times.
Next time I'll read it four times and still get fooled, apparently.
zfs send | zfs receive. repeat.
This thread saved me. Was about to sign similar deal. What monitoring tool you all use for MTR? I need something that logs 24/7 for evidence.
manish60 said:
What monitoring tool
SmokePing. Run it on a box you trust, not theirs. Log everything. They will ask for their tool, their method, their window. Have your own.
Also: screenshot the SLA page. They change.
seedbox, NAS, tape, and three offsite
steveipw
Member OP
They already changed it. My original ticket quoted "designated metro pairs." Now the public doc says "designated backbone paths between metro pairs." One word different, whole meaning shifted. Good thing I saved the PDF.
This is what we're dealing with.
zfs send | zfs receive. repeat.