VPS Infrastructure Improvements

We are pleased to confirm we have now upgraded our virtualisation platform, allowing us to provide you a far greater level of control from our client area for managing your VPS / Cloud servers.

We have also changed our pricing structure for VPS servers - the reason for this is that we wanted our VPS solutions to be entirely scaleable, rather than restricted to a certain number of 'packages'.

The changes have been made live to our website.

We will be working on releasing compute resource in Chicago within a few weeks time, allowing you to purchase VPS servers in the UK or the USA.

Elastic Cloud Upgrades

We have now rolled out an improved Elastic Cloud infrastructure, which is based on NVMe storage.

We have also removed any previous LVE limits from the Elastic Cloud plans, and have instead focused on limiting solely by storage / domains.

PHP Versions 'Auto Changing'

We had a number of tickets raised by clients stating that their PHP versions were 'reverting' periodically.

After thoroughly investigating the issue, we have found that this issue is isolated to accounts which have been migrated from other hosting providers which specifically make use of the MultiPHP Manager in WHM / cPanel.

At Brixly, we don't use the MultiPHP Selector throughout, allowing us to make use of the 'PHP Selector' which is bundled with the Cloudlinux product.

The investigation led us to notice that the MultiPHP configuration was being migrated from the previous provider, ignoring the global 'disable' of this functionality on our own servers.

We have raised this with cPanel, who confirmed they believe this to be a bug, however we have deployed a solution internally to resolve the issue.

We have added a 'post restore' cPanel hook, which now resets the PHP Version to 'Inherit', allowing the account to make full use of the Cloudlinux PHP Selector as intended.

This script is publicly available hereā€¦


The fix has now been deployed to all servers.

Default PHP Version - Increased to 7.2

New accounts will now use PHP 7.2 as the default version of PHP, and can still be changed via the usual PHP Selector in cPanel.

DKIM Support via MailChannels

DomainKeys Identified Mail (DKIM) is an email authentication method designed to detect forged sender addresses in emails (email spoofing), a technique often used in phishing and email spam.

DKIM allows the receiver to check that an email claimed to have come from a specific domain was indeed authorized by the owner of that domain. It achieves this by affixing a digital signature, linked to a domain name, to each outgoing email message. The recipient system can verify this by looking up the sender's public key published in the DNS. A valid signature also guarantees that some parts of the email (possibly including attachments) have not been modified since the signature was affixed. Usually, DKIM signatures are not visible to end-users and are affixed or verified by the infrastructure rather than the message's authors and recipients.

We have now implemented DKIM support via the MailChannels outbound SMTP relay on all servers.

Sending Limits and Mail Improvements

We have recently applied a number of changes surrounding email deliveries.

Previously, we routed all outbound mail sent via the SMTP protocol through MailChannels, ensuring that all SMTP messages were delivered to the end users / recipients.

However, one thing we noticed over the span of several months was that much of the 'SPAM' relayed via the PHPMail() protocol caused a number of our IP addresses and subnets to be 'blacklisted' - to combat this, we have reinvested significantly to now route all outbound mail through MailChannels, so that we can benefit from the outbound SPAM filtering that bundles with the solution.

In turn, this has allowed us to ensure that the IP addresses in our subnets are far less likely to be blacklisted.

We still highly recommend using the SMTP protocol for relaying all messages however, as its still possible for mail sent via PHPMail to be treated as SPAM - not due to the impact of blacklists, but instead due to the way the 'envelope senders' are relayed.

Additionally, we have increased our outbound sending limits per-account to 150 from the previous 100.

New Website Launched

We are pleased to announce the release of our new website, which has been several months in the making!

Whilst our previous website wasn't particularly 'old', we felt that a new update was required to freshen up our growing brand.

We have had some fantastic feedback since the release of the new website. Improvements and changes will be ongoing for the next few months.

Support Escalations

We have spent several months discussing ways to improve our already awesome technical support handling.

To ensure that your support enquiries are handled as efficiently as possible and to improve our response times overall, we have added a new member to the team who will be working throughout the evenings here. Shaz will be readily available and handling support enquiries in our front-line queue alongside our senior team.

We also have added the option to 'Escalate' a ticket to the Senior Support department, which will ensure that the ticket is handled exclusively by our Senior engineers - please note though, abuse of this facility is recorded and monitored.

Our front-line staff handle 93% of support enquiries 24 hours a day and are experienced cPanel certified engineers, however we have now extended our Senior Engineer availability to 12 hours daily, 9am until 9pm instead of 9am - 5.30pm weekdays.

Senior staff availability is 24/7 for server-wide / emergency related cases.

We're starting a changelog

Big news today, we're starting a public changelog so you're always up to date with all the updates, improvements and fixes that are made in Brixly.

Even though we work on Brixly all the time, sometimes it may seem that not much is happening. This changelog is here to improve that very important part of the communication between you and us.

You'll always receive an update when we change something in the widget, or if needed all things we've changed is available on our public changelog page.

Here's to an incredible 2020!