manton
manton

We’ve had an hours-long outage at our hosting provider Linode, mostly affecting photos using the CDN. They have rolled out a fix and we’re hoping things get back to normal. You may want to disable the CDN for your blog under the Design page temporarily if you’re still seeing issues.

|
Embed
Progress spinner
anniegreens
anniegreens

@manton ahh the joys of being on the west coast, I didn't even notice!

|
Embed
Progress spinner
renevanbelzen
renevanbelzen

@manton Yeah, I noticed something was off. Thanks for explanation! The web has become brittle with all these turnkey solutions.

|
Embed
Progress spinner
maique@social.lol
maique@social.lol

@anniegreens Also on the west coast (albeit the European one), and I can tell you it was a long one 🙂

|
Embed
Progress spinner
anniegreens
anniegreens

@maique sorry to hear that, at least it didn't happen during the September photo challenge 😱

|
Embed
Progress spinner
maique@social.lol
maique@social.lol

@anniegreens Hahahaha. Yes, that would have been a tragedy!

|
Embed
Progress spinner
pimoore
pimoore

@manton Yikes, that's less than stellar for Linode's reputation. Has any consideration been given to switching the CDN over to Bunny.net?

|
Embed
Progress spinner
In reply to
manton
manton

@pimoore Oh, we're not actually even using Linode for the CDN. We're using Amazon's Cloudfront. But the photo storage at Linode was busted and that mostly affected the CDN so it was easier to explain it that way. 🙂

|
Embed
Progress spinner
pimoore
pimoore

@manton Ah I gotcha now, that makes sense. :) Let's hope Linode gets their act together after this one.

|
Embed
Progress spinner