Support ticket diary
Day 1: ask Hetzner for php 8.2 bump
They say "we escalate" wey
Day 2: nothing?
Day 3: "still with tier 2" wey.
Day 4: I post in forum
Day 5: FIXED in two hours wey
Same company
Different speed when public wey
Make u think!
Support ticket diary
Day 1: ask Hetzner for php 8.2 bump
They say "we escalate" wey
Day 2: nothing?
Day 3: "still with tier 2" wey.
Day 4: I post in forum
Day 5: FIXED in two hours wey
Same company
Different speed when public wey
Make u think!
Actually this is Standard procedure for BudgetHosting, oder?
Internal ticket system versus Public relations priority. The Incentive structure changes when Reputation risk enters the Equation.
I documented same Pattern with InterServer last Year. ThreeWeeks via Email. TwoHours after ForumPost.
Not a Bug. A Feature of their Workflow.
1. This thread is useful
2. Let me document my similar experience
A) Hostinger
B) PHP 8.1 request
C) Timeline:
I) Ticket: 11 days
Ii) Forum post: 4 hours
Iii) Resolution: confirmed
3. Patterns observed
A) Private channel = slow
B) Public channel = fast
C) Not universal but common
4. Recommendations
A) Document everything
B) Escalate strategically
C) Keep records for future reference
"we escalate" = black hole
"still with tier 2" = one guy in a basement
"forum post" = CEO wakes up
Here we go again
Same with me in Vultr bro.
We make a test: ticket vs forum
Ticket: 9 days no answer
Forum: 1 day FIXED!
Is very good when work but the system is broken
They need to make internal same speed
I love when community help but hate when need shame to fix
Fun little project: I automated the escalation
#!/bin/bash
# post-to-forum.sh
# runs after ticket day 3
curl -X POST hostpeers.com \
-d "subject=PHP bump stuck" \
-d "body=Ticket #$1 pending ${2} days"It actually works
Three hosts now. Same pattern. Public pressure beats private patience.
Which PHP version did Hostinger finally give you?
Three hosts? Which ones, or you're not naming them
Same thing happened to me with a mysql bump.