15 Years of Loyalty, Destroyed in a month: Data Loss, Silence, and Zero Accountability
TL;DR: 15 years as a customer. They destroyed a client’s website, misled me for 23 days, blocked my support access mid-incident, and refused accountability. ACCC complaint ready. QCAT claim coming.
If you’re considering Digital Pacific, understand the risk. If something breaks, there’s a real chance no one answers calls or tickets, your incident gets marked low priority, and any eventual response may be incorrect. Your site could stay down for weeks. If you escalate, your support access may be removed while issues remain open. When you push for accountability, it may be dismissed as routine maintenance and your losses treated as your problem.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
I was with Digital Pacific for 15 years and referred over a dozen clients. This is what that meant:
In early March 2026, I found my shared hosting was running on infrastructure that reached end of life in 2020, with no security patches for years. I raised it expecting a routine upgrade. Support told me modern Node.js could not run on shared hosting and pushed me toward higher cost plans. That was false. Their own staff later confirmed they already run modern shared hosting capable of current software, and acknowledged the conflicting info in writing.
In the same ticket, I was told migration to modern shared hosting would cost $99. Also false. It was later confirmed migrations under their upgrade program were free. That was not disclosed when the fee was raised.
Digital Pacific then promised in writing both my accounts would be migrated at no cost and I’d receive advance notice before either move.
What happened: a stable client site was migrated with no formal notice. The only mention was a side note buried in a reply on a thread I could no longer respond to. The migration failed. The database was destroyed. The site went down. Digital Pacific did not tell me the migration occurred, failed, or that the database was gone. I found out when my client reported the outage nearly a week later.
Support then collapsed.
I raised a Critical ticket. No action for 35 hours. The first reply was boilerplate. No timeline, no cause, no acknowledgment of deadlines I’d set. Just “we’re working on it” from a provider that had already contradicted itself.
The day I learned the site was down, I called and was put on hold for 1 hour 13 minutes before disconnecting. I simultaneously opened a Chat in their website that ran 3 hours 15 minutes without any response before auto closing for “no response detected,” framing their silence as my failure.
On a CRITICAL issue...
I sent formal notice: restore the database by a set deadline or I’d be forced to perform emergency rebuild work and bill them. Deadline passed. No response. No restore attempt. No contact.
Every ticket in this period had at least a 24 hour delay before any reply. Some as long as a week. Critical issues, data loss, formal escalations... same result.
When replies did arrive, they were dismissive, inconsistent, or wrong. One staff member saw the temporary landing page I built because the real site was gone, confirmed it loaded, and considere the issue resolved. They did not check the database or actual functionality. They treated a placeholder, created due to their failure, as proof everything was fine. That pattern repeated. Poor assumptions, incorrect responses, and even when I replied immediately, I waited another 24 hours or more.
When I requested a refund, they redirected the ticket to an unrelated thread and marked it answered. No mention of a refund. No acknowledgment at all.
At no point did Digital Pacific accept responsibility. Not for false statements, the failed migration, the destroyed database, weeks of non response, removal of support access, or the unauthorized change to my account email while I had no access and active complaints open.
They repeatedly claimed in writing the database was restored while the site showed a database connection error for 14 days after the first claim. Actual restoration occurred on 4 April 2026... 23 days after the failure.
I have an ACCC complaint prepared and am pursuing recovery via QCAT. I’ve retained full ticket history, all correspondence, invoices, and written admissions.
15 years. Over a dozen referrals. This is the outcome.
18 March 2026
Unprompted review