{"id":1534,"date":"2025-04-23T17:21:39","date_gmt":"2025-04-23T11:51:39","guid":{"rendered":"https:\/\/blog.spike.sh\/?p=1534"},"modified":"2025-06-05T14:30:37","modified_gmt":"2025-06-05T09:00:37","slug":"payments-disruption-incident","status":"publish","type":"post","link":"https:\/\/blog.spike.sh\/payments-disruption-incident\/","title":{"rendered":"Payments Disruption Incident at Spike"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>Resolved (May 15th, 2025):<\/strong> The payment disruption incident has been fully resolved. We\u2019ve successfully restored all international payment processing with Stripe. During the disruption, we kept your service running by disabling auto-cancellations. Any pending payments will be automatically charged soon with invoices sent via email. Check your <a href=\"https:\/\/app.spike.sh\/billing\">billing dashboard<\/a> for updates or contact\u00a0<a href=\"mailto:billing@spike.sh\">billing@spike.sh<\/a> with questions.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Update (May 1st, 2025):<\/strong> We\u2019re actively working with Stripe to restore international payments. Once resolved, Stripe will automatically charge for the month of April (if not already charged), and invoices will be emailed accordingly. This is a one-time adjustment, and no action is needed from your end. We&#8217;ll share another update soon.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\">We want to inform you about an issue affecting subscription payments for customers across Americas, many parts of Europe,  Australia, and anyone using Amex cards. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On April 9th, <a href=\"https:\/\/stripe.com\">Stripe<\/a> (our payments processor) paused cross-border payments to our account due to a deactivated Import Export Certificate (IEC) from the Indian government. This policy change has impacted payment processing for many international customers.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Many customers may have received emails from <strong>Stripe<\/strong> or <strong>Spike<\/strong> regarding failed payments or errors while trying to update your credit card. We understand this can be concerning, and we sincerely apologize for the confusion. For now, please feel free to ignore those emails because a resolution action is needed on our and Stripe&#8217;s end.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\">Here\u2019s what you need to know:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Your Spike subscription is still active<\/strong><\/li>\n\n\n\n<li><strong>All alerts, on-call schedules, and status pages are working as expected<\/strong><\/li>\n\n\n\n<li><strong>There is no action required from your side<\/strong><\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\">As part of response for this issue, we have disabled auto-cancellation of accounts due to overdue fees and we are extending trials for anyone trying out Spike (<em>please email <a href=\"mailto:support@spike.sh\" rel=\"nofollow\">support@spike.sh<\/a><\/em>)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We\u2019re actively working with Stripe to resolve this issue and remove the IEC requirement. Once resolved, payments will resume as normal, and we\u2019ll notify you right away.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Thank you for your patience and continued trust in Spike. Please accept our apologies for any confusion. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you have any questions, feel free to reach out to us at <a href=\"mailto:billing@spike.sh\" rel=\"nofollow\">billing@spike.sh<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Resolved (May 15th, 2025): The payment disruption incident has been fully resolved. We\u2019ve successfully restored all international payment processing with Stripe. During the disruption, we kept your service running by disabling auto-cancellations. Any pending payments will be automatically charged soon with invoices sent via email. Check your billing dashboard for updates or contact\u00a0billing@spike.sh with questions. [&hellip;]<\/p>\n","protected":false},"author":191914268,"featured_media":1538,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_crdt_document":"","_import_markdown_pro_load_document_selector":0,"_import_markdown_pro_submit_text_textarea":"","_lmt_disableupdate":"","_lmt_disable":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":true,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false,"token":"eyJpbWciOiJodHRwczpcL1wvYmxvZy5zcGlrZS5zaFwvd3AtY29udGVudFwvdXBsb2Fkc1wvMjAyNVwvMDRcL1BheW1lbnRzLWRpc3J1cHRpb24taW5jaWRlbnQtYXQtU3Bpa2UtMTAyNHg1NTUucG5nIiwidHh0IjoiUGF5bWVudHMgZGlzcnVwdGlvbiBhdCBTcGlrZS4iLCJ0ZW1wbGF0ZSI6ImhpZ2h3YXkiLCJibG9nX2lkIjoyMzMxMzg5MDB9.1QJLnnZzlEcfGDtT5-Pt47agYSUx9nkB-pGUuaB_lYgMQ"},"version":2},"_wpas_customize_per_network":false,"jetpack_post_was_ever_published":false},"categories":[1442],"tags":[1379],"class_list":["post-1534","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-announcement","tag-announcements"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.4 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Payments Disruption Incident at Spike<\/title>\n<meta name=\"description\" content=\"Spike experienced a payment disruption after Stripe paused cross-border transactions. Learn how this impacted Spike&#039;s subscriptions, what actions were taken, and when normal service was resumed.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.spike.sh\/payments-disruption-incident\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Payments Disruption Incident at Spike\" \/>\n<meta property=\"og:description\" content=\"Spike experienced a payment disruption after Stripe paused cross-border transactions. Learn how this impacted Spike&#039;s subscriptions, what actions were taken, and when normal service was resumed.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.spike.sh\/payments-disruption-incident\/\" \/>\n<meta property=\"og:site_name\" content=\"Spike&#039;s blog\" \/>\n<meta property=\"article:published_time\" content=\"2025-04-23T11:51:39+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-06-05T09:00:37+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.spike.sh\/wp-content\/uploads\/2025\/04\/Payments-disruption-incident-at-Spike.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2080\" \/>\n\t<meta property=\"og:image:height\" content=\"1128\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Kaushik\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Kaushik\" \/>\n\t<meta name=\"twitter:label2\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"2 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/payments-disruption-incident\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/payments-disruption-incident\\\/\"},\"author\":{\"name\":\"Kaushik\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#\\\/schema\\\/person\\\/b137e57ace218547f02b86fdcb2d0e64\"},\"headline\":\"Payments Disruption Incident at Spike\",\"datePublished\":\"2025-04-23T11:51:39+00:00\",\"dateModified\":\"2025-06-05T09:00:37+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/payments-disruption-incident\\\/\"},\"wordCount\":359,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/payments-disruption-incident\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/blog.spike.sh\\\/wp-content\\\/uploads\\\/2025\\\/04\\\/Payments-disruption-incident-at-Spike.png\",\"keywords\":[\"announcements\"],\"articleSection\":[\"Announcement\"],\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/blog.spike.sh\\\/payments-disruption-incident\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/payments-disruption-incident\\\/\",\"url\":\"https:\\\/\\\/blog.spike.sh\\\/payments-disruption-incident\\\/\",\"name\":\"Payments Disruption Incident at Spike\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/payments-disruption-incident\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/payments-disruption-incident\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/blog.spike.sh\\\/wp-content\\\/uploads\\\/2025\\\/04\\\/Payments-disruption-incident-at-Spike.png\",\"datePublished\":\"2025-04-23T11:51:39+00:00\",\"dateModified\":\"2025-06-05T09:00:37+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#\\\/schema\\\/person\\\/b137e57ace218547f02b86fdcb2d0e64\"},\"description\":\"Spike experienced a payment disruption after Stripe paused cross-border transactions. Learn how this impacted Spike's subscriptions, what actions were taken, and when normal service was resumed.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/payments-disruption-incident\\\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/blog.spike.sh\\\/payments-disruption-incident\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/payments-disruption-incident\\\/#primaryimage\",\"url\":\"https:\\\/\\\/blog.spike.sh\\\/wp-content\\\/uploads\\\/2025\\\/04\\\/Payments-disruption-incident-at-Spike.png\",\"contentUrl\":\"https:\\\/\\\/blog.spike.sh\\\/wp-content\\\/uploads\\\/2025\\\/04\\\/Payments-disruption-incident-at-Spike.png\",\"width\":2080,\"height\":1128},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/payments-disruption-incident\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/blog.spike.sh\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Payments Disruption Incident at Spike\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#website\",\"url\":\"https:\\\/\\\/blog.spike.sh\\\/\",\"name\":\"Spike&#039;s blog\",\"description\":\"Learnings and opinions in a changing world\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/blog.spike.sh\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-GB\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/blog.spike.sh\\\/#\\\/schema\\\/person\\\/b137e57ace218547f02b86fdcb2d0e64\",\"name\":\"Kaushik\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/c7ec6b633161978fc09ed325cefde9061797a65a730e4b98c0eb26bc6925bc81?s=96&d=robohash&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/c7ec6b633161978fc09ed325cefde9061797a65a730e4b98c0eb26bc6925bc81?s=96&d=robohash&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/c7ec6b633161978fc09ed325cefde9061797a65a730e4b98c0eb26bc6925bc81?s=96&d=robohash&r=g\",\"caption\":\"Kaushik\"},\"description\":\"Founder of Spike. I like sharing how we are building Spike and the intricacies of building a startup by waking people up for critical incidents.\",\"url\":\"https:\\\/\\\/blog.spike.sh\\\/author\\\/spikehq\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Payments Disruption Incident at Spike","description":"Spike experienced a payment disruption after Stripe paused cross-border transactions. Learn how this impacted Spike's subscriptions, what actions were taken, and when normal service was resumed.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blog.spike.sh\/payments-disruption-incident\/","og_locale":"en_GB","og_type":"article","og_title":"Payments Disruption Incident at Spike","og_description":"Spike experienced a payment disruption after Stripe paused cross-border transactions. Learn how this impacted Spike's subscriptions, what actions were taken, and when normal service was resumed.","og_url":"https:\/\/blog.spike.sh\/payments-disruption-incident\/","og_site_name":"Spike&#039;s blog","article_published_time":"2025-04-23T11:51:39+00:00","article_modified_time":"2025-06-05T09:00:37+00:00","og_image":[{"width":2080,"height":1128,"url":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2025\/04\/Payments-disruption-incident-at-Spike.png","type":"image\/png"}],"author":"Kaushik","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Kaushik","Estimated reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.spike.sh\/payments-disruption-incident\/#article","isPartOf":{"@id":"https:\/\/blog.spike.sh\/payments-disruption-incident\/"},"author":{"name":"Kaushik","@id":"https:\/\/blog.spike.sh\/#\/schema\/person\/b137e57ace218547f02b86fdcb2d0e64"},"headline":"Payments Disruption Incident at Spike","datePublished":"2025-04-23T11:51:39+00:00","dateModified":"2025-06-05T09:00:37+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.spike.sh\/payments-disruption-incident\/"},"wordCount":359,"commentCount":0,"image":{"@id":"https:\/\/blog.spike.sh\/payments-disruption-incident\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2025\/04\/Payments-disruption-incident-at-Spike.png","keywords":["announcements"],"articleSection":["Announcement"],"inLanguage":"en-GB","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.spike.sh\/payments-disruption-incident\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.spike.sh\/payments-disruption-incident\/","url":"https:\/\/blog.spike.sh\/payments-disruption-incident\/","name":"Payments Disruption Incident at Spike","isPartOf":{"@id":"https:\/\/blog.spike.sh\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.spike.sh\/payments-disruption-incident\/#primaryimage"},"image":{"@id":"https:\/\/blog.spike.sh\/payments-disruption-incident\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2025\/04\/Payments-disruption-incident-at-Spike.png","datePublished":"2025-04-23T11:51:39+00:00","dateModified":"2025-06-05T09:00:37+00:00","author":{"@id":"https:\/\/blog.spike.sh\/#\/schema\/person\/b137e57ace218547f02b86fdcb2d0e64"},"description":"Spike experienced a payment disruption after Stripe paused cross-border transactions. Learn how this impacted Spike's subscriptions, what actions were taken, and when normal service was resumed.","breadcrumb":{"@id":"https:\/\/blog.spike.sh\/payments-disruption-incident\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.spike.sh\/payments-disruption-incident\/"]}]},{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/blog.spike.sh\/payments-disruption-incident\/#primaryimage","url":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2025\/04\/Payments-disruption-incident-at-Spike.png","contentUrl":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2025\/04\/Payments-disruption-incident-at-Spike.png","width":2080,"height":1128},{"@type":"BreadcrumbList","@id":"https:\/\/blog.spike.sh\/payments-disruption-incident\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.spike.sh\/"},{"@type":"ListItem","position":2,"name":"Payments Disruption Incident at Spike"}]},{"@type":"WebSite","@id":"https:\/\/blog.spike.sh\/#website","url":"https:\/\/blog.spike.sh\/","name":"Spike&#039;s blog","description":"Learnings and opinions in a changing world","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.spike.sh\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-GB"},{"@type":"Person","@id":"https:\/\/blog.spike.sh\/#\/schema\/person\/b137e57ace218547f02b86fdcb2d0e64","name":"Kaushik","image":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/secure.gravatar.com\/avatar\/c7ec6b633161978fc09ed325cefde9061797a65a730e4b98c0eb26bc6925bc81?s=96&d=robohash&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/c7ec6b633161978fc09ed325cefde9061797a65a730e4b98c0eb26bc6925bc81?s=96&d=robohash&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/c7ec6b633161978fc09ed325cefde9061797a65a730e4b98c0eb26bc6925bc81?s=96&d=robohash&r=g","caption":"Kaushik"},"description":"Founder of Spike. I like sharing how we are building Spike and the intricacies of building a startup by waking people up for critical incidents.","url":"https:\/\/blog.spike.sh\/author\/spikehq\/"}]}},"modified_by":"Sreekar","jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/blog.spike.sh\/wp-content\/uploads\/2025\/04\/Payments-disruption-incident-at-Spike.png","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pfMe4Q-oK","jetpack-related-posts":[{"id":2994,"url":"https:\/\/blog.spike.sh\/introducing-resolved-by-timer\/","url_meta":{"origin":1534,"position":0},"title":"Introducing \u201cResolved by Timer\u201d","author":"Kaushik","date":"27th August, 2025","format":false,"excerpt":"Spike\u2019s Resolve Timer clears cluttered dashboards by auto-resolving stale incidents. Prevent suppressed alerts, keep incidents fresh, and give on-call responders more focus.","rel":"","context":"In &quot;Announcement&quot;","block_context":{"text":"Announcement","link":"https:\/\/blog.spike.sh\/category\/announcement\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2025\/08\/resolved-by-tmer-cover.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2025\/08\/resolved-by-tmer-cover.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2025\/08\/resolved-by-tmer-cover.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2025\/08\/resolved-by-tmer-cover.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2025\/08\/resolved-by-tmer-cover.png?resize=1050%2C600&ssl=1 3x"},"classes":[]},{"id":5677,"url":"https:\/\/blog.spike.sh\/how-to-handle-midnight-incidents\/","url_meta":{"origin":1534,"position":1},"title":"How to handle midnight incidents without waking everyone up","author":"Sreekar","date":"29th March, 2026","format":false,"excerpt":"A midnight incident should wake one person, not the whole team. This guide covers how to set that up with routing rules and escalation policies.","rel":"","context":"In &quot;Guides&quot;","block_context":{"text":"Guides","link":"https:\/\/blog.spike.sh\/category\/guides\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/OpsGenie-Shutdown_-Everything-You-Need-To-Know-6.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/OpsGenie-Shutdown_-Everything-You-Need-To-Know-6.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/OpsGenie-Shutdown_-Everything-You-Need-To-Know-6.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/OpsGenie-Shutdown_-Everything-You-Need-To-Know-6.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/OpsGenie-Shutdown_-Everything-You-Need-To-Know-6.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2026\/03\/OpsGenie-Shutdown_-Everything-You-Need-To-Know-6.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":352,"url":"https:\/\/blog.spike.sh\/introducing-playbooks-automation\/","url_meta":{"origin":1534,"position":2},"title":"Introducing Playbooks Automation","author":"Kaushik","date":"10th April, 2024","format":false,"excerpt":"Playbooks automates your incident response, reduce response times, and mitigate alert fatigue. Explore real-world examples and future developments for enhanced incident resolution efficiency.","rel":"","context":"In &quot;Automation&quot;","block_context":{"text":"Automation","link":"https:\/\/blog.spike.sh\/category\/incident-management\/automation\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2024\/04\/introducing-Playbooks.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2024\/04\/introducing-Playbooks.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2024\/04\/introducing-Playbooks.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2024\/04\/introducing-Playbooks.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2024\/04\/introducing-Playbooks.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2024\/04\/introducing-Playbooks.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":3126,"url":"https:\/\/blog.spike.sh\/automated-incident-response\/","url_meta":{"origin":1534,"position":3},"title":"Automated Incident Response for DevOps, SREs, and IT Teams","author":"Sreekar","date":"2nd September, 2025","format":false,"excerpt":"While writing our 2024 recap, we found that teams handled over 2.2 million new incidents. Critical incidents alone tripled, increasing from 3,000 in 2023 to 9,200 in 2024. Dealing with such a large volume of incidents is not an easy task. And dealing with them manually is definitely not easy.\u2026","rel":"","context":"In &quot;Automation&quot;","block_context":{"text":"Automation","link":"https:\/\/blog.spike.sh\/category\/incident-management\/automation\/"},"img":{"alt_text":"Blog cover image titled \"Automated Incident Response for DevOps, SREs, and IT Teams\"","src":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2025\/09\/OpsGenie-Shutdown_-Everything-You-Need-To-Know.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2025\/09\/OpsGenie-Shutdown_-Everything-You-Need-To-Know.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2025\/09\/OpsGenie-Shutdown_-Everything-You-Need-To-Know.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2025\/09\/OpsGenie-Shutdown_-Everything-You-Need-To-Know.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2025\/09\/OpsGenie-Shutdown_-Everything-You-Need-To-Know.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2025\/09\/OpsGenie-Shutdown_-Everything-You-Need-To-Know.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":4561,"url":"https:\/\/blog.spike.sh\/postmortem-on-datadog-incidents-not-autoresolving\/","url_meta":{"origin":1534,"position":4},"title":"Postmortem on Datadog incidents not auto-resolving","author":"Damanpreet","date":"18th December, 2025","format":false,"excerpt":"On December 17th, 2025, we found that Datadog incidents weren't auto-resolving due to an issue in our Incident Grouping logic. We resolved the issue, and now Datadog incidents are auto-resolved as expected. This postmortem details the incident timeline, root cause analysis, and lessons learned.","rel":"","context":"In &quot;Postmortem&quot;","block_context":{"text":"Postmortem","link":"https:\/\/blog.spike.sh\/category\/postmortem\/"},"img":{"alt_text":"Blog cover titled \"Postmortem on Datadog incidents not auto-resolving\"","src":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2025\/12\/background-47.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2025\/12\/background-47.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2025\/12\/background-47.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2025\/12\/background-47.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":329,"url":"https:\/\/blog.spike.sh\/postmortem-of-our-dashboards-outage\/","url_meta":{"origin":1534,"position":5},"title":"Postmortem of Our Dashboard&#8217;s Outage","author":"Kaushik","date":"31st May, 2023","format":false,"excerpt":"Postmortem of Dashboard's outage on 30th May 2023. Incidents, Alerts, Escalations, API, and Status Page were NOT impacted.","rel":"","context":"In &quot;Postmortem&quot;","block_context":{"text":"Postmortem","link":"https:\/\/blog.spike.sh\/category\/postmortem\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2023\/05\/postmorem-31st-may.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2023\/05\/postmorem-31st-may.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2023\/05\/postmorem-31st-may.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2023\/05\/postmorem-31st-may.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2023\/05\/postmorem-31st-may.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/blog.spike.sh\/wp-content\/uploads\/2023\/05\/postmorem-31st-may.png?resize=1400%2C800&ssl=1 4x"},"classes":[]}],"_links":{"self":[{"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/posts\/1534","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/users\/191914268"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/comments?post=1534"}],"version-history":[{"count":11,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/posts\/1534\/revisions"}],"predecessor-version":[{"id":1741,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/posts\/1534\/revisions\/1741"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/media\/1538"}],"wp:attachment":[{"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/media?parent=1534"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/categories?post=1534"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.spike.sh\/wp-json\/wp\/v2\/tags?post=1534"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}