Outage 13 October 2020
All Engaging Networks systems are now up and running again. We are waiting for an incident report from our data center and we’ll send this through to you as soon as possible.
We apologise for the inconvenience caused.
This has only caused issues for the Toronto server – US clients on the Dallas server will not be effected.
Most world regions are reporting that the block is removed and pages loading. We will send an email out once we can confirm all sites are ok.
A DDOS alert that automatically caused the block. Some sites are back online, but it is not fully restored yet.
A distributed denial-of-service (DDoS) attack occurs when multiple systems flood the bandwidth or resources of a targeted system, usually one or more web servers. A DDoS attack uses more than one unique IP address or machines, often from thousands of hosts infected with malware. Multiple machines can generate more attack traffic than one machine, multiple attack machines are harder to turn off than one attack machine, and that the behavior of each attack machine can be stealthier, making it harder to track and shut down. Since the incoming traffic flooding the victim originates from different sources, it may be impossible to stop the attack simply by using ingress filtering. It also makes it difficult to distinguish legitimate user traffic from attack traffic when spread across multiple points of origin. As an alternative or augmentation of a DDoS, attacks may involve forging of IP sender addresses (IP address spoofing) further complicating identifying and defeating the attack. These attacker advantages cause challenges for defense mechanisms. For example, merely purchasing more incoming bandwidth than the current volume of the attack might not help, because the attacker might be able to simply add more attack machines. https://en.wikipedia.org/wiki/Denial-of-service_attack#Distributed_DoS
We have been notified that there is a connectivity issue with Engaging Networks right now that is causing an outage for some clients in East Asia, Australia, New Zealand and the US west coast. This is affecting client pages and your ability to login to the platform.
We believe this has been occurring since 8.30am BST.
Our developers are working with our data center to assess and rectify the issue as soon as possible. We will provide a full explanation in a follow up email as soon as we have one. You can also check the Status Update page where we will post updates.
Recent software updates
We are continually adding new features to the software. The most recent update was on 3 October 2020. For further details on each of our updates, see the link to release notes in the related articles section on the right sidebar.
What we’re working on…
We are working on the next mini release in November.
The ability to edit and create legacy pages has been removed from the software. All pages should be created in the page-builder tools. Please Close any live pages. You can still view closed pages – click here for more. Legacy triggers are shut down. Please use marketing automations for that.
Following a Visa and MasterCard mandate for payment processors, we will now store an additional id for the transaction id. For clients using Worldpay, you will note a change in the gateway transaction ID (campaign data 2) in your Engaging Network’s Transactional Data, post this release. Worldpay transaction IDs moving forward will have 2 parts to them (paymentToken__networkTransactionId). The ‘3D Secure’ payment flow is now supported, through the PaySafe gateway. If you are interested in applying this for card processing feature, please reach out to support.
Engaging Networks disabled TLS 1.0 on 1st June 2018. If you and your supporters are using modern browsers, you do not need to do anything. For more information, click here.
Supportal pages to check out
Here are some recently created (or updated) pages in the Supportal that you may have missed:
Our team publish regular webinars on new features and best practice. You can watch the latest webinars here
If you need further assistance, please contact support