Covid-19 Coronavirus Measures

In light of recent developments with the spread of Covid-19, and taking government advice, Team Creatomatic are now working remotely.

We have set up a new cloud-based phone system to enable us to continue to take calls away from the office on our usual number 01461 205437. If you require any website updates then please email [email protected] with your requests and we will get back to you asap.

We are still available to help throughout the duration; and we’ll be happy to arrange remote meetings via Zoom/Skype/Google Meet as appropriate.

Contact Details
Emergency contact: [email protected]
Phone number: 01461 205437

Stay safe folks!

Team Creatomatic! x

Close window

Get in touch

Got a project you’d like us to help you with? We’d love to hear from you.
Use the contact form or drop us an email and we’ll get back to you as soon as we can.

Office open Monday to Friday, 9am – 5pm

Tel: 01461 205437
Email: [email protected]

 

(Out of hours support number: *01461 536 202

*Please note:
This number is for EMERGENCY out-of-hours support only – please email [email protected] in the first instance as this account is monitored regularly)

Creatomatic Ltd
80a High Street
Annan
Dumfries and Galloway
DG12 6DW

Company number: SC422843
VAT number: 184828370

 
Close
One of our team will contact you within 24 hour of sending this form.
 
 
 
Home > Blog > Technical > CloudFlare 502 Bad Gateway errors
 
View all posts
 

CloudFlare 502 Bad Gateway errors


Around 10% of the Internet just went down.

 
 
 
James Miodonski
 

 

CloudFlare are currently experiencing an outage, resulting in affected sites returning a ‘502 Bad Gateway’ error.

It’s a pretty large-scale outage and affecting some really high profile sites including zendesk.com, medium.com and CloudFlare.com‘s own site for example.

The only options we have at this stage are either to update DNS across the board, essentially cutting out CloudFlare and it’s caching – or sitting tight until it comes back up.

Whilst the former is an option, and one we’ll initiate if it looks like this is going to be a long-running issue, DNS updates can take up to 24 hours to propagate. in this case, we’re hopeful that CloudFlare are likely to have this resolved before the updates could be made.

They’ve just updated their status page in the last few minutes: https://www.cloudflarestatus.com.

We’re keeping an eye on this status page – right now, it’s, frustratingly, all we can do until there’s an update.

 

* Update

All of the affected sites we’ve been monitoring now appear to be back online.

Updated Cloudflare System Status page has the details:

https://www.cloudflarestatus.com/

 
 
 
 
 

More stories like this

 

 
View all posts