Dual Infrastructure Collapse: Home-Connect Billing Breach & Vumatel Layer 3 Packet Loss

I'm logging this publicly to formally register a critical service and billing failure involving Home-Connect (***) and their underlying Fibre Network Operator, Vumatel. Despite weeks of documented escalations, formal credit negotiations, and technical telemetry handed to both companies on a plate, I'm now sitting 48 hours away from an imminent billing breach on Monday, 1 June 2026 — with packet loss that's been crippling my 200 Mbps line during peak hours still completely unaddressed.

1. THE BILLING BREACH & ACCOUNT ***** RISK (Home-Connect) Here's the timeline, because it matters:

Tuesday, 26 May 2026 (12:28 PM): Home-Connect Accounts offered an initial internal router dispatch delay credit of -R415.00 plus a -R199.00 delivery fee waiver. I disputed this immediately. My own pro-rata calculations showed the credit should be higher given the full 15-day capping period. Thursday, 28 May 2026 (16:32 PM): I sent Princess and Accounts an itemized pro-rata breakdown establishing my audited timeline and pushing for the corrected credit of -R514.00 for the hardware delay, alongside my separate regional blackout deductions. Friday, 29 May 2026 (16:15 PM): I sent a formal reconciliation summary to Princess and Accounts confirming that the combined hardware credits (-R514.00 + -R199.00 waiver) brought my finalized, agreed balance due for 1 June 2026 to exactly R415.00. Saturday, 30 May 2026 (11:05 AM): Princess (Client Critical Care Management) sent a final written email confirmation explicitly approving the -R514.00 hardware delay credit and the -R199.00 shipping waiver, confirming my adjusted liability as R415.00 against what was originally a R1,128.00 invoice.

That's R713.00 in total approved adjustments. In writing. From management. Home-Connect's billing system still hasn't been updated. If a single cent over R415.00 is debited on Monday morning, I will immediately execute a formal bank reversal and file billing violation claims with ICASA and the Ombud for Electronic Communications. That's not a threat — that's the next step.

2. THE TECHNICAL INFRASTRUCTURE COLLAPSE (Vumatel & Home-Connect) While Vumatel logged a physical layer blackout on Tuesday, 26 May 2026 at 14:50 PM (FNO Ticket #***0) and hastily marked it "resolved," severe Layer 3 routing defects remain actively disputed. Traceroute diagnostics I captured on Thursday, 28 May 2026 at 18:37 PM conclusively prove severe packet loss and repeated request timeouts originating at Hop 2 (100.127.129.118) — the Home-Connect Edge Gateway.

The Failure of Vumatel Maintenance: As I escalated directly to Vumatel Maintenance via Angelar on 29 May, their standard morning network snapshots are completely missing these drops. I personally logged five distinct routing collapses overnight. Their diagnostic protocols are blind to peak-hour edge gateway congestion — and they need to own that. Where Home-Connect Stands: They've committed to provisioning a direct dial-up connection to run continuous ping tests and isolate the exact hop failure origin. That's the right call. It still needs to actually happen.

3. ACTIVE TICKETS & INFRASTRUCTURE LOGS Ticket / ReferenceInternal DesignationStatusTicket #*** [O2TNUFV]Home-Connect Accounts ThreadTracks the financial credit negotiation, R713.00 total adjustments, and the final R415.00 manual billing overrideTicket #*** [NRS2V7O]Home-Connect Critical CareActive technical escalation — intermittent drops, edge gateway issues, pending dial-up diagnosticsFNO Ticket #***0Vumatel InfrastructurePhysical blackout logged 26 May at 14:50 PM, marked "resolved" at physical layer — Layer 3 routing remains open and disputed

4. PERSONNEL ON FILE

Princess — Client Critical Care / Senior Escalations, Home-Connect. Primary contact for the hardware delay dispute. She authorized the credit increase to -R514.00 and the -R199.00 waiver in writing on Saturday morning. Angelar — Vumatel Maintenance Liaison / Home-Connect Tech Team. Received my traceroute telemetry on 29 May and escalated the five overnight routing collapses directly to Vumatel's backend maintenance desk. Home-Connect Accounts Team — Handled initial ticketing communications from 26 May before Princess pulled the file into Critical Care.

Final Notice: I'm holding back my full archive of network logs, traceroute screenshots, and written credit approvals for now. If my account is incorrectly debited on Monday, or if Home-Connect and Vumatel keep passing the buck on this Hop 2 routing failure, everything goes up — publicly — alongside immediate escalation to ICASA, ISPA, and the Ombud. Two things need to happen before Monday morning: manually override the billing batch to R415.00, and get an actual engineer looking at that edge gateway routing. Both are documented, both are agreed. There's no reason they shouldn't already be done.

To be absolutely clear: if my account is debited by a single cent more than the agreed and written-confirmed amount of R415.00 on Monday, 1 June 2026, I will be taking the following actions simultaneously and without further notice:

ISPA (Internet Service Providers' Association of South Africa) — formal member conduct complaint against Home-Connect for billing in direct violation of a written credit agreement ICASA (Independent Communications Authority of South Africa) — regulatory billing violation filing under the Electronic Communications Act My Bank's Dispute & ***** Department — immediate debit reversal instruction, flagged as an unauthorised transaction given that the correct agreed amount is already on record in writing

I have dated, timestamped, written confirmation from Home-Connect's own Critical Care management. Any debit above R415.00 isn't a billing error — it's an unauthorised transaction against a formally agreed balance. I will treat it accordingly.