{"id":1016,"date":"2024-09-19T16:14:16","date_gmt":"2024-09-19T10:44:16","guid":{"rendered":"https:\/\/www.geedesk.com\/blog\/?p=1016"},"modified":"2024-09-19T16:19:54","modified_gmt":"2024-09-19T10:49:54","slug":"how-we-handled-downtime-caused-by-cloudflare-outage","status":"publish","type":"post","link":"https:\/\/www.geedesk.com\/blog\/how-we-handled-downtime-caused-by-cloudflare-outage\/","title":{"rendered":"How we handled downtime caused by Cloudflare outage"},"content":{"rendered":"\n
\"cloudflare<\/figure>\n\n\n\n

As a cloud-based SaaS provider, we rely on a robust infrastructure to keep our web application running seamlessly. One key player in that setup is Cloudflare<\/a>, which manages our DNS, firewall, and CDN, ensuring security and speed. <\/p>\n\n\n\n

Recently, we found out firsthand. Cloudflare encountered a routing issue, causing a significant disruption. Our users were suddenly unable to access the service, and traffic to our application came to a halt. Faced with this challenge, we acted fast. To restore access, we made the decision to bypass Cloudflare\u2019s firewall and CDN, and it worked\u2014the app was back online.<\/p>\n\n\n\n

But this was just the beginning. As soon as service was restored, the queued HTTP requests flooded our servers all at once. The sudden traffic spike overwhelmed the system, impacting performance. While we typically rely on autoscaling to handle such surges, waiting for it to take effect would have taken too long.<\/p>\n\n\n\n

Instead of waiting, we took a proactive approach and manually provisioned additional servers to absorb the load. This immediate action stabilized performance, and our users experienced minimal disruption.<\/p>\n\n\n\n

In situations like these, every second matters. While automation is a powerful tool, sometimes manual intervention is the best way to ensure smooth operations when the unexpected happens.<\/p>\n","protected":false},"excerpt":{"rendered":"

As a cloud-based SaaS provider, we rely on a robust infrastructure to keep our web application running seamlessly. One key player in that setup is Cloudflare, which manages our DNS, firewall, and CDN, ensuring security and speed. Recently, we found out firsthand. Cloudflare encountered a routing issue, causing a significant disruption. Our users were suddenly […]<\/p>\n","protected":false},"author":2,"featured_media":1017,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14],"tags":[],"class_list":["post-1016","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-product-update"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/posts\/1016","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/comments?post=1016"}],"version-history":[{"count":2,"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/posts\/1016\/revisions"}],"predecessor-version":[{"id":1020,"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/posts\/1016\/revisions\/1020"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/media\/1017"}],"wp:attachment":[{"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/media?parent=1016"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/categories?post=1016"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.geedesk.com\/blog\/wp-json\/wp\/v2\/tags?post=1016"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}