Skip to content

Your latency SLA excludes the route you actually use

Networking by steveipw 24 replies 1.8K views
#11
hankels said:
Honesty is a feature

This. In Jakarta I resell Hostinger and UpCloud. Hostinger tells customer "Jakarta to Amsterdam 180 ms" before they pay. No appendix needed.

traffic worse than my packet loss
9 #12

I run BGP to two upstreams in Moscow. The idea that a provider can promise latency on a path they don't control is fantasy. They should say "we guarantee nothing past our border" like honest people.

#13

They do control it though. That's the thing. East-1 to Central-2, they own both ends. They just choose to route me via cheap peering instead of their own backbone to save money. The backbone exists. They built it. They just don't let my traffic use it for the SLA they sold me.

zfs send | zfs receive. repeat.
#14

This is the "best effort" dressed in a tuxedo. In Budapest we have a word for this.

#15

I moved a client from Frankfurt to Istanbul last month. Same provider, same "backbone SLA," actual latency doubled because they started routing via Bucharest. Ticket answer: "network optimization in progress." Three weeks now. No optimization, no SLA credit.

The only SLA that matters is the one you can measure and they can't redefine.

7 #16

Running game servers since 2003, latency is everything. My players feel 20 ms. They ragequit at 40. I use OVH now, their SLA is vague but at least the routes are consistent. Glasgow to Gravelines: 18 ms every time. I'll take predictable over promised.

#17

Appendix Z is where they hide the bodies. And the bodies are your packets.

#18
JokoNord said:
Hostinger tells customer "Jakarta to Amsterdam 180 ms" before they pay

Same here bungkus, I also reseller in Jakarta. Hostinger clear about latency, UpCloud also clear. The "legacy" excuse is only for companies too big to care about small customer. My warung clients don't read SLA but I do, for them.

wrap it, ship it, pray it
#19

Has anyone actually won a latency SLA claim? Like, documented proof, got paid? I tried with AWS once, they wanted 30 days of MTR from both ends with their specific tool. I gave up.

#20
Paul623 said:
Won a latency SLA claim

Never. I have the spreadsheet. Zero payouts in 4 years across 7 providers. Two credits offered, both "goodwill" not "SLA breach." They'd rather give $20 credit than admit fault.

My new rule: if the SLA has more than 3 definitions, it's decorative.

seedbox, NAS, tape, and three offsite

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft