{"id":221,"date":"2020-03-20T14:46:03","date_gmt":"2020-03-20T14:46:03","guid":{"rendered":"http:\/\/box5442.temp.domains\/~arpioio\/?p=221"},"modified":"2022-07-25T00:39:51","modified_gmt":"2022-07-25T00:39:51","slug":"behind-the-aws-sydney-outage","status":"publish","type":"post","link":"https:\/\/arpio.io\/staging\/8013\/behind-the-aws-sydney-outage\/","title":{"rendered":"Outage Report: AWS Sydney Region-Wide Outage, Jan 23, 2020"},"content":{"rendered":"

File this one under #RegionWideOutage\u2026<\/p>\n

On January 23, 2020, AWS suffered a 7.5 hour region-wide outage of the VPC subsystem in the ap-southeast-2 (Sydney) region. In this blog post, we\u2019ll explore what we know about the outage and its impact on customers in the region.<\/p>\n

The detail provided here comes from the Amazon Personal Health Dashboard, press articles, and stories told to us by real AWS customers impacted by the event.<\/p>\n

TLDR<\/h4>\n
To summarize, something bad happened with the data store that underlies the VPC subsystem within AWS, which required them to put that data store into read-only mode for a while. This cascaded into numerous other services within AWS that depend on writes to the VPC subsystem.<\/p>\n
Ultimately, many users were completely unscathed. But users who operate sophisticated workloads within AWS, and users who rely on higher-level services that are themselves sophisticated AWS workloads, had a really bad 7 hours that day.<\/p>\n
The only way to avoid this one would have been to be multi-region. And, Arpio can make that happen for you in minutes.<\/p>\n

Timeline<\/h4>\n
\n
11:07 a.m. AEDT,<\/strong>\u00a0The issue begins\u2026<\/li>\n
11:41 a.m. AEDT,<\/strong>\u00a0First reports of \u201cincreased API error rates and latencies\u201c show on the AWS health dashboard. \u201cConnectivity to existing instances is not impacted.\u201c<\/li>\n
12:18 p.m. AEDT,<\/strong>\u00a0EC2 status indicates that root cause has been identified, and they are working towards resolution. \u201cThis issue mainly affects EC2 RunInstances and VPC related API requests\u201c.<\/li>\n
12:29 p.m. \u2013 2:31 p.m. AEDT,<\/strong>\u00a0Additional status updates indicate cascading impact to ELB, RDS, ElastiCache, AppStream, Workspaces, and Lambda services in the region<\/li>\n
3:49 p.m. AEDT,<\/strong>\u00a0EC2 status report explains that \u201ca data store used by a subsystem responsible for the configuration of Virtual Private Cloud (VPC) networks is currently offline and the engineering teams are working to restore it.\u201c They expect the restoration process to be complete within 2 hours.<\/li>\n
\n
6:45 p.m. AEDT,<\/strong>\u00a0EC2 status report confirms that everything has returned to normal.<\/p>\n<\/li>\n<\/ul>\n
User Impact<\/h4>\n
We spoke with several AWS customers who use this region, and the impact was quite varied. Some customers were totally untouched and had only heard there were issues. Others spent the day fighting their environments. One customer we spoke with said, \u201cWe are managing a number of prod customer loads in AWS and we had issues in pure DevOps environments and autoscaling. The impact was big.\u201c<\/p>\n
But as you know, Twitter is the best place to figure out what\u2019s really going on:<\/p>\n
<\/iframe><br>\n<iframe id=\"twitter-widget-1\" class=\"\" title=\"Twitter Tweet\" src=\"https:\/\/platform.twitter.com\/embed\/index.html?dnt=false&embedId=twitter-widget-1&frame=false&hideCard=false&hideThread=false&id=1220181392652267523&lang=en&origin=http%3A%2F%2Farpio.io%2Fblog%2Foutage-report-aws-sydney-region-wide-impairment-jan-22-2020&theme=light&widgetsVersion=223fc1c4%3A1596143124634&width=550px\" frameborder=\"0\" scrolling=\"no\" allowfullscreen=\"allowfullscreen\" data-tweet-id=\"1220181392652267523\" data-mce-fragment=\"1\"><\/iframe><br>\n<iframe id=\"twitter-widget-2\" class=\"\" title=\"Twitter Tweet\" src=\"https:\/\/platform.twitter.com\/embed\/index.html?dnt=false&embedId=twitter-widget-2&frame=false&hideCard=false&hideThread=false&id=1220141074116571136&lang=en&origin=http%3A%2F%2Farpio.io%2Fblog%2Foutage-report-aws-sydney-region-wide-impairment-jan-22-2020&theme=light&widgetsVersion=223fc1c4%3A1596143124634&width=550px\" frameborder=\"0\" scrolling=\"no\" allowfullscreen=\"allowfullscreen\" data-tweet-id=\"1220141074116571136\" data-mce-fragment=\"1\"><span data-mce-type=\"bookmark\" style=\"display: inline-block; width: 0px; overflow: hidden; line-height: 0;\" class=\"mce_SELRES_start\">\ufeff<\/span><\/iframe><br>\nIn the end, it seems that activities that modified infrastructure were impacted. If you didn\u2019t need to launch new instances, run Lambdas that are VPC-connected, deploy new load balancers, etc., you were probably fine. But if your workload is elastic and wasn\u2019t already scaled up, you struggled.<\/p>\n<h4>So What Happened?<\/h4>\n<p>From the timeline above, we know that the datastore underlying the VPC subsystem was impaired. But what else can we learn from their messaging?<\/p>\n<p>Midway through the outage, AWS posted:<\/p>\n<blockquote><p>We determined that the data store needed to be restored to a point before the issue began.<\/p><\/blockquote>\n<p>Alright, data loss or data corruption occurred, and they need to restore from a backup. Or maybe they had a hardware failure and they need to rebuild the server. We\u2019ve all been there. Credit to AWS for having backups \ud83d\ude42<\/p>\n<blockquote><p>In order to do this restore, we needed to disable writes.<\/p><\/blockquote>\n<p>So, they\u2019re doing some kind of in-place restore while the data store is online for reads? If you can read from it, maybe it\u2019s not data loss\/corruption. But it seems more likely that they\u2019re operating the service off of read replicas that weren\u2019t impacted while they rebuild the primary datastore. And if that\u2019s the case, the data loss\/corruption didn\u2019t get replicated to other nodes, so maybe it was actually hardware failure.<\/p>\n<p>When the event was over, they posted more detail:<\/p>\n<blockquote><p>By 10:50 PM PST, we had fully restored the primary node in the affected data store. At this stage, we began to see recovery in instance launches within the AP-SOUTHEAST-2 Region.<\/p><\/blockquote>\n<p>So, there\u2019s a \u201cprimary node\u201d in this data store. It\u2019s not some kind of multi-master data store. And either this primary node is a single point of failure, or they had a really unfortunate compound event that impacted its redundancy as well.<\/p>\n<p>The truth is, what happened doesn\u2019t really matter. The important thing is how you engineer your system so that you\u2019re not impacted the next time.<\/p>\n<h4>Okay, Then How Do You Avoid It?<\/h4>\n<p>This was a region-wide impairment. To avoid it, you need to be able to operate from another region. Your options here are to build a multi-region application (which for many workloads is a significant re-architecture) or to be able to fail-over your application to another region (a process often called disaster recovery).<\/p>\n<h4>How Can Arpio Help?<\/h4>\n<p>Arpio is disaster recovery as a service for AWS workloads. In 15 minutes, Arpio can fully automate the disaster recovery process for your existing applications that run in AWS. And when the next region-wide outage occurs, Arpio can restore your service in an alternate region even faster.<\/p>\n<p>Oh, and we also protect you from cyber attacks on your AWS account.<\/p>\n<p>Check it out at arpio.io, and let us know if you\u2019d like to give it a spin!<\/p>\n<h4>Sources For This Post<\/h4>\n<ul>\n<li><a href=\"https:\/\/phd.aws.amazon.com\/phd\/home#\/event-log?eventID=arn:aws:health:ap-southeast-2::event\/EC2\/AWS_EC2_OPERATIONAL_ISSUE\/AWS_EC2_OPERATIONAL_ISSUE_RFMRO_1579740075&eventTab=details&layout=vertical\" target=\"_blank\" rel=\"noopener noreferrer\">The AWS Personal Health Dashboard<\/a><\/li>\n<li><a href=\"https:\/\/www.itnews.com.au\/news\/aws-suffers-cloud-problems-in-sydney-region-536917\" target=\"_blank\" rel=\"noopener noreferrer\">AWS suffers cloud problems in Sydney region<\/a><\/li>\n<li><a href=\"https:\/\/www.zdnet.com\/article\/aws-sydney-region-suffers-errors-and-latencies\/\" target=\"_blank\" rel=\"noopener noreferrer\">AWS Sydney Region Suffers API \u2018Errors And Latencies\u2019<\/a><\/li>\n<li><a href=\"https:\/\/www.crn.com.au\/news\/aws-cloud-issues-hit-sydney-region-536921\" target=\"_blank\" rel=\"noopener noreferrer\">AWS cloud issues hit Sydney region<\/a><\/li>\n<li><a href=\"https:\/\/www.crn.com.au\/news\/aws-reveals-rollback-required-to-restore-sydney-outage-536969\" target=\"_blank\" rel=\"noopener noreferrer\">AWS reveals rollback required to restore Sydney outage<\/a><\/li>\n<\/ul>\n<\/body>","protected":false},"excerpt":{"rendered":"<p>File this one under #RegionWideOutage\u2026 On January 23, 2020, AWS suffered a 7.5 hour region-wide outage of the VPC subsystem in the ap-southeast-2 (Sydney) region. In this blog post, we\u2019ll…<\/p>\n","protected":false},"author":1,"featured_media":222,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","content-type":"","inline_featured_image":false,"footnotes":""},"categories":[3],"tags":[],"class_list":["post-221","post","type-post","status-publish","format-standard","has-post-thumbnail","category-blog"],"yoast_head":"\n<title>AWS Sydney Outage, January 2020 \u2014 Arpio<\/title>\n<meta name=\"description\" content=\"On January 23, 2020, AWS suffered a 7.5 hour outage in the entire ap-southeast-2 region. This is what happened.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"AWS Sydney Outage, January 2020 \u2014 Arpio\" \/>\n<meta property=\"og:description\" content=\"On January 23, 2020, AWS suffered a 7.5 hour outage in the entire ap-southeast-2 region. This is what happened.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/\" \/>\n<meta property=\"og:site_name\" content=\"Arpio Disaster Recovery Made Easy\" \/>\n<meta property=\"article:published_time\" content=\"2020-03-20T14:46:03+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-07-25T00:39:51+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/arpio.io\/wp-content\/uploads\/2020\/08\/image-asset-3.jpeg\" \/>\n\t<meta property=\"og:image:width\" content=\"750\" \/>\n\t<meta property=\"og:image:height\" content=\"500\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"6805pwpadmin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"6805pwpadmin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/\"},\"author\":{\"name\":\"6805pwpadmin\",\"@id\":\"https:\/\/arpio.io\/staging\/8013\/#\/schema\/person\/0a2437a37056190db7e46201a6a65095\"},\"headline\":\"Outage Report: AWS Sydney Region-Wide Outage, Jan 23, 2020\",\"datePublished\":\"2020-03-20T14:46:03+00:00\",\"dateModified\":\"2022-07-25T00:39:51+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/\"},\"wordCount\":928,\"image\":{\"@id\":\"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/arpio.io\/staging\/8013\/wp-content\/uploads\/2020\/08\/image-asset-3.jpeg\",\"articleSection\":[\"Blog\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/\",\"url\":\"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/\",\"name\":\"AWS Sydney Outage, January 2020 \u2014 Arpio\",\"isPartOf\":{\"@id\":\"https:\/\/arpio.io\/staging\/8013\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/arpio.io\/staging\/8013\/wp-content\/uploads\/2020\/08\/image-asset-3.jpeg\",\"datePublished\":\"2020-03-20T14:46:03+00:00\",\"dateModified\":\"2022-07-25T00:39:51+00:00\",\"author\":{\"@id\":\"https:\/\/arpio.io\/staging\/8013\/#\/schema\/person\/0a2437a37056190db7e46201a6a65095\"},\"description\":\"On January 23, 2020, AWS suffered a 7.5 hour outage in the entire ap-southeast-2 region. This is what happened.\",\"breadcrumb\":{\"@id\":\"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/#primaryimage\",\"url\":\"https:\/\/arpio.io\/staging\/8013\/wp-content\/uploads\/2020\/08\/image-asset-3.jpeg\",\"contentUrl\":\"https:\/\/arpio.io\/staging\/8013\/wp-content\/uploads\/2020\/08\/image-asset-3.jpeg\",\"width\":750,\"height\":500},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/arpio.io\/staging\/8013\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Outage Report: AWS Sydney Region-Wide Outage, Jan 23, 2020\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/arpio.io\/staging\/8013\/#website\",\"url\":\"https:\/\/arpio.io\/staging\/8013\/\",\"name\":\"Arpio Disaster Recovery Made Easy\",\"description\":\"AWS Disaster Recovery\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/arpio.io\/staging\/8013\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/arpio.io\/staging\/8013\/#\/schema\/person\/0a2437a37056190db7e46201a6a65095\",\"name\":\"6805pwpadmin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/arpio.io\/staging\/8013\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/bbce7316dd4979a6199ddcdaed836e357939826f60c7be919373136535d247b6?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/bbce7316dd4979a6199ddcdaed836e357939826f60c7be919373136535d247b6?s=96&d=mm&r=g\",\"caption\":\"6805pwpadmin\"},\"sameAs\":[\"http:\/\/support.pagely.com\"],\"url\":\"https:\/\/arpio.io\/staging\/8013\/author\/6805pwpadmin\/\"}]}<\/script>\n","yoast_head_json":{"title":"AWS Sydney Outage, January 2020 \u2014 Arpio","description":"On January 23, 2020, AWS suffered a 7.5 hour outage in the entire ap-southeast-2 region. This is what happened.","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:\/\/arpio.io\/behind-the-aws-sydney-outage\/","og_locale":"en_US","og_type":"article","og_title":"AWS Sydney Outage, January 2020 \u2014 Arpio","og_description":"On January 23, 2020, AWS suffered a 7.5 hour outage in the entire ap-southeast-2 region. This is what happened.","og_url":"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/","og_site_name":"Arpio Disaster Recovery Made Easy","article_published_time":"2020-03-20T14:46:03+00:00","article_modified_time":"2022-07-25T00:39:51+00:00","og_image":[{"width":750,"height":500,"url":"https:\/\/arpio.io\/wp-content\/uploads\/2020\/08\/image-asset-3.jpeg","type":"image\/jpeg"}],"author":"6805pwpadmin","twitter_card":"summary_large_image","twitter_misc":{"Written by":"6805pwpadmin","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/#article","isPartOf":{"@id":"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/"},"author":{"name":"6805pwpadmin","@id":"https:\/\/arpio.io\/staging\/8013\/#\/schema\/person\/0a2437a37056190db7e46201a6a65095"},"headline":"Outage Report: AWS Sydney Region-Wide Outage, Jan 23, 2020","datePublished":"2020-03-20T14:46:03+00:00","dateModified":"2022-07-25T00:39:51+00:00","mainEntityOfPage":{"@id":"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/"},"wordCount":928,"image":{"@id":"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/#primaryimage"},"thumbnailUrl":"https:\/\/arpio.io\/staging\/8013\/wp-content\/uploads\/2020\/08\/image-asset-3.jpeg","articleSection":["Blog"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/","url":"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/","name":"AWS Sydney Outage, January 2020 \u2014 Arpio","isPartOf":{"@id":"https:\/\/arpio.io\/staging\/8013\/#website"},"primaryImageOfPage":{"@id":"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/#primaryimage"},"image":{"@id":"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/#primaryimage"},"thumbnailUrl":"https:\/\/arpio.io\/staging\/8013\/wp-content\/uploads\/2020\/08\/image-asset-3.jpeg","datePublished":"2020-03-20T14:46:03+00:00","dateModified":"2022-07-25T00:39:51+00:00","author":{"@id":"https:\/\/arpio.io\/staging\/8013\/#\/schema\/person\/0a2437a37056190db7e46201a6a65095"},"description":"On January 23, 2020, AWS suffered a 7.5 hour outage in the entire ap-southeast-2 region. This is what happened.","breadcrumb":{"@id":"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/arpio.io\/behind-the-aws-sydney-outage\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/#primaryimage","url":"https:\/\/arpio.io\/staging\/8013\/wp-content\/uploads\/2020\/08\/image-asset-3.jpeg","contentUrl":"https:\/\/arpio.io\/staging\/8013\/wp-content\/uploads\/2020\/08\/image-asset-3.jpeg","width":750,"height":500},{"@type":"BreadcrumbList","@id":"https:\/\/arpio.io\/behind-the-aws-sydney-outage\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/arpio.io\/staging\/8013\/"},{"@type":"ListItem","position":2,"name":"Outage Report: AWS Sydney Region-Wide Outage, Jan 23, 2020"}]},{"@type":"WebSite","@id":"https:\/\/arpio.io\/staging\/8013\/#website","url":"https:\/\/arpio.io\/staging\/8013\/","name":"Arpio Disaster Recovery Made Easy","description":"AWS Disaster Recovery","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/arpio.io\/staging\/8013\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/arpio.io\/staging\/8013\/#\/schema\/person\/0a2437a37056190db7e46201a6a65095","name":"6805pwpadmin","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/arpio.io\/staging\/8013\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/bbce7316dd4979a6199ddcdaed836e357939826f60c7be919373136535d247b6?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/bbce7316dd4979a6199ddcdaed836e357939826f60c7be919373136535d247b6?s=96&d=mm&r=g","caption":"6805pwpadmin"},"sameAs":["http:\/\/support.pagely.com"],"url":"https:\/\/arpio.io\/staging\/8013\/author\/6805pwpadmin\/"}]}},"_links":{"self":[{"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/posts\/221","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/comments?post=221"}],"version-history":[{"count":1,"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/posts\/221\/revisions"}],"predecessor-version":[{"id":1634,"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/posts\/221\/revisions\/1634"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/media\/222"}],"wp:attachment":[{"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/media?parent=221"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/categories?post=221"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/arpio.io\/staging\/8013\/wp-json\/wp\/v2\/tags?post=221"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}