The Darkness
Expert Member
- Joined
- Sep 25, 2018
- Messages
- 4,417
- Reaction score
- 5,068
I am posting this to document my direct experience of Xneelo’s ongoing Johannesburg shared-server email incident and to establish how many other customers are affected.
Xneelo’s official incident record begins at 08:47 SAST on 1 September 2026:
https://xneelostatus.co.za/incidents/82f86958-7050-4cdb-a888-3f805de7e942
As of approximately 17:00 SAST on 3 September, the incident remains marked “Investigating”. Xneelo attributes the problem to a major operating-system upgrade that changed how background processes write data to its high-capacity email storage.
Its latest update, posted at 15:15, says that some background logging processes have been moved to faster storage and that further workloads are being migrated. It does not state that mail delivery has been restored, that the backlog is clearing, or when normal service will resume.
In my case, the service remains unusable for normal business purposes.
My experience includes:
Xneelo stated in its 10:07 update that all email remains queued and that no messages or data have been lost. I hope that is correct. From a customer’s position, however, that claim cannot be verified until the missing messages are delivered and mailbox contents become accessible again.
This is not a minor inconvenience. Businesses depend on email for instructions, approvals, quotations, orders, deadlines and contractual communication. Several days without dependable incoming or outgoing mail creates a real commercial risk.
I would like to hear from other affected customers.
Once the incident is resolved, Xneelo should publish a proper technical report covering the change-control process, testing, failure mechanism, recovery actions, actual customer impact, treatment of queued mail and steps taken to prevent a recurrence.
Based on what I have personally experienced and documented, the handling of this incident has been unacceptable for a business email service.
Xneelo’s official incident record begins at 08:47 SAST on 1 September 2026:
https://xneelostatus.co.za/incidents/82f86958-7050-4cdb-a888-3f805de7e942
As of approximately 17:00 SAST on 3 September, the incident remains marked “Investigating”. Xneelo attributes the problem to a major operating-system upgrade that changed how background processes write data to its high-capacity email storage.
Its latest update, posted at 15:15, says that some background logging processes have been moved to faster storage and that further workloads are being migrated. It does not state that mail delivery has been restored, that the backlog is clearing, or when normal service will resume.
In my case, the service remains unusable for normal business purposes.
My experience includes:
- Incoming mail arriving sporadically or not arriving.
- An outgoing test message sent to my personal Gmail account at 08:44 still not delivered many hours later.
- Apple Mail reporting that the IMAP APPEND command to the Sent mailbox failed because the server timed out while waiting for a lock.
- Apple Mail becoming stuck on “Moving Messages 4 of 11”.
- Xneelo webmail failing to display the Sent-mail contents correctly.
- Mailbox contents and recent messages not synchronising reliably.
Xneelo stated in its 10:07 update that all email remains queued and that no messages or data have been lost. I hope that is correct. From a customer’s position, however, that claim cannot be verified until the missing messages are delivered and mailbox contents become accessible again.
This is not a minor inconvenience. Businesses depend on email for instructions, approvals, quotations, orders, deadlines and contractual communication. Several days without dependable incoming or outgoing mail creates a real commercial risk.
I would like to hear from other affected customers.
Once the incident is resolved, Xneelo should publish a proper technical report covering the change-control process, testing, failure mechanism, recovery actions, actual customer impact, treatment of queued mail and steps taken to prevent a recurrence.
Based on what I have personally experienced and documented, the handling of this incident has been unacceptable for a business email service.
