×
Giz Asks: Do We Really Need a Category 6 for Hurricanes?

Giz Asks: Do We Really Need a Category 6 for Hurricanes?

For more than 50 years, forecasters at the National Hurricane Center used the Saffir-Simpson Hurricane Wind Scale (SSHWS) to classify hurricane strength. This scale, which ranks hurricanes from Category 1 to Category 5, is based on only one metric: maximum sustained wind speed.

That wasn’t always the case. Until 2012, the SSHWS also took central pressure and storm surge into account, but the NHC eliminated these factors to reduce public confusion. The trouble is, rising global temperatures are exacerbating multiple hurricane hazards, not just wind speed. In recent years, exceptionally intense storms, such as Milton, Patricia, and Typhoon Haiyan, have sparked a debate over whether it’s time to create a Category 6.

For this Giz asks, we asked multiple experts which side of that debate they’re on. While some are more open to the idea than others, all agreed that simply adding a Category 6 to the SSHWS isn’t the answer—even though several past hurricanes have exceeded Category 5 wind speeds. Instead, some argue that communicating hurricane risks in a warming world may require rethinking the scale entirely, while others believe the existing system should remain unchanged.

Jennifer Collins

A professor in the School of Geosciences at the University of South Florida who co-developed an alternative to the SSHWS.

The current SSHWS—as the name implies—is just based on wind. Regarding that scale, my thoughts on a Category 6 is that it is not needed when a Category 5 on that scale would lead to total destruction anyway. There was a lot of discussion about this in the scientific community about a decade ago, and I believe that to be the general consensus.

Our newly proposed scale, the Tropical Cyclone Sensitivity Scale (TCSS), considers that wind generally only accounts for 10% of fatalities. Storm surge accounts for roughly 50% and rain about 30%. Our scale includes all three of these hurricane hazards, assigning each one a category between 1 and 5. Then, it gives an overall category which can never be lower than the highest category given to the hazards.

For example, Hurricane Florence in 2018 would be a Cat 1 at landfall for wind, a Cat 4 for storm surge, and a Cat 5 for rainfall. So, its overall score would be a Cat 5. If you consider the flooding and loss of life, I believe people who lived through it would agree that calling it a Cat 1—which the SSHWH did—does not adequately reflect the other hazards they experienced. People underestimate the risk of a low-category hurricane, or even a tropical storm, when they consider their evacuation decision, according to my previous evacuation research.

The proposed TCSS also reflects the high potential risk of two or more hazards. We consider a hazard high risk when its category is classified as a 3 or higher (equal to the definition of a Major Hurricane on the SSHWS). Whenever at least two high-risk hazards have the same category and the third hazard has a lower category, this bumps the hurricane’s overall category up by 1. So, a tropical cyclone with a Cat 3 score for both wind and storm surge, but a Cat 1 score for rainfall, would be classified as a Cat 4.

As such, a high-risk tropical cyclone can be classified as a Cat 6 on the TCSS in two scenarios. Either at least two of the hazards are Cat 5s, or two hazards are Cat 4s and one is a Cat 5. This is intended to warn the public of a hurricane with multiple extreme hazards.

Brian McNoldy

A senior research associate at the University of Miami’s Rosenstiel School of Marine, Atmospheric, and Earth Science who has tracked and written about tropical Atlantic activity since 1996.

My general thought is that adding a Cat 6 is not necessary and would not add any value to the current suite of information out there.

Since 1980, Cat 5 hurricanes have only accounted for about 5% of all named storms globally.  In the Atlantic specifically, they have accounted for 4%. I’m not convinced that splitting that tiny number of storms into even smaller bins has any advantages.

The most intense Atlantic hurricane on record is Allen was Allen in 1980, with maximum sustained winds of 190 miles per hour. None have reached that mark since then. If the threshold for a Cat 6 is at least 193-mile-per-hour winds as proposed in this study, for example, no Atlantic hurricanes to-date would qualify.

Furthermore, partitioning those small numbers into even smaller numbers does not change risk communication. The National Hurricane Center describes the aftermath of a landfalling Cat 5 hurricane as such: “Catastrophic damage will occur: A high percentage of framed homes will be destroyed, with total roof failure and wall collapse. Fallen trees and power poles will isolate residential areas. Power outages will last for weeks to possibly months. Most of the area will be uninhabitable for weeks or months.”

What additional risk communication would there be for a Category 6 if one should make landfall?

Liz Ritchie-Tyo

A professor at Monash University’s School of Earth, Atmosphere and Environment who also serves as deputy director of the university’s ARC Centre of Excellence for Weather of the 21st Century.

The answer is “no.”

The SSHWS was developed in the U.S. by a hurricane specialist and a wind engineer to put maximum sustained wind thresholds on levels of damage at landfall. If a hurricane is a Cat 5 on the SSHWS, that means catastrophic damage is expected. Thus, a new “Cat 6” just doesn’t make sense in terms of communicating threat levels.

All hurricane classification systems for all tropical cyclone basins are based on maximum sustained wind speeds. Whether it’s the SSHWS in the north Atlantic and the eastern North Pacific, or other scales in the western North Pacific, Indian Ocean, and South Pacific, but the main idea is the same: once a hurricane reaches the top category, catastrophic damage is likely if the hurricane makes landfall.

The main limitation of the current classification systems is not that they don’t go high enough to adequately communicate the threat, it’s that they are based solely on that wind threshold, which does not capture all the possible hazards associated with a landfalling hurricane.

What we really need is a new “multi-factor” categorization system that can communicate the threat of multiple hazards, namely wind, storm surge, rainfall, flooding, and landslides. Depending on the location of landfall, different hazards will be more important. Along coastlines, wind, waves, and storm surge are extremely important, while flooding and mudslides caused by heavy rain are more important further inland.

What’s more, maximum sustained wind speed does not capture the aerial extent of the storm-force winds that create waves and storm surge. The larger the area of these damaging winds, the greater the potential impact of storm surge. Similarly, the maximum wind intensity is not directly correlated with heavy rainfall. Though it’s true that Cat 4 and 5 hurricanes produce heavy rain, Cat 1 hurricanes can also produce heavy rain.

Therefore, a multi-factor categorization system that can communicate the risk of various hazards would be more useful than adding an extra category to the current scale.

Daniel Brown, NHC Hurricane Specialist Branch Chief

NHC Hurricane Specialist Branch Chief. In this role, he oversees the unit that issues tropical cyclone forecasts and warnings for the Atlantic and eastern North Pacific hurricane basins.

Currently, there are no efforts underway within NOAA to modify the SSHWS or add a new Category 6.

Storm categories only communicate the wind hazard. When warning the public about the dangers associated with tropical systems, the National Hurricane Center communicates the wide range of hazards, including storm surge, wind, rainfall, tornadoes and rip currents.

We do not over-emphasize the wind hazard by placing too much focus on the category, because most deaths caused by tropical cyclones are due to a water hazard. Storm surge, rainfall and inland flooding, and hazardous surf cause about 90% of tropical cyclone direct fatalities in the U.S.

Further, the Saffir-Simpson scale’s Category 5 already captures the worst possible damage, which is labeled as “Catastrophic Damage.” Regardless of whether storms are getting stronger, the damage can’t get any worse than “Catastrophic.”

Mark Bourassa

Professor of meteorology at Florida State University’s Center for Ocean-Atmospheric Prediction Studies with expertise in air/sea interactions, surface water waves, identification of tropical disturbances, and possible precursors to tropical cyclones.

One could make an argument that better scale construction and improved measurements would allow us to classify storms as stronger than Cat 5, but would that be helpful for any reason other than keeping a more detailed record?

I find any major hurricane worrisome enough that I doubt a new category would have any impact on public response. People who won’t or can’t evacuate for a Cat 3 or 4 storm usually won’t or can’t evacuate for a stronger storm either.

There are other types of information that forecasters are trying to communicate clearly, and this is more useful than defining a new storm category. Storm surge forecast maps are one good example of impactful improvements to hurricane hazards communication.

I hope to see clear messages about the odds of various wind speeds reaching the area where I live and work. I’d also welcome more information on projected inland flooding. This information would be much more useful than distinguishing between a Cat 5 and Cat 6 storm, both for the public and for emergency management.

That said, the arguments I’m making against creating a Cat 6 aren’t particularly fair because the goal of such a designation seems to be record keeping rather than providing a lot of additional information. There’s no reason that we can’t pursue all these options, but speaking as someone living near the Gulf Coast, I’d like to see better probabilistic maps of key hurricane hazards.

Source link
#Giz #Asks #Category #Hurricanes

What every U.K. AI startup wants to know these days is, how can I get office space in King’s Cross?  

The area is so hot that a VC firm allegedly recently won a deal by promising a founder office space in the neighborhood. “We stop at nothing to win deals [for] and to support” founders, “including helping them source office space when needed,” the firm told me when asked about the rumor, declining to confirm or deny any details. 

The neighborhood’s popularity began back in 2016 when DeepMind — then newly acquired by Google — moved in. Soon after, a flood of AI startups followed, wanting to be around the Google DeepMind magic. Today, they hope to take advantage of the cluster of AI talent there. 

This has transformed King’s Cross into one of the world’s top AI hubs, rivaled only by San Francisco and Beijing. Around London, it’s known by the sobriquet “Knowledge Quarter,” as it’s home to names like OpenAI, Meta, Isomorphic Labs, Cusp AI, Wayne, Recursive, and, a little farther down the road, Synthesia and Anthropic. The European Technology Network (ETN) just moved into a glossy new office nearby, while University College London sits around the corner.  

Mixed in with the new developments are trendy food spots like Hoppers and BAO. Hop a train from King’s Cross, and founders can be in Cambridge in 45 minutes to source talent or can be in Paris in two hours to strike a deal.  

Who would have guessed that a little more than 20 years ago, this was one of the seediest areas in London?  

“In the ’80s, crack and heroin made the area a major narcotics market,” Hussein Kanji, an investor at Hoxton Ventures, said, recalling syringes in tree trunks and gangs patrolling the streets. “In 1982, the local church was occupied by the English Collective of Prostitutes for 12 straight days.” Then, in the early 2000s, a real estate developer had a dream and, well, “now it is the AI hotbed of the United Kingdom,” Kanji said. “What a change.” 
 
Around 18 months ago, his portfolio company BioCorteX moved from the neighborhood Holborn to the Jellicoe building in King’s Cross, hoping to be near the action. “Lots going on in London right now,” Nik Sharma, co-founder of BioCorteX, told me. “Lots of hyperscalers moving in.” That includes, reportedly, Jeff Bezos’ AI company Prometheus, which is also said to be in talks to move into the Jellicoe.  

There are around 3,600 AI startups in London, which, together, have raised around $12.1 billion out of the $14.8 billion raised in the city since late July, according to Dealroom. Since the start of June, AI-related startups have leased more than 1 million square feet of office space in London, according to the real estate firm Knight Frank. With that, prime rents in King’s Cross have risen 18% over the past three years, Chris Dunn, a commercial insight associate at the firm, told me. 
 
That percentage represents only the largest leases encompassing at least 10,000 square feet, like the ones OpenAI and Prometheus are signing. The shorter deals go for even more, he said, and now the vacancy rate for conventional office space is just 0.9%. “Demand has outstripped supply,” he continued.  

Today, one of the big topics of the area is sovereignty. It was a wake-up call for many when Anthropic shut off access to Mythos and Fable this summer, leaving some in the ecosystem to conclude: “We’d better look after ourselves,” Saul Klein, co-founder of the VC firm Phoenix Court, told me.  

Phoenix Court is located in the King’s Cross area and has three portfolio companies in the vicinity, including Olix (which just announced a $3.3 billion valuation), Early Health and CoMind. Robin Klein, co-founder of the firm, said the shutdown of Fable and Mythos access was a “small but sharp reminder that Europe can’t simply rent its AI capabilities and capacity; it needs to build and hold some of its own.” King’s Cross, he said, is where much of this building is actually happening.  

“The bigger question,” he continued, “is whether the U.K. builds the infrastructure, compute, energy, capital, to make this self-reliance durable, rather than just hosting outposts of U.S. labs.” 

This former notorious red-light district is now one of the world’s top AI hubs | TechCrunch
What every U.K. AI startup wants to know these days is, how can I get office space in King’s Cross?  

The area is so hot that a VC firm allegedly recently won a deal by promising a founder office space in the neighborhood. “We stop at nothing to win deals [for] and to support” founders, “including helping them source office space when needed,” the firm told me when asked about the rumor, declining to confirm or deny any details. 







The neighborhood’s popularity began back in 2016 when DeepMind — then newly acquired by Google — moved in. Soon after, a flood of AI startups followed, wanting to be around the Google DeepMind magic. Today, they hope to take advantage of the cluster of AI talent there. 

This has transformed King’s Cross into one of the world’s top AI hubs, rivaled only by San Francisco and Beijing. Around London, it’s known by the sobriquet “Knowledge Quarter,” as it’s home to names like OpenAI, Meta, Isomorphic Labs, Cusp AI, Wayne, Recursive, and, a little farther down the road, Synthesia and Anthropic. The European Technology Network (ETN) just moved into a glossy new office nearby, while University College London sits around the corner.  

Mixed in with the new developments are trendy food spots like Hoppers and BAO. Hop a train from King’s Cross, and founders can be in Cambridge in 45 minutes to source talent or can be in Paris in two hours to strike a deal.  

Who would have guessed that a little more than 20 years ago, this was one of the seediest areas in London?  

“In the ’80s, crack and heroin made the area a major narcotics market,” Hussein Kanji, an investor at Hoxton Ventures, said, recalling syringes in tree trunks and gangs patrolling the streets. “In 1982, the local church was occupied by the English Collective of Prostitutes for 12 straight days.” Then, in the early 2000s, a real estate developer had a dream and, well, “now it is the AI hotbed of the United Kingdom,” Kanji said. “What a change.”  Around 18 months ago, his portfolio company BioCorteX moved from the neighborhood Holborn to the Jellicoe building in King’s Cross, hoping to be near the action. “Lots going on in London right now,” Nik Sharma, co-founder of BioCorteX, told me. “Lots of hyperscalers moving in.” That includes, reportedly, Jeff Bezos’ AI company Prometheus, which is also said to be in talks to move into the Jellicoe.  


There are around 3,600 AI startups in London, which, together, have raised around .1 billion out of the .8 billion raised in the city since late July, according to Dealroom. Since the start of June, AI-related startups have leased more than 1 million square feet of office space in London, according to the real estate firm Knight Frank. With that, prime rents in King’s Cross have risen 18% over the past three years, Chris Dunn, a commercial insight associate at the firm, told me.  That percentage represents only the largest leases encompassing at least 10,000 square feet, like the ones OpenAI and Prometheus are signing. The shorter deals go for even more, he said, and now the vacancy rate for conventional office space is just 0.9%. “Demand has outstripped supply,” he continued.  

Today, one of the big topics of the area is sovereignty. It was a wake-up call for many when Anthropic shut off access to Mythos and Fable this summer, leaving some in the ecosystem to conclude: “We’d better look after ourselves,” Saul Klein, co-founder of the VC firm Phoenix Court, told me.  

Phoenix Court is located in the King’s Cross area and has three portfolio companies in the vicinity, including Olix (which just announced a .3 billion valuation), Early Health and CoMind. Robin Klein, co-founder of the firm, said the shutdown of Fable and Mythos access was a “small but sharp reminder that Europe can’t simply rent its AI capabilities and capacity; it needs to build and hold some of its own.” King’s Cross, he said, is where much of this building is actually happening.  







“The bigger question,” he continued, “is whether the U.K. builds the infrastructure, compute, energy, capital, to make this self-reliance durable, rather than just hosting outposts of U.S. labs.” 

Image Credits:Phoenix Court

Top founders want to stay 

Simon Kohl, founder of Latent Labs, has offices in King’s Cross and San Francisco. The London office, at the moment, is growing faster, and he’s more bullish than ever on the ecosystem, he said. “The mood right now feels less like London trying to catch up and more like London becoming one of the default places to start a serious AI company,” he said.  Look around and you are likely to see Wayve testing its autonomous cars. Founded in 2017 by co-founder Alex Kendall, the unicorn is one of London’s biggest success stories.  

“Ten years ago, building a frontier AI company from London felt like an unusual choice,” Kendall told me. “Now it feels like an obvious one.” Wayve moved into King’s Cross in 2018 looking for a space that could double as a garage — “a rare combination in Central London,” Kendall said. He has watched the ecosystem mature around him — and it’s now evident that a startup can stay in London, raise serious capital, hire world-class AI talent, and remain globally competitive, he said.  Down the street from Anthropic’s new 158,000-square-foot office is the AI agent builder Sierra and the AI video platform Synthesia. 

Laura Gonzalez Florez, Synthesia’s chief of staff and head of people, says the company moved into its glossy new office building a year ago to accommodate its growing team. They were drawn to the area for the same reason as everyone else: “It’s very close to the airport … very close to where a lot of investors are,” she said. 

Image Credits:Synthesia

Around two-thirds of Synthesia’s engineers are remote, Gonzalez Florez said, letting the company tap into an affordable, international, and diverse talent pool and helping it scale faster. “From London, we can hire and work, without any problem, people from anywhere, from Slovenia to Portugal,” she said.  

Unsurprisingly, London’s AI boom is also causing a talent war.U.K. AI job postings have skyrocketed in the past few years, per data from PwC. When Anthropic announced it moved into town earlier this year, it listed, for example, a salary range of £260,000 to £630,000 for a machine learning research engineer when the average salary in London for the same role is around £102,000. Some founders in the U.K., like those in Silicon Valley, are being forced to raise more and bigger rounds to keep up. 

“The real test is whether more globally significant AI companies are founded, funded, and scaled from the U.K., while continuing to attract the world’s best talent to build them here,” Zain Ali, founder of the King’s Cross-based AI legal firm Centuro, told me. “If that continues to happen, King’s Cross won’t just be an AI hub. It’ll become one of the U.K.’s most important strategic assets.”
When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.#Thisformernotorious #redlight #districtis #nowone #worlds #top #hubs #TechCrunchUK
Image Credits:Phoenix Court

Top founders want to stay

Simon Kohl, founder of Latent Labs, has offices in King’s Cross and San Francisco. The London office, at the moment, is growing faster, and he’s more bullish than ever on the ecosystem, he said. “The mood right now feels less like London trying to catch up and more like London becoming one of the default places to start a serious AI company,” he said. 
 
Look around and you are likely to see Wayve testing its autonomous cars. Founded in 2017 by co-founder Alex Kendall, the unicorn is one of London’s biggest success stories.  

“Ten years ago, building a frontier AI company from London felt like an unusual choice,” Kendall told me. “Now it feels like an obvious one.” Wayve moved into King’s Cross in 2018 looking for a space that could double as a garage — “a rare combination in Central London,” Kendall said. He has watched the ecosystem mature around him — and it’s now evident that a startup can stay in London, raise serious capital, hire world-class AI talent, and remain globally competitive, he said. 
 
Down the street from Anthropic’s new 158,000-square-foot office is the AI agent builder Sierra and the AI video platform Synthesia. 

Laura Gonzalez Florez, Synthesia’s chief of staff and head of people, says the company moved into its glossy new office building a year ago to accommodate its growing team. They were drawn to the area for the same reason as everyone else: “It’s very close to the airport … very close to where a lot of investors are,” she said. 

Image Credits:Synthesia

Around two-thirds of Synthesia’s engineers are remote, Gonzalez Florez said, letting the company tap into an affordable, international, and diverse talent pool and helping it scale faster. “From London, we can hire and work, without any problem, people from anywhere, from Slovenia to Portugal,” she said.  

Unsurprisingly, London’s AI boom is also causing a talent war.

U.K. AI job postings have skyrocketed in the past few years, per data from PwC. When Anthropic announced it moved into town earlier this year, it listed, for example, a salary range of £260,000 to £630,000 for a machine learning research engineer when the average salary in London for the same role is around £102,000. Some founders in the U.K., like those in Silicon Valley, are being forced to raise more and bigger rounds to keep up. 

“The real test is whether more globally significant AI companies are founded, funded, and scaled from the U.K., while continuing to attract the world’s best talent to build them here,” Zain Ali, founder of the King’s Cross-based AI legal firm Centuro, told me. “If that continues to happen, King’s Cross won’t just be an AI hub. It’ll become one of the U.K.’s most important strategic assets.”

When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.

#Thisformernotorious #redlight #districtis #nowone #worlds #top #hubs #TechCrunchUK">This former notorious red-light district is now one of the world’s top AI hubs | TechCrunch
What every U.K. AI startup wants to know these days is, how can I get office space in King’s Cross?  

The area is so hot that a VC firm allegedly recently won a deal by promising a founder office space in the neighborhood. “We stop at nothing to win deals [for] and to support” founders, “including helping them source office space when needed,” the firm told me when asked about the rumor, declining to confirm or deny any details. 







The neighborhood’s popularity began back in 2016 when DeepMind — then newly acquired by Google — moved in. Soon after, a flood of AI startups followed, wanting to be around the Google DeepMind magic. Today, they hope to take advantage of the cluster of AI talent there. 

This has transformed King’s Cross into one of the world’s top AI hubs, rivaled only by San Francisco and Beijing. Around London, it’s known by the sobriquet “Knowledge Quarter,” as it’s home to names like OpenAI, Meta, Isomorphic Labs, Cusp AI, Wayne, Recursive, and, a little farther down the road, Synthesia and Anthropic. The European Technology Network (ETN) just moved into a glossy new office nearby, while University College London sits around the corner.  

Mixed in with the new developments are trendy food spots like Hoppers and BAO. Hop a train from King’s Cross, and founders can be in Cambridge in 45 minutes to source talent or can be in Paris in two hours to strike a deal.  

Who would have guessed that a little more than 20 years ago, this was one of the seediest areas in London?  

“In the ’80s, crack and heroin made the area a major narcotics market,” Hussein Kanji, an investor at Hoxton Ventures, said, recalling syringes in tree trunks and gangs patrolling the streets. “In 1982, the local church was occupied by the English Collective of Prostitutes for 12 straight days.” Then, in the early 2000s, a real estate developer had a dream and, well, “now it is the AI hotbed of the United Kingdom,” Kanji said. “What a change.”  Around 18 months ago, his portfolio company BioCorteX moved from the neighborhood Holborn to the Jellicoe building in King’s Cross, hoping to be near the action. “Lots going on in London right now,” Nik Sharma, co-founder of BioCorteX, told me. “Lots of hyperscalers moving in.” That includes, reportedly, Jeff Bezos’ AI company Prometheus, which is also said to be in talks to move into the Jellicoe.  


There are around 3,600 AI startups in London, which, together, have raised around .1 billion out of the .8 billion raised in the city since late July, according to Dealroom. Since the start of June, AI-related startups have leased more than 1 million square feet of office space in London, according to the real estate firm Knight Frank. With that, prime rents in King’s Cross have risen 18% over the past three years, Chris Dunn, a commercial insight associate at the firm, told me.  That percentage represents only the largest leases encompassing at least 10,000 square feet, like the ones OpenAI and Prometheus are signing. The shorter deals go for even more, he said, and now the vacancy rate for conventional office space is just 0.9%. “Demand has outstripped supply,” he continued.  

Today, one of the big topics of the area is sovereignty. It was a wake-up call for many when Anthropic shut off access to Mythos and Fable this summer, leaving some in the ecosystem to conclude: “We’d better look after ourselves,” Saul Klein, co-founder of the VC firm Phoenix Court, told me.  

Phoenix Court is located in the King’s Cross area and has three portfolio companies in the vicinity, including Olix (which just announced a .3 billion valuation), Early Health and CoMind. Robin Klein, co-founder of the firm, said the shutdown of Fable and Mythos access was a “small but sharp reminder that Europe can’t simply rent its AI capabilities and capacity; it needs to build and hold some of its own.” King’s Cross, he said, is where much of this building is actually happening.  







“The bigger question,” he continued, “is whether the U.K. builds the infrastructure, compute, energy, capital, to make this self-reliance durable, rather than just hosting outposts of U.S. labs.” 

Image Credits:Phoenix Court

Top founders want to stay 

Simon Kohl, founder of Latent Labs, has offices in King’s Cross and San Francisco. The London office, at the moment, is growing faster, and he’s more bullish than ever on the ecosystem, he said. “The mood right now feels less like London trying to catch up and more like London becoming one of the default places to start a serious AI company,” he said.  Look around and you are likely to see Wayve testing its autonomous cars. Founded in 2017 by co-founder Alex Kendall, the unicorn is one of London’s biggest success stories.  

“Ten years ago, building a frontier AI company from London felt like an unusual choice,” Kendall told me. “Now it feels like an obvious one.” Wayve moved into King’s Cross in 2018 looking for a space that could double as a garage — “a rare combination in Central London,” Kendall said. He has watched the ecosystem mature around him — and it’s now evident that a startup can stay in London, raise serious capital, hire world-class AI talent, and remain globally competitive, he said.  Down the street from Anthropic’s new 158,000-square-foot office is the AI agent builder Sierra and the AI video platform Synthesia. 

Laura Gonzalez Florez, Synthesia’s chief of staff and head of people, says the company moved into its glossy new office building a year ago to accommodate its growing team. They were drawn to the area for the same reason as everyone else: “It’s very close to the airport … very close to where a lot of investors are,” she said. 

Image Credits:Synthesia

Around two-thirds of Synthesia’s engineers are remote, Gonzalez Florez said, letting the company tap into an affordable, international, and diverse talent pool and helping it scale faster. “From London, we can hire and work, without any problem, people from anywhere, from Slovenia to Portugal,” she said.  

Unsurprisingly, London’s AI boom is also causing a talent war.U.K. AI job postings have skyrocketed in the past few years, per data from PwC. When Anthropic announced it moved into town earlier this year, it listed, for example, a salary range of £260,000 to £630,000 for a machine learning research engineer when the average salary in London for the same role is around £102,000. Some founders in the U.K., like those in Silicon Valley, are being forced to raise more and bigger rounds to keep up. 

“The real test is whether more globally significant AI companies are founded, funded, and scaled from the U.K., while continuing to attract the world’s best talent to build them here,” Zain Ali, founder of the King’s Cross-based AI legal firm Centuro, told me. “If that continues to happen, King’s Cross won’t just be an AI hub. It’ll become one of the U.K.’s most important strategic assets.”
When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.#Thisformernotorious #redlight #districtis #nowone #worlds #top #hubs #TechCrunchUK

European Technology Network (ETN) just moved into a glossy new office nearby, while University College London sits around the corner.  

Mixed in with the new developments are trendy food spots like Hoppers and BAO. Hop a train from King’s Cross, and founders can be in Cambridge in 45 minutes to source talent or can be in Paris in two hours to strike a deal.  

Who would have guessed that a little more than 20 years ago, this was one of the seediest areas in London?  

“In the ’80s, crack and heroin made the area a major narcotics market,” Hussein Kanji, an investor at Hoxton Ventures, said, recalling syringes in tree trunks and gangs patrolling the streets. “In 1982, the local church was occupied by the English Collective of Prostitutes for 12 straight days.” Then, in the early 2000s, a real estate developer had a dream and, well, “now it is the AI hotbed of the United Kingdom,” Kanji said. “What a change.” 
 
Around 18 months ago, his portfolio company BioCorteX moved from the neighborhood Holborn to the Jellicoe building in King’s Cross, hoping to be near the action. “Lots going on in London right now,” Nik Sharma, co-founder of BioCorteX, told me. “Lots of hyperscalers moving in.” That includes, reportedly, Jeff Bezos’ AI company Prometheus, which is also said to be in talks to move into the Jellicoe.  

There are around 3,600 AI startups in London, which, together, have raised around $12.1 billion out of the $14.8 billion raised in the city since late July, according to Dealroom. Since the start of June, AI-related startups have leased more than 1 million square feet of office space in London, according to the real estate firm Knight Frank. With that, prime rents in King’s Cross have risen 18% over the past three years, Chris Dunn, a commercial insight associate at the firm, told me. 
 
That percentage represents only the largest leases encompassing at least 10,000 square feet, like the ones OpenAI and Prometheus are signing. The shorter deals go for even more, he said, and now the vacancy rate for conventional office space is just 0.9%. “Demand has outstripped supply,” he continued.  

Today, one of the big topics of the area is sovereignty. It was a wake-up call for many when Anthropic shut off access to Mythos and Fable this summer, leaving some in the ecosystem to conclude: “We’d better look after ourselves,” Saul Klein, co-founder of the VC firm Phoenix Court, told me.  

Phoenix Court is located in the King’s Cross area and has three portfolio companies in the vicinity, including Olix (which just announced a $3.3 billion valuation), Early Health and CoMind. Robin Klein, co-founder of the firm, said the shutdown of Fable and Mythos access was a “small but sharp reminder that Europe can’t simply rent its AI capabilities and capacity; it needs to build and hold some of its own.” King’s Cross, he said, is where much of this building is actually happening.  

“The bigger question,” he continued, “is whether the U.K. builds the infrastructure, compute, energy, capital, to make this self-reliance durable, rather than just hosting outposts of U.S. labs.” 

This former notorious red-light district is now one of the world’s top AI hubs | TechCrunch
What every U.K. AI startup wants to know these days is, how can I get office space in King’s Cross?  

The area is so hot that a VC firm allegedly recently won a deal by promising a founder office space in the neighborhood. “We stop at nothing to win deals [for] and to support” founders, “including helping them source office space when needed,” the firm told me when asked about the rumor, declining to confirm or deny any details. 







The neighborhood’s popularity began back in 2016 when DeepMind — then newly acquired by Google — moved in. Soon after, a flood of AI startups followed, wanting to be around the Google DeepMind magic. Today, they hope to take advantage of the cluster of AI talent there. 

This has transformed King’s Cross into one of the world’s top AI hubs, rivaled only by San Francisco and Beijing. Around London, it’s known by the sobriquet “Knowledge Quarter,” as it’s home to names like OpenAI, Meta, Isomorphic Labs, Cusp AI, Wayne, Recursive, and, a little farther down the road, Synthesia and Anthropic. The European Technology Network (ETN) just moved into a glossy new office nearby, while University College London sits around the corner.  

Mixed in with the new developments are trendy food spots like Hoppers and BAO. Hop a train from King’s Cross, and founders can be in Cambridge in 45 minutes to source talent or can be in Paris in two hours to strike a deal.  

Who would have guessed that a little more than 20 years ago, this was one of the seediest areas in London?  

“In the ’80s, crack and heroin made the area a major narcotics market,” Hussein Kanji, an investor at Hoxton Ventures, said, recalling syringes in tree trunks and gangs patrolling the streets. “In 1982, the local church was occupied by the English Collective of Prostitutes for 12 straight days.” Then, in the early 2000s, a real estate developer had a dream and, well, “now it is the AI hotbed of the United Kingdom,” Kanji said. “What a change.”  Around 18 months ago, his portfolio company BioCorteX moved from the neighborhood Holborn to the Jellicoe building in King’s Cross, hoping to be near the action. “Lots going on in London right now,” Nik Sharma, co-founder of BioCorteX, told me. “Lots of hyperscalers moving in.” That includes, reportedly, Jeff Bezos’ AI company Prometheus, which is also said to be in talks to move into the Jellicoe.  


There are around 3,600 AI startups in London, which, together, have raised around .1 billion out of the .8 billion raised in the city since late July, according to Dealroom. Since the start of June, AI-related startups have leased more than 1 million square feet of office space in London, according to the real estate firm Knight Frank. With that, prime rents in King’s Cross have risen 18% over the past three years, Chris Dunn, a commercial insight associate at the firm, told me.  That percentage represents only the largest leases encompassing at least 10,000 square feet, like the ones OpenAI and Prometheus are signing. The shorter deals go for even more, he said, and now the vacancy rate for conventional office space is just 0.9%. “Demand has outstripped supply,” he continued.  

Today, one of the big topics of the area is sovereignty. It was a wake-up call for many when Anthropic shut off access to Mythos and Fable this summer, leaving some in the ecosystem to conclude: “We’d better look after ourselves,” Saul Klein, co-founder of the VC firm Phoenix Court, told me.  

Phoenix Court is located in the King’s Cross area and has three portfolio companies in the vicinity, including Olix (which just announced a .3 billion valuation), Early Health and CoMind. Robin Klein, co-founder of the firm, said the shutdown of Fable and Mythos access was a “small but sharp reminder that Europe can’t simply rent its AI capabilities and capacity; it needs to build and hold some of its own.” King’s Cross, he said, is where much of this building is actually happening.  







“The bigger question,” he continued, “is whether the U.K. builds the infrastructure, compute, energy, capital, to make this self-reliance durable, rather than just hosting outposts of U.S. labs.” 

Image Credits:Phoenix Court

Top founders want to stay 

Simon Kohl, founder of Latent Labs, has offices in King’s Cross and San Francisco. The London office, at the moment, is growing faster, and he’s more bullish than ever on the ecosystem, he said. “The mood right now feels less like London trying to catch up and more like London becoming one of the default places to start a serious AI company,” he said.  Look around and you are likely to see Wayve testing its autonomous cars. Founded in 2017 by co-founder Alex Kendall, the unicorn is one of London’s biggest success stories.  

“Ten years ago, building a frontier AI company from London felt like an unusual choice,” Kendall told me. “Now it feels like an obvious one.” Wayve moved into King’s Cross in 2018 looking for a space that could double as a garage — “a rare combination in Central London,” Kendall said. He has watched the ecosystem mature around him — and it’s now evident that a startup can stay in London, raise serious capital, hire world-class AI talent, and remain globally competitive, he said.  Down the street from Anthropic’s new 158,000-square-foot office is the AI agent builder Sierra and the AI video platform Synthesia. 

Laura Gonzalez Florez, Synthesia’s chief of staff and head of people, says the company moved into its glossy new office building a year ago to accommodate its growing team. They were drawn to the area for the same reason as everyone else: “It’s very close to the airport … very close to where a lot of investors are,” she said. 

Image Credits:Synthesia

Around two-thirds of Synthesia’s engineers are remote, Gonzalez Florez said, letting the company tap into an affordable, international, and diverse talent pool and helping it scale faster. “From London, we can hire and work, without any problem, people from anywhere, from Slovenia to Portugal,” she said.  

Unsurprisingly, London’s AI boom is also causing a talent war.U.K. AI job postings have skyrocketed in the past few years, per data from PwC. When Anthropic announced it moved into town earlier this year, it listed, for example, a salary range of £260,000 to £630,000 for a machine learning research engineer when the average salary in London for the same role is around £102,000. Some founders in the U.K., like those in Silicon Valley, are being forced to raise more and bigger rounds to keep up. 

“The real test is whether more globally significant AI companies are founded, funded, and scaled from the U.K., while continuing to attract the world’s best talent to build them here,” Zain Ali, founder of the King’s Cross-based AI legal firm Centuro, told me. “If that continues to happen, King’s Cross won’t just be an AI hub. It’ll become one of the U.K.’s most important strategic assets.”
When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.#Thisformernotorious #redlight #districtis #nowone #worlds #top #hubs #TechCrunchUK
Image Credits:Phoenix Court

Top founders want to stay

Simon Kohl, founder of Latent Labs, has offices in King’s Cross and San Francisco. The London office, at the moment, is growing faster, and he’s more bullish than ever on the ecosystem, he said. “The mood right now feels less like London trying to catch up and more like London becoming one of the default places to start a serious AI company,” he said. 
 
Look around and you are likely to see Wayve testing its autonomous cars. Founded in 2017 by co-founder Alex Kendall, the unicorn is one of London’s biggest success stories.  

“Ten years ago, building a frontier AI company from London felt like an unusual choice,” Kendall told me. “Now it feels like an obvious one.” Wayve moved into King’s Cross in 2018 looking for a space that could double as a garage — “a rare combination in Central London,” Kendall said. He has watched the ecosystem mature around him — and it’s now evident that a startup can stay in London, raise serious capital, hire world-class AI talent, and remain globally competitive, he said. 
 
Down the street from Anthropic’s new 158,000-square-foot office is the AI agent builder Sierra and the AI video platform Synthesia. 

Laura Gonzalez Florez, Synthesia’s chief of staff and head of people, says the company moved into its glossy new office building a year ago to accommodate its growing team. They were drawn to the area for the same reason as everyone else: “It’s very close to the airport … very close to where a lot of investors are,” she said. 

Image Credits:Synthesia

Around two-thirds of Synthesia’s engineers are remote, Gonzalez Florez said, letting the company tap into an affordable, international, and diverse talent pool and helping it scale faster. “From London, we can hire and work, without any problem, people from anywhere, from Slovenia to Portugal,” she said.  

Unsurprisingly, London’s AI boom is also causing a talent war.

U.K. AI job postings have skyrocketed in the past few years, per data from PwC. When Anthropic announced it moved into town earlier this year, it listed, for example, a salary range of £260,000 to £630,000 for a machine learning research engineer when the average salary in London for the same role is around £102,000. Some founders in the U.K., like those in Silicon Valley, are being forced to raise more and bigger rounds to keep up. 

“The real test is whether more globally significant AI companies are founded, funded, and scaled from the U.K., while continuing to attract the world’s best talent to build them here,” Zain Ali, founder of the King’s Cross-based AI legal firm Centuro, told me. “If that continues to happen, King’s Cross won’t just be an AI hub. It’ll become one of the U.K.’s most important strategic assets.”

When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.

#Thisformernotorious #redlight #districtis #nowone #worlds #top #hubs #TechCrunchUK">This former notorious red-light district is now one of the world’s top AI hubs | TechCrunch

What every U.K. AI startup wants to know these days is, how can I get office space in King’s Cross?  

The area is so hot that a VC firm allegedly recently won a deal by promising a founder office space in the neighborhood. “We stop at nothing to win deals [for] and to support” founders, “including helping them source office space when needed,” the firm told me when asked about the rumor, declining to confirm or deny any details. 

The neighborhood’s popularity began back in 2016 when DeepMind — then newly acquired by Google — moved in. Soon after, a flood of AI startups followed, wanting to be around the Google DeepMind magic. Today, they hope to take advantage of the cluster of AI talent there. 

This has transformed King’s Cross into one of the world’s top AI hubs, rivaled only by San Francisco and Beijing. Around London, it’s known by the sobriquet “Knowledge Quarter,” as it’s home to names like OpenAI, Meta, Isomorphic Labs, Cusp AI, Wayne, Recursive, and, a little farther down the road, Synthesia and Anthropic. The European Technology Network (ETN) just moved into a glossy new office nearby, while University College London sits around the corner.  

Mixed in with the new developments are trendy food spots like Hoppers and BAO. Hop a train from King’s Cross, and founders can be in Cambridge in 45 minutes to source talent or can be in Paris in two hours to strike a deal.  

Who would have guessed that a little more than 20 years ago, this was one of the seediest areas in London?  

“In the ’80s, crack and heroin made the area a major narcotics market,” Hussein Kanji, an investor at Hoxton Ventures, said, recalling syringes in tree trunks and gangs patrolling the streets. “In 1982, the local church was occupied by the English Collective of Prostitutes for 12 straight days.” Then, in the early 2000s, a real estate developer had a dream and, well, “now it is the AI hotbed of the United Kingdom,” Kanji said. “What a change.” 
 
Around 18 months ago, his portfolio company BioCorteX moved from the neighborhood Holborn to the Jellicoe building in King’s Cross, hoping to be near the action. “Lots going on in London right now,” Nik Sharma, co-founder of BioCorteX, told me. “Lots of hyperscalers moving in.” That includes, reportedly, Jeff Bezos’ AI company Prometheus, which is also said to be in talks to move into the Jellicoe.  

There are around 3,600 AI startups in London, which, together, have raised around $12.1 billion out of the $14.8 billion raised in the city since late July, according to Dealroom. Since the start of June, AI-related startups have leased more than 1 million square feet of office space in London, according to the real estate firm Knight Frank. With that, prime rents in King’s Cross have risen 18% over the past three years, Chris Dunn, a commercial insight associate at the firm, told me. 
 
That percentage represents only the largest leases encompassing at least 10,000 square feet, like the ones OpenAI and Prometheus are signing. The shorter deals go for even more, he said, and now the vacancy rate for conventional office space is just 0.9%. “Demand has outstripped supply,” he continued.  

Today, one of the big topics of the area is sovereignty. It was a wake-up call for many when Anthropic shut off access to Mythos and Fable this summer, leaving some in the ecosystem to conclude: “We’d better look after ourselves,” Saul Klein, co-founder of the VC firm Phoenix Court, told me.  

Phoenix Court is located in the King’s Cross area and has three portfolio companies in the vicinity, including Olix (which just announced a $3.3 billion valuation), Early Health and CoMind. Robin Klein, co-founder of the firm, said the shutdown of Fable and Mythos access was a “small but sharp reminder that Europe can’t simply rent its AI capabilities and capacity; it needs to build and hold some of its own.” King’s Cross, he said, is where much of this building is actually happening.  

“The bigger question,” he continued, “is whether the U.K. builds the infrastructure, compute, energy, capital, to make this self-reliance durable, rather than just hosting outposts of U.S. labs.” 

This former notorious red-light district is now one of the world’s top AI hubs | TechCrunch
What every U.K. AI startup wants to know these days is, how can I get office space in King’s Cross?  

The area is so hot that a VC firm allegedly recently won a deal by promising a founder office space in the neighborhood. “We stop at nothing to win deals [for] and to support” founders, “including helping them source office space when needed,” the firm told me when asked about the rumor, declining to confirm or deny any details. 







The neighborhood’s popularity began back in 2016 when DeepMind — then newly acquired by Google — moved in. Soon after, a flood of AI startups followed, wanting to be around the Google DeepMind magic. Today, they hope to take advantage of the cluster of AI talent there. 

This has transformed King’s Cross into one of the world’s top AI hubs, rivaled only by San Francisco and Beijing. Around London, it’s known by the sobriquet “Knowledge Quarter,” as it’s home to names like OpenAI, Meta, Isomorphic Labs, Cusp AI, Wayne, Recursive, and, a little farther down the road, Synthesia and Anthropic. The European Technology Network (ETN) just moved into a glossy new office nearby, while University College London sits around the corner.  

Mixed in with the new developments are trendy food spots like Hoppers and BAO. Hop a train from King’s Cross, and founders can be in Cambridge in 45 minutes to source talent or can be in Paris in two hours to strike a deal.  

Who would have guessed that a little more than 20 years ago, this was one of the seediest areas in London?  

“In the ’80s, crack and heroin made the area a major narcotics market,” Hussein Kanji, an investor at Hoxton Ventures, said, recalling syringes in tree trunks and gangs patrolling the streets. “In 1982, the local church was occupied by the English Collective of Prostitutes for 12 straight days.” Then, in the early 2000s, a real estate developer had a dream and, well, “now it is the AI hotbed of the United Kingdom,” Kanji said. “What a change.”  Around 18 months ago, his portfolio company BioCorteX moved from the neighborhood Holborn to the Jellicoe building in King’s Cross, hoping to be near the action. “Lots going on in London right now,” Nik Sharma, co-founder of BioCorteX, told me. “Lots of hyperscalers moving in.” That includes, reportedly, Jeff Bezos’ AI company Prometheus, which is also said to be in talks to move into the Jellicoe.  


There are around 3,600 AI startups in London, which, together, have raised around .1 billion out of the .8 billion raised in the city since late July, according to Dealroom. Since the start of June, AI-related startups have leased more than 1 million square feet of office space in London, according to the real estate firm Knight Frank. With that, prime rents in King’s Cross have risen 18% over the past three years, Chris Dunn, a commercial insight associate at the firm, told me.  That percentage represents only the largest leases encompassing at least 10,000 square feet, like the ones OpenAI and Prometheus are signing. The shorter deals go for even more, he said, and now the vacancy rate for conventional office space is just 0.9%. “Demand has outstripped supply,” he continued.  

Today, one of the big topics of the area is sovereignty. It was a wake-up call for many when Anthropic shut off access to Mythos and Fable this summer, leaving some in the ecosystem to conclude: “We’d better look after ourselves,” Saul Klein, co-founder of the VC firm Phoenix Court, told me.  

Phoenix Court is located in the King’s Cross area and has three portfolio companies in the vicinity, including Olix (which just announced a .3 billion valuation), Early Health and CoMind. Robin Klein, co-founder of the firm, said the shutdown of Fable and Mythos access was a “small but sharp reminder that Europe can’t simply rent its AI capabilities and capacity; it needs to build and hold some of its own.” King’s Cross, he said, is where much of this building is actually happening.  







“The bigger question,” he continued, “is whether the U.K. builds the infrastructure, compute, energy, capital, to make this self-reliance durable, rather than just hosting outposts of U.S. labs.” 

Image Credits:Phoenix Court

Top founders want to stay 

Simon Kohl, founder of Latent Labs, has offices in King’s Cross and San Francisco. The London office, at the moment, is growing faster, and he’s more bullish than ever on the ecosystem, he said. “The mood right now feels less like London trying to catch up and more like London becoming one of the default places to start a serious AI company,” he said.  Look around and you are likely to see Wayve testing its autonomous cars. Founded in 2017 by co-founder Alex Kendall, the unicorn is one of London’s biggest success stories.  

“Ten years ago, building a frontier AI company from London felt like an unusual choice,” Kendall told me. “Now it feels like an obvious one.” Wayve moved into King’s Cross in 2018 looking for a space that could double as a garage — “a rare combination in Central London,” Kendall said. He has watched the ecosystem mature around him — and it’s now evident that a startup can stay in London, raise serious capital, hire world-class AI talent, and remain globally competitive, he said.  Down the street from Anthropic’s new 158,000-square-foot office is the AI agent builder Sierra and the AI video platform Synthesia. 

Laura Gonzalez Florez, Synthesia’s chief of staff and head of people, says the company moved into its glossy new office building a year ago to accommodate its growing team. They were drawn to the area for the same reason as everyone else: “It’s very close to the airport … very close to where a lot of investors are,” she said. 

Image Credits:Synthesia

Around two-thirds of Synthesia’s engineers are remote, Gonzalez Florez said, letting the company tap into an affordable, international, and diverse talent pool and helping it scale faster. “From London, we can hire and work, without any problem, people from anywhere, from Slovenia to Portugal,” she said.  

Unsurprisingly, London’s AI boom is also causing a talent war.U.K. AI job postings have skyrocketed in the past few years, per data from PwC. When Anthropic announced it moved into town earlier this year, it listed, for example, a salary range of £260,000 to £630,000 for a machine learning research engineer when the average salary in London for the same role is around £102,000. Some founders in the U.K., like those in Silicon Valley, are being forced to raise more and bigger rounds to keep up. 

“The real test is whether more globally significant AI companies are founded, funded, and scaled from the U.K., while continuing to attract the world’s best talent to build them here,” Zain Ali, founder of the King’s Cross-based AI legal firm Centuro, told me. “If that continues to happen, King’s Cross won’t just be an AI hub. It’ll become one of the U.K.’s most important strategic assets.”
When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.#Thisformernotorious #redlight #districtis #nowone #worlds #top #hubs #TechCrunchUK
Image Credits:Phoenix Court

Top founders want to stay

Simon Kohl, founder of Latent Labs, has offices in King’s Cross and San Francisco. The London office, at the moment, is growing faster, and he’s more bullish than ever on the ecosystem, he said. “The mood right now feels less like London trying to catch up and more like London becoming one of the default places to start a serious AI company,” he said. 
 
Look around and you are likely to see Wayve testing its autonomous cars. Founded in 2017 by co-founder Alex Kendall, the unicorn is one of London’s biggest success stories.  

“Ten years ago, building a frontier AI company from London felt like an unusual choice,” Kendall told me. “Now it feels like an obvious one.” Wayve moved into King’s Cross in 2018 looking for a space that could double as a garage — “a rare combination in Central London,” Kendall said. He has watched the ecosystem mature around him — and it’s now evident that a startup can stay in London, raise serious capital, hire world-class AI talent, and remain globally competitive, he said. 
 
Down the street from Anthropic’s new 158,000-square-foot office is the AI agent builder Sierra and the AI video platform Synthesia. 

Laura Gonzalez Florez, Synthesia’s chief of staff and head of people, says the company moved into its glossy new office building a year ago to accommodate its growing team. They were drawn to the area for the same reason as everyone else: “It’s very close to the airport … very close to where a lot of investors are,” she said. 

Image Credits:Synthesia

Around two-thirds of Synthesia’s engineers are remote, Gonzalez Florez said, letting the company tap into an affordable, international, and diverse talent pool and helping it scale faster. “From London, we can hire and work, without any problem, people from anywhere, from Slovenia to Portugal,” she said.  

Unsurprisingly, London’s AI boom is also causing a talent war.

U.K. AI job postings have skyrocketed in the past few years, per data from PwC. When Anthropic announced it moved into town earlier this year, it listed, for example, a salary range of £260,000 to £630,000 for a machine learning research engineer when the average salary in London for the same role is around £102,000. Some founders in the U.K., like those in Silicon Valley, are being forced to raise more and bigger rounds to keep up. 

“The real test is whether more globally significant AI companies are founded, funded, and scaled from the U.K., while continuing to attract the world’s best talent to build them here,” Zain Ali, founder of the King’s Cross-based AI legal firm Centuro, told me. “If that continues to happen, King’s Cross won’t just be an AI hub. It’ll become one of the U.K.’s most important strategic assets.”

When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.

#Thisformernotorious #redlight #districtis #nowone #worlds #top #hubs #TechCrunchUK
Why Remote Server Access Is a Common Attack Vector

Every cloud server exposes at least one remote access point – usually SSH on port 22 – and that port is scanned constantly by bots looking for weak credentials. Password-based login is the most common way a system can be attacked by brute force, and it is quite common with a standard setup that the system is left in a state where an admin/user of that system – “root user” – can log in directly by guessing the user ID and the password combination. Add in shared team credentials, forgotten firewall rules from old projects, and staging servers left publicly reachable, and it’s clear why misconfigured remote access – not zero-day exploits – is behind most cloud server compromises. The fix is simple, though you’ll need to do some setup yourself instead of trusting the default setting.

How to lock down SSH access in the right way

The best way to secure remote access is through a series of small improvements rather than one major overhaul. The following is a real working method:

  1. Switch to SSH key authentication, then turn off password login completely in the same location: sshd_config. Keys are far harder to brute-force than passwords.
  2. Disable root login over SSH and require a non-root user with sudo privileges instead; this is a security advantage that even without any change, one key compromising would limit the impact.
  3. Change the default SSH port away from 22 to cut down on automated scanning noise (not a security measure on its own, but it reduces log clutter).
  4. Restrict access by IP using your firewall or security group, allowing SSH only from known office or VPN IP ranges rather than the entire internet.
  5. Add a VPN as a connection layer for anyone accessing servers from outside a trusted network – a VPN like Planet VPN’s free VPN service can encrypt the connection between a remote worker’s laptop and the server before SSH traffic ever leaves their device, which matters especially on public wi-fi or shared networks.

Every step you take closes the doors that the attacker may open slightly, and when you combine everything, you would have a door to a series of locked gates.

Why Do I Need a Bastion Host?

When it comes to teams working with many servers, deploying a bastion host (jump box) may be a clean and effective way to solve the long-term problem. With this method, you only expose SSH to the bastion, and the other servers accept it only when it’s from the bastion’s internal IP. This centralizes logging and makes auditing access far simpler.

Using a virtual private network (VPN) and a bastion host together is perfectly fine – and many solutions use both: a safe way to access the private network via a VPN, followed by use of a bastion host to restrict which servers can be accessed. Some teams may decide to forgo the bastion because they don’t have the manpower to manage one, and so use a combination of a VPN and a set of firewall rules that still quite a bit lowers the exposure, but without the extra effort.

Mistakes Leading to Leaving Cloud Servers Open

The Mistakes That Cause Leaving Cloud Servers Open: Even the safest development teams may have slip-ups from time to time. One of the most frequent is leaving staged, or test servers with relaxed firewall rules equivalent to those of the production environment – hackers don’t concern themselves with which environment they first land on. Another frequent error is reusing the same SSH key on several servers and clients, causing one hacked laptop to compromise all servers that key has access to.

Another common human error is not removing or changing access when someone leaves the team, so stale credentials remain valid and accessible. At last, putting trust in the strategy of “security through obscurity” – meaning one thinks that setting up the unusual port or hiding the hostname from the public is actually sufficient security – creates a wrong impression of security. This is mostly true; in reality, modern-day attackers scan all ports anyway, and there is no way to hide from them.

System Administrators Guide to Secure Remote Access 

Prohibit SSH password logins totally and depend exclusively on key-based authentication

  • Surely no one wants to type in the password every time; because of this, use only key-based authentication 
  • Deter the user from logging in as root by default and instead use the sudo command to do root tasks
  • A firewall or security group rule can provide great help with IP address-based restrictions on SSH logins 
  • For access that comes from untrusted sources or external networks, use a secure tunnel like a vpn or bastion host
  • Periodically change SSH keys and inspect access lists
  • Maintain records of login attempts and detect brute-force attacks as quickly as possible

Frequently Asked Questions

What is the principal means by which cloud servers suffer break-ins through remote access?

By far the biggest reason why this can happen is unauthorized password-based SSH logins that have been cracked by brute force. The scenario is most likely to develop where the administrator allows root login via password and leaves the default port open.

Sufficient security measures for the server via SSH keys: Do you think it is safe to rely only on key authentication? 

It is true that SSH keys drastically decrease the danger of a successful brute-force attack. However, if there is only key authentication on the server, there are still risks – the server administrator can always enable root login or disable the IP-based login restrictions. So it is recommended to always have these three in the server configuration: disabled root login, restricted access to known IPs, and rotating the keys regularly as the main components of meaningful protection. 

Is it really necessary to set up a separate VPN network while I am able to connect via SSH keys? 

A VPN gives extra security by first encrypting your computer traffic before it reaches your network, where the SSH connection will be used. This is mostly important when working on untrusted networks – like public wi-fi – where there is a threat of a potential hacker in your local network looking at your data.

Bastion host vs VPN as methods of accessing the server? 

The bastion host works by funneling SSH sessions from many users through a single, carefully monitored server point while the rest of the network (and mostly the servers) remains protected from the internet. At the same time, a vpn will fully encrypt the communication between the user and the corporate network or servers. The combination is very common among larger security teams as a part of the defense-in-depth principle. 

How often should SSH keys be rotated? 

The ideal period to change your SSH keys depends on the security practices of your organization, but generally a good practice is to change SSH keys between 90 and 180 days, or in the case that the user who had access with the key leaves or is no longer able to be contacted, such as when a team member leaves.

Why is only changing the port number for SSH enough to secure that port?

Changing the port reduces automated scanning noise in your logs but isn’t a real security control on its own — port scanners check all ports, so it should never replace key-based auth and firewall rules.

#Secure #Remote #Access #Cloud #ServerCloud,remote access">How to Secure Remote Access to Your Cloud Server in 2026
	
Protection against unauthorized remote logins to your cloud server is a matter of SSH key-based authentication, a strict security policy on the firewall, two-factor authentication, and a secure communication channel – no individual component will give adequate protection by itself. The major risk point in breaches is not the server but the open door to remote login. To patch that vulnerability, you need a series of countermeasures, not a magical setting.





Why Remote Server Access Is a Common Attack Vector



Every cloud server exposes at least one remote access point – usually SSH on port 22 – and that port is scanned constantly by bots looking for weak credentials. Password-based login is the most common way a system can be attacked by brute force, and it is quite common with a standard setup that the system is left in a state where an admin/user of that system – “root user” – can log in directly by guessing the user ID and the password combination. Add in shared team credentials, forgotten firewall rules from old projects, and staging servers left publicly reachable, and it’s clear why misconfigured remote access – not zero-day exploits – is behind most cloud server compromises. The fix is simple, though you’ll need to do some setup yourself instead of trusting the default setting.



How to lock down SSH access in the right way



The best way to secure remote access is through a series of small improvements rather than one major overhaul. The following is a real working method:




Switch to SSH key authentication, then turn off password login completely in the same location: sshd_config. Keys are far harder to brute-force than passwords.



Disable root login over SSH and require a non-root user with sudo privileges instead; this is a security advantage that even without any change, one key compromising would limit the impact.



Change the default SSH port away from 22 to cut down on automated scanning noise (not a security measure on its own, but it reduces log clutter).



Restrict access by IP using your firewall or security group, allowing SSH only from known office or VPN IP ranges rather than the entire internet.



Add a VPN as a connection layer for anyone accessing servers from outside a trusted network – a VPN like Planet VPN’s free VPN service can encrypt the connection between a remote worker’s laptop and the server before SSH traffic ever leaves their device, which matters especially on public wi-fi or shared networks.




Every step you take closes the doors that the attacker may open slightly, and when you combine everything, you would have a door to a series of locked gates.



Why Do I Need a Bastion Host?



When it comes to teams working with many servers, deploying a bastion host (jump box) may be a clean and effective way to solve the long-term problem. With this method, you only expose SSH to the bastion, and the other servers accept it only when it’s from the bastion’s internal IP. This centralizes logging and makes auditing access far simpler.



Using a virtual private network (VPN) and a bastion host together is perfectly fine – and many solutions use both: a safe way to access the private network via a VPN, followed by use of a bastion host to restrict which servers can be accessed. Some teams may decide to forgo the bastion because they don’t have the manpower to manage one, and so use a combination of a VPN and a set of firewall rules that still quite a bit lowers the exposure, but without the extra effort.



Mistakes Leading to Leaving Cloud Servers Open



The Mistakes That Cause Leaving Cloud Servers Open: Even the safest development teams may have slip-ups from time to time. One of the most frequent is leaving staged, or test servers with relaxed firewall rules equivalent to those of the production environment – hackers don’t concern themselves with which environment they first land on. Another frequent error is reusing the same SSH key on several servers and clients, causing one hacked laptop to compromise all servers that key has access to.



Another common human error is not removing or changing access when someone leaves the team, so stale credentials remain valid and accessible. At last, putting trust in the strategy of “security through obscurity” – meaning one thinks that setting up the unusual port or hiding the hostname from the public is actually sufficient security – creates a wrong impression of security. This is mostly true; in reality, modern-day attackers scan all ports anyway, and there is no way to hide from them.



System Administrators Guide to Secure Remote Access 



Prohibit SSH password logins totally and depend exclusively on key-based authentication




Surely no one wants to type in the password every time; because of this, use only key-based authentication 



Deter the user from logging in as root by default and instead use the sudo command to do root tasks



A firewall or security group rule can provide great help with IP address-based restrictions on SSH logins 



For access that comes from untrusted sources or external networks, use a secure tunnel like a vpn or bastion host



Periodically change SSH keys and inspect access lists



Maintain records of login attempts and detect brute-force attacks as quickly as possible




Frequently Asked Questions



What is the principal means by which cloud servers suffer break-ins through remote access? By far the biggest reason why this can happen is unauthorized password-based SSH logins that have been cracked by brute force. The scenario is most likely to develop where the administrator allows root login via password and leaves the default port open.  Sufficient security measures for the server via SSH keys: Do you think it is safe to rely only on key authentication?  It is true that SSH keys drastically decrease the danger of a successful brute-force attack. However, if there is only key authentication on the server, there are still risks – the server administrator can always enable root login or disable the IP-based login restrictions. So it is recommended to always have these three in the server configuration: disabled root login, restricted access to known IPs, and rotating the keys regularly as the main components of meaningful protection.   Is it really necessary to set up a separate VPN network while I am able to connect via SSH keys?  A VPN gives extra security by first encrypting your computer traffic before it reaches your network, where the SSH connection will be used. This is mostly important when working on untrusted networks – like public wi-fi – where there is a threat of a potential hacker in your local network looking at your data.  Bastion host vs VPN as methods of accessing the server?  The bastion host works by funneling SSH sessions from many users through a single, carefully monitored server point while the rest of the network (and mostly the servers) remains protected from the internet. At the same time, a vpn will fully encrypt the communication between the user and the corporate network or servers. The combination is very common among larger security teams as a part of the defense-in-depth principle.   How often should SSH keys be rotated?  The ideal period to change your SSH keys depends on the security practices of your organization, but generally a good practice is to change SSH keys between 90 and 180 days, or in the case that the user who had access with the key leaves or is no longer able to be contacted, such as when a team member leaves.  Why is only changing the port number for SSH enough to secure that port? Changing the port reduces automated scanning noise in your logs but isn’t a real security control on its own — port scanners check all ports, so it should never replace key-based auth and firewall rules.  





#Secure #Remote #Access #Cloud #ServerCloud,remote access

  1. free VPN service can encrypt the connection between a remote worker’s laptop and the server before SSH traffic ever leaves their device, which matters especially on public wi-fi or shared networks.

Every step you take closes the doors that the attacker may open slightly, and when you combine everything, you would have a door to a series of locked gates.

Why Do I Need a Bastion Host?

When it comes to teams working with many servers, deploying a bastion host (jump box) may be a clean and effective way to solve the long-term problem. With this method, you only expose SSH to the bastion, and the other servers accept it only when it’s from the bastion’s internal IP. This centralizes logging and makes auditing access far simpler.

Using a virtual private network (VPN) and a bastion host together is perfectly fine – and many solutions use both: a safe way to access the private network via a VPN, followed by use of a bastion host to restrict which servers can be accessed. Some teams may decide to forgo the bastion because they don’t have the manpower to manage one, and so use a combination of a VPN and a set of firewall rules that still quite a bit lowers the exposure, but without the extra effort.

Mistakes Leading to Leaving Cloud Servers Open

The Mistakes That Cause Leaving Cloud Servers Open: Even the safest development teams may have slip-ups from time to time. One of the most frequent is leaving staged, or test servers with relaxed firewall rules equivalent to those of the production environment – hackers don’t concern themselves with which environment they first land on. Another frequent error is reusing the same SSH key on several servers and clients, causing one hacked laptop to compromise all servers that key has access to.

Another common human error is not removing or changing access when someone leaves the team, so stale credentials remain valid and accessible. At last, putting trust in the strategy of “security through obscurity” – meaning one thinks that setting up the unusual port or hiding the hostname from the public is actually sufficient security – creates a wrong impression of security. This is mostly true; in reality, modern-day attackers scan all ports anyway, and there is no way to hide from them.

System Administrators Guide to Secure Remote Access 

Prohibit SSH password logins totally and depend exclusively on key-based authentication

  • Surely no one wants to type in the password every time; because of this, use only key-based authentication 
  • Deter the user from logging in as root by default and instead use the sudo command to do root tasks
  • A firewall or security group rule can provide great help with IP address-based restrictions on SSH logins 
  • For access that comes from untrusted sources or external networks, use a secure tunnel like a vpn or bastion host
  • Periodically change SSH keys and inspect access lists
  • Maintain records of login attempts and detect brute-force attacks as quickly as possible

Frequently Asked Questions

What is the principal means by which cloud servers suffer break-ins through remote access?

By far the biggest reason why this can happen is unauthorized password-based SSH logins that have been cracked by brute force. The scenario is most likely to develop where the administrator allows root login via password and leaves the default port open.

Sufficient security measures for the server via SSH keys: Do you think it is safe to rely only on key authentication? 

It is true that SSH keys drastically decrease the danger of a successful brute-force attack. However, if there is only key authentication on the server, there are still risks – the server administrator can always enable root login or disable the IP-based login restrictions. So it is recommended to always have these three in the server configuration: disabled root login, restricted access to known IPs, and rotating the keys regularly as the main components of meaningful protection. 

Is it really necessary to set up a separate VPN network while I am able to connect via SSH keys? 

A VPN gives extra security by first encrypting your computer traffic before it reaches your network, where the SSH connection will be used. This is mostly important when working on untrusted networks – like public wi-fi – where there is a threat of a potential hacker in your local network looking at your data.

Bastion host vs VPN as methods of accessing the server? 

The bastion host works by funneling SSH sessions from many users through a single, carefully monitored server point while the rest of the network (and mostly the servers) remains protected from the internet. At the same time, a vpn will fully encrypt the communication between the user and the corporate network or servers. The combination is very common among larger security teams as a part of the defense-in-depth principle. 

How often should SSH keys be rotated? 

The ideal period to change your SSH keys depends on the security practices of your organization, but generally a good practice is to change SSH keys between 90 and 180 days, or in the case that the user who had access with the key leaves or is no longer able to be contacted, such as when a team member leaves.

Why is only changing the port number for SSH enough to secure that port?

Changing the port reduces automated scanning noise in your logs but isn’t a real security control on its own — port scanners check all ports, so it should never replace key-based auth and firewall rules.

#Secure #Remote #Access #Cloud #ServerCloud,remote access">How to Secure Remote Access to Your Cloud Server in 2026

Protection against unauthorized remote logins to your cloud server is a matter of SSH key-based authentication, a strict security policy on the firewall, two-factor authentication, and a secure communication channel – no individual component will give adequate protection by itself. The major risk point in breaches is not the server but the open door to remote login. To patch that vulnerability, you need a series of countermeasures, not a magical setting.

Why Remote Server Access Is a Common Attack Vector

Every cloud server exposes at least one remote access point – usually SSH on port 22 – and that port is scanned constantly by bots looking for weak credentials. Password-based login is the most common way a system can be attacked by brute force, and it is quite common with a standard setup that the system is left in a state where an admin/user of that system – “root user” – can log in directly by guessing the user ID and the password combination. Add in shared team credentials, forgotten firewall rules from old projects, and staging servers left publicly reachable, and it’s clear why misconfigured remote access – not zero-day exploits – is behind most cloud server compromises. The fix is simple, though you’ll need to do some setup yourself instead of trusting the default setting.

How to lock down SSH access in the right way

The best way to secure remote access is through a series of small improvements rather than one major overhaul. The following is a real working method:

  1. Switch to SSH key authentication, then turn off password login completely in the same location: sshd_config. Keys are far harder to brute-force than passwords.
  2. Disable root login over SSH and require a non-root user with sudo privileges instead; this is a security advantage that even without any change, one key compromising would limit the impact.
  3. Change the default SSH port away from 22 to cut down on automated scanning noise (not a security measure on its own, but it reduces log clutter).
  4. Restrict access by IP using your firewall or security group, allowing SSH only from known office or VPN IP ranges rather than the entire internet.
  5. Add a VPN as a connection layer for anyone accessing servers from outside a trusted network – a VPN like Planet VPN’s free VPN service can encrypt the connection between a remote worker’s laptop and the server before SSH traffic ever leaves their device, which matters especially on public wi-fi or shared networks.

Every step you take closes the doors that the attacker may open slightly, and when you combine everything, you would have a door to a series of locked gates.

Why Do I Need a Bastion Host?

When it comes to teams working with many servers, deploying a bastion host (jump box) may be a clean and effective way to solve the long-term problem. With this method, you only expose SSH to the bastion, and the other servers accept it only when it’s from the bastion’s internal IP. This centralizes logging and makes auditing access far simpler.

Using a virtual private network (VPN) and a bastion host together is perfectly fine – and many solutions use both: a safe way to access the private network via a VPN, followed by use of a bastion host to restrict which servers can be accessed. Some teams may decide to forgo the bastion because they don’t have the manpower to manage one, and so use a combination of a VPN and a set of firewall rules that still quite a bit lowers the exposure, but without the extra effort.

Mistakes Leading to Leaving Cloud Servers Open

The Mistakes That Cause Leaving Cloud Servers Open: Even the safest development teams may have slip-ups from time to time. One of the most frequent is leaving staged, or test servers with relaxed firewall rules equivalent to those of the production environment – hackers don’t concern themselves with which environment they first land on. Another frequent error is reusing the same SSH key on several servers and clients, causing one hacked laptop to compromise all servers that key has access to.

Another common human error is not removing or changing access when someone leaves the team, so stale credentials remain valid and accessible. At last, putting trust in the strategy of “security through obscurity” – meaning one thinks that setting up the unusual port or hiding the hostname from the public is actually sufficient security – creates a wrong impression of security. This is mostly true; in reality, modern-day attackers scan all ports anyway, and there is no way to hide from them.

System Administrators Guide to Secure Remote Access 

Prohibit SSH password logins totally and depend exclusively on key-based authentication

  • Surely no one wants to type in the password every time; because of this, use only key-based authentication 
  • Deter the user from logging in as root by default and instead use the sudo command to do root tasks
  • A firewall or security group rule can provide great help with IP address-based restrictions on SSH logins 
  • For access that comes from untrusted sources or external networks, use a secure tunnel like a vpn or bastion host
  • Periodically change SSH keys and inspect access lists
  • Maintain records of login attempts and detect brute-force attacks as quickly as possible

Frequently Asked Questions

What is the principal means by which cloud servers suffer break-ins through remote access?

By far the biggest reason why this can happen is unauthorized password-based SSH logins that have been cracked by brute force. The scenario is most likely to develop where the administrator allows root login via password and leaves the default port open.

Sufficient security measures for the server via SSH keys: Do you think it is safe to rely only on key authentication? 

It is true that SSH keys drastically decrease the danger of a successful brute-force attack. However, if there is only key authentication on the server, there are still risks – the server administrator can always enable root login or disable the IP-based login restrictions. So it is recommended to always have these three in the server configuration: disabled root login, restricted access to known IPs, and rotating the keys regularly as the main components of meaningful protection. 

Is it really necessary to set up a separate VPN network while I am able to connect via SSH keys? 

A VPN gives extra security by first encrypting your computer traffic before it reaches your network, where the SSH connection will be used. This is mostly important when working on untrusted networks – like public wi-fi – where there is a threat of a potential hacker in your local network looking at your data.

Bastion host vs VPN as methods of accessing the server? 

The bastion host works by funneling SSH sessions from many users through a single, carefully monitored server point while the rest of the network (and mostly the servers) remains protected from the internet. At the same time, a vpn will fully encrypt the communication between the user and the corporate network or servers. The combination is very common among larger security teams as a part of the defense-in-depth principle. 

How often should SSH keys be rotated? 

The ideal period to change your SSH keys depends on the security practices of your organization, but generally a good practice is to change SSH keys between 90 and 180 days, or in the case that the user who had access with the key leaves or is no longer able to be contacted, such as when a team member leaves.

Why is only changing the port number for SSH enough to secure that port?

Changing the port reduces automated scanning noise in your logs but isn’t a real security control on its own — port scanners check all ports, so it should never replace key-based auth and firewall rules.

#Secure #Remote #Access #Cloud #ServerCloud,remote access

Post Comment