Hello there,

Thank you for reporting this issue to us.

I was lucky enough to troubleshoot this issue at the moment it appeared.
It looks like this is an issue with resolving DNS records for your domain.

While everything was alright with the CDN "dev showoffeurope media" I decided to check Cloud Files CDN enabled container 'supra'. Particularly I stared with resolving "supra.showoffimports.nl" and that was the moment I noticed first problems. Please, look at these two attempts of resolving aforementioned FQDN:


$ dig supra.showoffimports.nl

; <<>> DiG 9.9.4-RedHat-9.9.4-29.el7_2.3 <<>> supra.showoffimports.nl
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40205
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1500
;; QUESTION SECTION:
;supra.showoffimports.nl.	IN	A

;; AUTHORITY SECTION:
showoffimports.nl.	10800	IN	SOA	ns1.showoffimports.nl. hostmaster.showoffimports.nl. 2016101902 14400 3600 1209600 86400

;; Query time: 12 msec
;; SERVER: 83.138.151.80#53(83.138.151.80)
;; WHEN: Fri Oct 21 08:47:58 UTC 2016
;; MSG SIZE  rcvd: 103



$ dig supra.showoffimports.nl

; <<>> DiG 9.9.4-RedHat-9.9.4-29.el7_2.3 <<>> supra.showoffimports.nl
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58361
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1500
;; QUESTION SECTION:
;supra.showoffimports.nl.	IN	A

;; ANSWER SECTION:
supra.showoffimports.nl. 60	IN	CNAME	b62a0add3026974832df-d9a51ecbea6d4cee9097bede7d09b6db.r39.cf3.rackcdn.com.
b62a0add3026974832df-d9a51ecbea6d4cee9097bede7d09b6db.r39.cf3.rackcdn.com. 300 IN CNAME	a39.rackcdn.com.
a39.rackcdn.com.	300	IN	CNAME	a39.rackcdn.com.mdc.edgesuite.net.
a39.rackcdn.com.mdc.edgesuite.net. 300 IN CNAME	a41.dscg10.akamai.net.
a41.dscg10.akamai.net.	20	IN	A	2.22.146.25
a41.dscg10.akamai.net.	20	IN	A	2.22.146.91

;; Query time: 103 msec
;; SERVER: 83.138.151.80#53(83.138.151.80)
;; WHEN: Fri Oct 21 08:51:28 UTC 2016
;; MSG SIZE  rcvd: 268



As you can see the very first attempt failed and the another one (around 3,5 minutes later) succeeded.
This leads me to the conclusion that the problem is introduced by your DNS registrar.

Please, contact with your DNS registrar and report to them issue with resolving DNS records.


Regards,
Marcin Adamowicz
Cloud Infrastructure Support