Skip to content

Your status page is always green

General Discussion by nate_pad 25 replies 2.3K views
#11
nate_pad said:
Their Singapore page stayed green the whole time.

UpCloud runs their own gear, not rented cages. That makes it worse because they have no upstream to blame. Their status page pulls from internal monitoring. If internal monitoring cannot reach the public internet, it should say so. "Green" means their Nagios or whatever can ping the gateway. Not that you can.

I have seen this with OpenVZ, with KVM, with VMware. The hypervisor layer is irrelevant. The monitoring topology is what matters.

virsh list --all | wc -l: 47
9 #12
kate3 said:
Same. Status page stayed green through three hours of 80% loss.

Who was yours? I am trying to figure out if this is industry-wide or specific tiers. Mine was a budget managed VPS in New Jersey. Not naming because their lawyers are awake.

grabs popcorn, checks /r/drama
2 #13

I run a small hosting thing in Tallinn. Our status page is a lie and I will say it. We mark "degraded" when our single external monitor from Hetzner FSN sees packet loss above 10% for 5 minutes. But we only have one external monitor. If the FSN route is clean and the Frankfurt route is on fire, green page. I am not spending 50€/month on distributed monitoring for a 200€/month revenue operation. The economics are broken.

https://status.hetzner.com

#14
sven said:
I am not spending 50€/month on distributed monitoring

Then your status page should say "best effort monitoring from single point" not "all systems operational." The lie is not the green light. The lie is the implication of coverage.

/dev/null: full of good ideas
#15

In Denmark we have a consumer protection thing about this. If you sell "99.9% uptime" and your status page is the proof, the page itself becomes a marketing claim. Ombudsman has fined two small hosts for status pages that did not reflect actual availability. I do not know if it applies to VPS outside EU consumer sales but the principle is there.

#16
JohnBlu said:
Ombudsman has fined two small hosts

I used to write those tickets. "Your status page says green but my site is down" was maybe 15% of first responses. Standard reply: "Our monitoring shows no issues, please check your local connection." Second reply from us, if they pushed: "We see intermittent routing, no action required." Third reply: actual escalation. Most people gave up at one. The status page existed to reduce ticket volume, not to inform. I left because I got tired of lying by template.

Single mode till I die 💀
#17

I run ARM64 nodes in Seoul. My provider is a local company, not global. Their status page is literally a text file updated by hand when someone calls the NOC. More honest than automated green. At least you know nobody looked.

one small ping for man...
6 #18

This. I would rather see "last updated 14 days ago" than a dashboard of fake precision.

#19
Nadia said:
They cannot ignore what others see

They ignored it. KnownHost support said my page was "causing confusion" and asked me to add a disclaimer that it was "unofficial." I added "unofficial independent monitoring" in big letters. They stopped replying. My 5€ CloudCone VPS in LA keeps checking their Dallas and Amsterdam locations. Dallas has had three "degraded" periods my page caught, theirs missed. Amsterdam has been stable on both.

#20

How do you handle false positives? I tried uptime-kuma on a Contabo VPS checking OVH and got alerts every time OVH did maintenance on their anti-DDoS scrubbing. The service was not down, just shifted. My page looked like crying wolf.

Post a reply

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

Post reply Preview Save draft