All Systems Operational
Applications & API Operational
Main Platform & API ? Operational
New Platform Features ? Operational
Insights Reporting Operational
Keyword Search Operational
Processing & Workflow Operational
Background Processing ? Operational
Workflow Processing Operational
Email & SMS Operational
Outbound Email Operational
Inbound Email Operational
Outbound SMS Operational
Inbound SMS Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Support for TLS 1.0 ending Apr 13, 21:00-21:15 BST
** What is happening? **

FLG will stop supporting TLS 1.0. From this time, any request to FLG using TLS 1.0 will fail.

** What is TLS 1.0? **

TLS stands for Transport Layer Security. TLS is a cryptographic protocol that provides authentication and data encryption between different endpoints (for instance, a client connecting to a web server). New versions of TLS have been released to address vulnerabilities and support the strongest and most secure cipher suites and algorithms.

** Why are you doing this? **

It is best practice to configure all systems communicating with FLG to support the latest protocol version possible. We currently support TLS 1.2. Continuing to support old versions of the protocol can leave you vulnerable to attacks.

Industry experts have recommended disabling TLS 1.0 for a while now due to various vulnerabilities, but this current initiative is being driven by an improvement we are making to our infrastructure which will stop us supporting TLS 1.0.

You can already use TLS 1.2 (and TLS 1.1), it's just that we're making this mandatory.

** Will it affect me? **

We have sent targeted communications to all affected customers and will continue to capture requests to identify all affected customers.

** What do I need to do? **

If you still use TLS 1.0, identify the system sending data to FLG using TLS 1.0 and then carry out the necessary steps to stop sending data using TLS 1.0 and instead send using TLS 1.2.

There are various places where you might find requests to FLG using TLS 1.0:

- From your website (including Web Form, iFrame and API integration methods) and other systems that post into FLG.
- In requests to the FLG API within code you've written for your plugins or webhooks.

It's important that you audit your systems carefully.
Posted on Mar 3, 15:27 GMT
Past Incidents
Apr 3, 2020

No incidents reported today.

Apr 2, 2020

No incidents reported.

Apr 1, 2020
Resolved - This incident has been resolved. The re-sync is complete and all files are now available. If you see any further issues then please let us know.

Sorry again for the disruption this will have caused you and your customers this morning.
Apr 1, 14:44 BST
Update - We have completed the file re-sync mentioned earlier and are currently verifying the results. We will provide an update in the next 60 minutes.
Apr 1, 13:48 BST
Update - We are continuing to monitor for any further issues.
Apr 1, 11:52 BST
Monitoring - The issues seen with emails and attachments are a result of a change we made to file handling last night. We have reversed this change whilst we investigate and resolve the remaining issues.

You may have seen emails with attachments not being sent to the dropbox, inbound emails with attachments not appearing on the lead, problems adding attachments to email templates and attachments not showing on emails. Only emails with attachments were affected.

We are currently completing a re-sync on files created in the system, including email attachments, between 22.00 last night (Tuesday 31st March) when the change was made and 11.40 today (Wednesday 1st April) when it was reversed. Until this is completed, you may continue to see the above problems. We'll tell you once everything is back to normal.

We’re really sorry to disrupt the start of your day. We will update you in the next 120 minutes with an update on the re-sync of files.
Apr 1, 11:51 BST
Identified - The issue has been identified and a fix is being implemented. We will update you in the next 60 minutes with the latest information.
Apr 1, 10:26 BST
Update - The team is continuing to investigate this problem as a top priority. We will update you in the next 60 minutes with the latest information.
Apr 1, 09:29 BST
Investigating - Some customers are seeing problems with email attachments. We’re aware of the issue and are working on it urgently.

We’re really sorry about this. Our teams are working hard to get everything back to normal, and we will update you in the next 60 minutes with the latest information.
Apr 1, 08:37 BST
Mar 31, 2020

No incidents reported.

Mar 30, 2020

No incidents reported.

Mar 29, 2020

No incidents reported.

Mar 28, 2020

No incidents reported.

Mar 27, 2020

No incidents reported.

Mar 26, 2020

No incidents reported.

Mar 25, 2020

No incidents reported.

Mar 24, 2020

No incidents reported.

Mar 23, 2020

No incidents reported.

Mar 22, 2020

No incidents reported.

Mar 21, 2020

No incidents reported.

Mar 20, 2020

No incidents reported.