Natural Catastrophe·ActiveEscalating
Tropical Storm Arthur tracks along Texas Gulf Coast
🇺🇸 Texas Gulf Coast, centered near Houston, Texas· Area17 Jun
84 reportsPROPMHMC+2
MediumAI Refreshed
MonitoringLow impactAI Refreshed
Google Cloud Outage in India After Third-Party Data Centre Fire
Occurred 9 Jun 2026·Detected 10 Jun 2026·
🇮🇳 India (specific city not identified in source)17 reports
Energy & InfrastructureCyberPropertyEnergyCyberCasualty & Liability
Three independent mainstream Indian outlets (Indian Express, Economic Times, Times of India) report a fire at a Delhi data centre linked to Google Cloud service disruption in India, with users in Delhi, Mumbai and Chennai reporting latency and Google Cloud rerouting traffic. Facility ownership is contested across sources — one outlet characterises it as a Google Cloud data centre, while others describe a third-party data centre used by Google Cloud. No insured loss, outage duration, customer-impact count, or claims activity has been disclosed, and the event remains at signal stage.
AI-generated from linked source reports. See our correction policy.
Impact verdict
Low impact. LOW: Three independent mainstream Indian outlets corroborate a Delhi data centre fire linked to Google Cloud disruption across three metros, establishing emergency-response scale. However, no named insured, outage duration, BI quantification, insurer/broker loss estimate, or claims/reserving action has been disclosed. Sources conflict on whether the facility is Google-owned or third-party colocation, creating coverage-pathway ambiguity. Absent any disclosed loss, BI, or aggregate exposure, overall London Market materiality remains at LOW. Continued monitoring is warranted for loss disclosures, Google Cloud status updates, or property insurance disclosures.
View assessment methodologyHow we grade what we know -- Known · Reported · Uncertain. Methodology →
Intelligence ledger
Each line expands in place to its underlying sourced claim.
Known15 lines
A fire occurred at a third-party data centre in India▾
structured lineknown
No separate sourced-claim record is available for this line yet.
The fire triggered a Google Cloud outage in India▾
structured lineknown
No separate sourced-claim record is available for this line yet.
A fire occurred at a data centre facility in India, triggering a Google Cloud outage.▾
fire_at_india_data_centrepotential property bi exposurevalid from 10 Jun 2026, 11:15Property
Market relevance: Data centre property and business interruption exposure in India
“Fire at third-party data centre hits Google Cloud services in Delhi, Mumbai, Chennai” — thehindubusinessline.com · 10 Jun 2026, 16:30 · mainstream media
“A fire at a Google Cloud data centre in Delhi has disrupted cloud services for users in the region.” — dailypioneer.com · 10 Jun 2026, 13:00 · mainstream media
“Google Cloud Outage In India As 3rd-Party Data Centre Fire Triggers Shutdown” — cobrapost.com · 10 Jun 2026, 12:15 · mainstream media
A fire occurred at a data centre in Delhi, India, on or around 10 June 2026.▾
delhi_data_centre_fire_occurredconcentration riskvalid from 10 Jun 2026, 00:00Property
Market relevance: Relevant to data centre property and business interruption lines
“Delhi data centre fire impacts Google Cloud services in India” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“Delhi data centre fire sees Google Cloud reroute traffic network capacity” — indiatimes.com · 10 Jun 2026, 12:30 · mainstream media
“Fire at data centre, Traffic rerouted from impacted facility in Delhi” — indiatimes.com · 10 Jun 2026, 07:15 · mainstream media
A fire occurred at a data centre in Delhi, India, triggering an emergency response.▾
fire_at_delhi_data_centreperil occurrencevalid from 10 Jun 2026, 07:15Property
Market relevance: Establishes peril (fire) at a critical digital infrastructure asset with potential property and BI exposure.
“Delhi data centre fire impacts Google Cloud services in India, causing latency issues for users across the country.” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“Delhi data centre fire sees Google Cloud reroute traffic network capacity” — indiatimes.com · 10 Jun 2026, 12:30 · mainstream media
“Fire at data centre, Traffic rerouted from impacted facility in Delhi” — timesofindia.indiatimes.com · 10 Jun 2026, 07:15 · mainstream media
A fire occurred at a data centre in India that Indian media link to a Google Cloud outage in Delhi, Mumbai, and Chennai.▾
datacentre_fire_indiacontextualvalid from 10 Jun 2026, 00:00Property
Market relevance: Peripheral event confirming physical/cyber concentration risk in India cloud infrastructure.
“Fire at data centre, Traffic rerouted from impacted facility in Delhi” — indiatimes.com · 10 Jun 2026, 07:15 · mainstream media
“Google Cloud outage in India after third-party data centre fire triggers shutdown” — moneycontrol.com · 10 Jun 2026, 03:30 · mainstream media
“Google Cloud outage in India after third-party data centre fire triggers shutdown” — indiatimes.com · 10 Jun 2026, 03:00 · mainstream media
A fire occurred at a data centre in the Greater Kailash area of Delhi, India, triggering an emergency response.▾
fire_at_data_centre_in_delhipotential property and bi lossvalid from 14 Jun 2026, 13:47Property
Market relevance: Physical damage to a hyperscale/colocation facility in a major Indian metro has direct London Market property and BI exposure.
“Delhi data centre fire may have destroyed equipment worth hundreds of crores” — thehindu.com · 10 Jun 2026, 02:30 · mainstream media
The fire-hit data centre is located in the Greater Kailash area of Delhi, within the National Capital Region.▾
affected_facility_in_delhi_greater_kailashregional concentration exposurevalid from 14 Jun 2026, 13:47Property
Market relevance: A Delhi metro location places the site within established Indian commercial-property risk zoning for London Market placements.
A fire occurred at a data centre facility in India and is reported to have triggered a Google Cloud outage.▾
fire_at_data_centre_in_indialoss triggervalid from 10 Jun 2026, 12:29Property
Market relevance: Establishes a physical peril (fire) at a data centre asset, which is the loss pathway anchor for property and BI cover.
“Fire at third-party data centre hits Google Cloud services in Delhi, Mumbai, Chennai” — thehindubusinessline.com · 10 Jun 2026, 16:30 · mainstream media
“A fire at a Google Cloud data centre in Delhi has disrupted cloud services for users in the region.” — dailypioneer.com · 10 Jun 2026, 13:00 · mainstream media
“Google Cloud Outage In India As 3rd-Party Data Centre Fire Triggers Shutdown” — cobrapost.com · 10 Jun 2026, 12:15 · mainstream media
A fire occurred at a data centre facility in India on or about 10 June 2026, triggering a Google Cloud service outage.▾
fire_at_data_centre_india_2026_06_10contingent business interruption potentialvalid from 10 Jun 2026, 00:00Property
Market relevance: Data centre fires are a recognised property and business interruption exposure; cloud-provider dependency creates contingent BI pathways for enterprise customers.
“Fire at third-party data centre hits Google Cloud services in Delhi, Mumbai, Chennai” — thehindubusinessline.com · 10 Jun 2026, 16:30 · mainstream media
“A fire at a Google Cloud data centre in Delhi has disrupted cloud services for users in the region.” — dailypioneer.com · 10 Jun 2026, 13:00 · mainstream media
“Google Cloud outage in India after data centre fire” — pakistantoday.com.pk · 10 Jun 2026, 12:30 · mainstream media
“Google Cloud Outage In India As 3rd-Party Data Centre Fire Triggers Shutdown” — cobrapost.com · 10 Jun 2026, 12:15 · mainstream media
A fire occurred at a third-party data centre facility in India.▾
fire_at_third_party_data_centre_indiacontingent business interruptionvalid from 9 Jun 2026, 00:00Property
Market relevance: Property damage and BI exposure for a third-party colocation/data centre facility in India
“Google Cloud outage in India after third-party data centre fire triggers shutdown” — 933thedrive.com · 10 Jun 2026, 05:18
No insured loss estimate, outage duration quantification, customer impact count, or claims/reserving activity has been publicly disclosed as of the latest update.▾
no_disclosed_insured_lossmonitoring onlyvalid from 15 Jun 2026, 04:06Property
Market relevance: Absence of disclosed loss caps current London Market materiality
No insured loss estimate, physical damage valuation, outage duration figure, or customer-impact quantification has been disclosed in any available source.▾
no_loss_estimate_disclosedunquantified exposureProperty
Market relevance: Absence of loss quantification is the principal reason the event remains at LOW potential impact; further disclosure would be required for escalation.
“No loss estimates or extent of physical damage have been disclosed.” — thehindubusinessline.com · 10 Jun 2026, 16:30 · mainstream media
The event remains at signal stage with no loss disclosure, named insured, or claims/reserving action reported.▾
lifecycle_signal_stagestatusvalid from 15 Jun 2026, 04:06
Supersession history: 1 prior/revised claim rows.
The fire triggered a Google Cloud outage in India, disrupting cloud services for users in the region.▾
google_cloud_outage_in_indiacontingent business interruptionvalid from 9 Jun 2026, 00:00Cyber
Market relevance: CBI / outage exposure for cloud-dependent commercial operations in India
“Google Cloud outage in India after third-party data centre fire triggers shutdown” — 933thedrive.com · 10 Jun 2026, 05:18
Reported34 lines
The data centre is a third-party facility used by Google Cloud▾
structured linereported
No separate sourced-claim record is available for this line yet.
Cloud services were disrupted in India as a result▾
structured linereported
No separate sourced-claim record is available for this line yet.
No injuries or fatalities at the data centre have been disclosed in available reporting.▾
no_casualties_reportedcontext onlyvalid from 15 Jun 2026, 04:06Property
Market relevance: Absence of reported casualties is consistent with a low-severity property signal but is not independently confirmed.
“Delhi data centre fire impacts Google Cloud services in India, causing latency issues for users across the country.” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“Delhi data centre fire sees Google Cloud reroute traffic network capacity” — indiatimes.com · 10 Jun 2026, 12:30 · mainstream media
Reporting characterises the incident as illustrating concentration risk in cloud infrastructure serving the Indian market, with potential business interruption implications for dependent enterprises.▾
concentration_risk_signalconcentration riskCyber
Market relevance: Underpins underwriting scrutiny of single-region cloud dependency
“highlights concentration risk in cloud infrastructure and potential business interruption exposure” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
Users in Delhi, Mumbai and Chennai reported latency and service disruption linked to the fire-affected data centre.▾
three_metro_user_impactconcentration riskvalid from 10 Jun 2026, 00:00Cyber
Market relevance: Multi-metro impact broadens potential contingent BI exposure for cloud tenants
“causing latency issues for users across the country” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“Delhi data centre fire sees Google Cloud reroute traffic network capacity” — indiatimes.com · 10 Jun 2026, 12:30 · mainstream media
Latency and service disruption for Google Cloud users were reported in Delhi, Mumbai and Chennai.▾
latency_reported_delhi_mumbai_chennaicontingent exposurevalid from 10 Jun 2026, 00:00Cyber
Market relevance: Geographic footprint suggests multi-region customer impact relevant to BI/cyber aggregation considerations.
“Delhi data centre fire impacts Google Cloud services in India, causing latency issues for users across the country.” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“Delhi data centre fire sees Google Cloud reroute traffic network capacity” — indiatimes.com · 10 Jun 2026, 12:30 · mainstream media
Coverage frames the incident as illustrative of concentration risk in cloud infrastructure and potential business interruption exposure for cloud-dependent enterprises.▾
cloud_infrastructure_concentration_riskcontingent exposurevalid from 15 Jun 2026, 04:06Cyber
Market relevance: Reinforces underwriting focus on cloud concentration and contingent BI aggregation in India.
“The incident highlights concentration risk in cloud infrastructure and potential business interruption exposure for businesses reliant on Google Cloud services in the region.” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
Indian media framed the incident as highlighting concentration risk in cloud infrastructure and potential business interruption exposure for enterprises reliant on Google Cloud services in India.▾
cloud_concentration_risk_signalconcentration raw qualitativeCyber
Market relevance: Reinforces a known concentration-risk narrative relevant to cyber, contingent BI, and supply-chain covers for cloud-dependent insureds; remains a qualitative signal only.
“highlights concentration risk in cloud infrastructure and potential business interruption exposure” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“highlights critical infrastructure fire risk at hyperscale cloud facilities” — indiatimes.com · 10 Jun 2026, 12:30 · mainstream media
Cloud service disruption was reported across three Indian metros: Delhi, Mumbai, and Chennai.▾
affected_geographic_scopeaggregation indicatorvalid from 10 Jun 2026, 07:15Cyber
Market relevance: Multi-metro impact elevates contingent BI aggregation potential versus a single-site event, but no commercial-customer quantification is available.
“latency issues for users across the country” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
Media report a large-scale emergency response to the data centre fire, with approximately 10 fire tenders deployed and two firefighter injuries.▾
datacentre_emergency_response_scalecontextualvalid from 10 Jun 2026, 00:00Property
Market relevance: Indicates a significant industrial fire event rather than a minor incident; supports seriousness of property exposure but does not by itself size the loss.
“Fire at data centre, Traffic rerouted from impacted facility in Delhi” — indiatimes.com · 10 Jun 2026, 07:15 · mainstream media
“Google Cloud outage in India after third-party data centre fire triggers shutdown” — moneycontrol.com · 10 Jun 2026, 03:30 · mainstream media
Delhi Fire Service dispatched approximately 10 fire tenders to the scene, with 3 visible on site; 2 firefighters were reported injured during suppression.▾
fire_response_scale_dfs_tendersincident severity indicatorvalid from 14 Jun 2026, 13:47Property
Market relevance: Indicates a non-trivial fire load consistent with significant IT/electrical damage, supporting potential property claim severity.
Reporting identifies the facility as a carrier-neutral site with tenants including Tata Communications, Singtel, Megaport Ltd, Netflix (Open Connect), and Google content/edge presence, alongside smaller ISPs.▾
tenants_include_major_cloud_cdn_carrierstenant industry relevancevalid from 14 Jun 2026, 13:47Property
Market relevance: Named global carrier and CDN tenants raise the prospect of London Market property, BI, and contingent BI placements covering this site.
Mainstream Indian media report a Google Cloud outage in India triggered by a third-party data centre fire, with disruption noted across Delhi, Mumbai, and Chennai.▾
google_cloud_outage_in_india_linked_to_firepotential dependent business interruptionvalid from 14 Jun 2026, 15:12Cyber
Market relevance: Cloud concentration risk and dependent enterprise BI could be triggered, but no customer-impact or duration data disclosed.
“Google Cloud outage in India after third-party data centre fire triggers shutdown” — moneycontrol.com · 10 Jun 2026, 03:30 · mainstream media
“Google Cloud outage in India after third-party data centre fire triggers shutdown” — indiatimes.com · 10 Jun 2026, 03:00 · mainstream media
Reporting frames the incident as an illustration of concentration risk in cloud infrastructure dependencies and potential business interruption exposure for cloud-dependent enterprises.▾
cloud_concentration_risk_contextthematic risk signalvalid from 10 Jun 2026, 16:49Cyber
Market relevance: Themes cloud outage aggregation, hyperscaler BI, and tech E&O accumulation analyses for underwriters.
Reporting describes outage impact in Delhi, Mumbai, and Chennai.▾
outage_geographic_scopegeographic exposurevalid from 10 Jun 2026, 16:49Cyber
Market relevance: Indicates impact across India's largest commercial hubs, relevant to enterprise BI and cloud customer exposure assessment.
“Fire at third-party data centre hits Google Cloud services in Delhi, Mumbai, Chennai” — thehindubusinessline.com · 10 Jun 2026, 16:30 · mainstream media
Multiple reports indicate the affected facility is a third-party data centre used by Google Cloud, not a Google-owned data centre.▾
facility_ownership_third_partypathway ambiguityvalid from 10 Jun 2026, 12:29Property
Market relevance: Ownership determines which property policy responds: colocation operator or hyperscaler direct
“Fire at third-party data centre hits Google Cloud services” — thehindubusinessline.com · 10 Jun 2026, 16:30 · mainstream media
“Google Cloud Outage In India As 3rd-Party Data Centre Fire Triggers Shutdown” — cobrapost.com · 10 Jun 2026, 12:15 · mainstream media
Cloud service disruption was reported across major Indian metropolitan areas including Delhi, Mumbai, and Chennai.▾
affected_metros_delhi_mumbai_chennaigeographic concentration indicatorvalid from 10 Jun 2026, 16:49Property
Market relevance: Major commercial hubs concentrate potential BI exposure for India-headquartered and India-serving enterprises
“Fire at third-party data centre hits Google Cloud services in Delhi, Mumbai, Chennai” — thehindubusinessline.com · 10 Jun 2026, 16:30 · mainstream media
Media commentary frames the incident as illustrative of supply-chain concentration risk in cloud infrastructure and potential business interruption exposure for cloud-dependent commercial enterprises, including possible knock-on effects for cyber liability and technology E&O books.▾
cloud_concentration_risk_thesissector risk narrativeCyber
Market relevance: The event is being cited in trade-adjacent coverage as a reference point for cloud concentration risk, contingent BI exposure, and cyber/Tech E&O considerations.
“The incident raises potential implications for property and cyber insurance lines” — thehindubusinessline.com · 10 Jun 2026, 16:30 · mainstream media
“potential knock-on effects for cyber liability and technology E&O books” — rediff.com · 10 Jun 2026, 11:00 · mainstream media
The affected data centre is a third-party facility used by Google Cloud, not directly owned by Google.▾
data_centre_is_third_party_to_googlesupply chain concentrationCyber
Market relevance: Illustrates supply-chain / vendor concentration in cloud infrastructure
Indian media report the fire destroyed approximately 200 server racks and IT equipment valued in the hundreds of crores of rupees, with industry estimates in the low-to-mid single-digit USD millions.▾
datacentre_equipment_valueloss floorvalid from 10 Jun 2026, 00:00Property
Market relevance: Floors facility-level property damage in the low single-digit USD millions range; consistent with a localised data hall loss, not a multi-facility catastrophe.
“Google Cloud outage in India after third-party data centre fire triggers shutdown” — indiatimes.com · 10 Jun 2026, 03:00 · mainstream media
Reporting indicates approximately 200 racks of servers were affected, of which around 50 racks belonged to a single named tenant.▾
server_racks_destroyed_200_of_50property damage indicatorvalid from 14 Jun 2026, 13:47Property
Market relevance: Multi-tenant server damage drives both property and BI exposure, and the 50-rack single-tenant detail is a credible loss-lead for follow-up.
A Google Cloud service disruption was reported in India following the Delhi data centre fire, with traffic rerouted.▾
google_cloud_outage_indiacontingent exposurevalid from 10 Jun 2026, 00:00Cyber
Market relevance: Indicates downstream service interruption potentially relevant to cyber and contingent BI coverage.
“Delhi data centre fire impacts Google Cloud services in India, causing latency issues for users across the country.” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“Delhi data centre fire sees Google Cloud reroute traffic network capacity” — indiatimes.com · 10 Jun 2026, 12:30 · mainstream media
“Fire at data centre, Traffic rerouted from impacted facility in Delhi” — indiatimes.com · 10 Jun 2026, 07:15 · mainstream media
Supersession history: 1 prior/revised claim rows.
A fire occurred at a data centre in Delhi, India.▾
delhi_dc_fire_occurredevent triggervalid from 10 Jun 2026, 00:00Property
Market relevance: Establishes physical peril occurrence underpinning downstream property and BI exposure.
“Delhi data centre fire impacts Google Cloud services in India, causing latency issues for users across the country.” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“Delhi data centre fire sees Google Cloud reroute traffic network capacity” — indiatimes.com · 10 Jun 2026, 12:30 · mainstream media
“Fire at data centre, Traffic rerouted from impacted facility in Delhi” — indiatimes.com · 10 Jun 2026, 07:15 · mainstream media
Indian media located the fire at a data centre in the Greater Kailash area of Delhi; precise facility name and street address are not disclosed.▾
datacentre_fire_locationcontextualvalid from 10 Jun 2026, 00:00Property
Market relevance: Helps local loss adjusters and brokers identify the site for property inspections.
“Google Cloud outage in India after third-party data centre fire triggers shutdown” — moneycontrol.com · 10 Jun 2026, 03:30 · mainstream media
Google Cloud service disruption was reported across Indian metropolitan areas. The Hindu Businessline specifically identifies Delhi, Mumbai, and Chennai; other sources reference Delhi or India more broadly.▾
outage_geographic_scope_indiageographic exposurevalid from 10 Jun 2026, 00:00Cyber
Market relevance: Geographic scope informs potential enterprise customer concentration and business interruption exposure in major Indian commercial centres.
“Fire at third-party data centre hits Google Cloud services in Delhi, Mumbai, Chennai” — thehindubusinessline.com · 10 Jun 2026, 16:30 · mainstream media
No insured loss, business interruption figure, customer-impact count, insurer or broker loss estimate, or claims/reserving activity has been disclosed.▾
no_insured_loss_disclosedinsufficient informationvalid from 15 Jun 2026, 04:06Property
Market relevance: Without disclosed loss, severity cannot be banded and London Market materiality remains low.
“Delhi data centre fire impacts Google Cloud services in India, causing latency issues for users across the country.” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“Delhi data centre fire sees Google Cloud reroute traffic network capacity” — indiatimes.com · 10 Jun 2026, 12:30 · mainstream media
“Fire at data centre, Traffic rerouted from impacted facility in Delhi” — indiatimes.com · 10 Jun 2026, 07:15 · mainstream media
Industry estimates cited in reporting place the destroyed IT equipment at 'hundreds of crores' of rupees (tens of millions of USD), with a specific quote citing ₹100 crore and a facility-wide estimate of up to ₹500 crore.▾
equipment_loss_in_hundreds_of_croresproperty loss estimatevalid from 14 Jun 2026, 13:47Property
Market relevance: An insured equipment loss in the low-to-mid single-digit USD millions range is consistent with a MEDIUM property/BI materiality at the facility level, absent total loss and additional BI.
Media frame the event as illustrative of cloud infrastructure supply-chain concentration risk, with potential contingent business interruption exposure for enterprises dependent on a single hyperscaler region.▾
datacentre_supply_chain_concentration_riskunderwriting attentionvalid from 10 Jun 2026, 00:00Cyber
Market relevance: Underpins renewed underwriting scrutiny of cloud-dependent BI wordings, dependent business interruption extensions, and systemic cyber aggregation scenarios.
“supply chain dependency risks in cloud infrastructure” — moneycontrol.com · 10 Jun 2026, 03:30 · mainstream media
“concentration risk in cloud service dependencies” — indiatimes.com · 10 Jun 2026, 03:00 · mainstream media
Google Cloud services in India were disrupted following the Delhi data centre fire, with traffic being rerouted and users in Delhi, Mumbai and Chennai reporting latency.▾
google_cloud_service_disruption_indiabusiness interruption exposurevalid from 10 Jun 2026, 00:00Cyber
Market relevance: Cloud outage signals potential contingent business interruption for cloud-dependent enterprises
“Delhi data centre fire impacts Google Cloud services in India, causing latency issues for users across the country” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“Delhi data centre fire sees Google Cloud reroute traffic network capacity” — indiatimes.com · 10 Jun 2026, 12:30 · mainstream media
“Traffic rerouted from impacted facility in Delhi” — indiatimes.com · 10 Jun 2026, 07:15 · mainstream media
Event remains at signal stage: no insured loss, outage duration, customer-impact quantification, or claims activity has been disclosed.▾
signal_stage_no_loss_disclosureinsufficient informationvalid from 15 Jun 2026, 04:06Property
Market relevance: Lifecycle at signal supports conservative severity banding; continued monitoring warranted.
“Delhi data centre fire impacts Google Cloud services in India, causing latency issues for users across the country.” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
Supersession history: 1 prior/revised claim rows.
Google Cloud users in India experienced latency and service disruption following the Delhi data centre fire, with traffic being rerouted from the impacted facility.▾
google_cloud_service_disruptionservice interruptionvalid from 10 Jun 2026, 07:15Cyber
Market relevance: Confirms a cyber/cloud service interruption linked to a physical peril, relevant to cyber and BI covers dependent on hyperscale cloud availability.
“causing latency issues for users across the country” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“Google Cloud reroute traffic network capacity” — indiatimes.com · 10 Jun 2026, 12:30 · mainstream media
“Traffic rerouted from impacted facility in Delhi” — timesofindia.indiatimes.com · 10 Jun 2026, 07:15 · mainstream media
Indian media report a Google Cloud outage impacting Delhi, Mumbai, and Chennai, with traffic rerouted from the impacted Delhi facility.▾
google_cloud_outage_scopepotential bi exposurevalid from 10 Jun 2026, 00:00Cyber
Market relevance: Suggests geographic concentration of cloud disruption in India's three largest cloud markets; relevant to contingent business interruption coverage for cloud-dependent insureds.
“Traffic rerouted from impacted facility in Delhi” — indiatimes.com · 10 Jun 2026, 07:15 · mainstream media
The event remains at signal stage pending quantification of facility value, outage duration, customer impact, and any insured loss disclosure.▾
event_lifecycle_remains_signallifecycle classificationvalid from 14 Jun 2026, 15:12
Market relevance: Signal-stage classification is consistent with absent loss disclosure and conflicting facility-ownership reporting.
Google Cloud services were disrupted in India following the data centre fire, with reporting describing impact across Delhi, Mumbai, and Chennai.▾
google_cloud_outage_reportedoperational impactvalid from 10 Jun 2026, 16:49Cyber
Market relevance: Confirms operational impact to a cloud hyperscaler footprint, relevant to cloud outage aggregation and downstream enterprise BI.
“Fire at third-party data centre hits Google Cloud services in Delhi, Mumbai, Chennai” — thehindubusinessline.com · 10 Jun 2026, 16:30 · mainstream media
“A fire at a Google Cloud data centre in Delhi has disrupted cloud services for users in the region.” — dailypioneer.com · 10 Jun 2026, 13:00 · mainstream media
“Fire Causes Google Cloud Outage In Key Indian Metros” — rediff.com · 10 Jun 2026, 11:00 · mainstream media
Uncertain40 lines
Name and exact location of the affected data centre▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Extent and duration of the outage▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Scope of affected Google Cloud services▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Number of commercial customers impacted▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Estimated insured loss or business interruption figure▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Root cause of the fire▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Sources conflict on whether the affected Delhi facility is a Google-operated data centre or a third-party colocation used by Google Cloud.▾
facility_ownership_disputedcoverage pathway ambiguityvalid from 10 Jun 2026, 00:00Property
Market relevance: Ownership ambiguity affects coverage pathway (property owner policy vs hyperscaler policy) and reinsurance recovery paths.
“Delhi data centre fire impacts Google Cloud services in India, causing latency issues for users across the country.” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“Delhi data centre fire sees Google Cloud reroute traffic network capacity” — indiatimes.com · 10 Jun 2026, 12:30 · mainstream media
“Fire at data centre, Traffic rerouted from impacted facility in Delhi” — indiatimes.com · 10 Jun 2026, 07:15 · mainstream media
No outage duration, restoration timeline, or scope of affected Google Cloud services has been disclosed in available reporting.▾
outage_duration_unknowninsufficient informationvalid from 15 Jun 2026, 04:06Cyber
Market relevance: Duration is a primary driver of contingent BI severity; absence prevents severity banding.
“Delhi data centre fire impacts Google Cloud services in India, causing latency issues for users across the country.” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“Delhi data centre fire sees Google Cloud reroute traffic network capacity” — indiatimes.com · 10 Jun 2026, 12:30 · mainstream media
Supersession history: 1 prior/revised claim rows.
The name and exact street-level location of the affected Delhi data centre have not been disclosed in available reporting.▾
facility_name_location_uncertaininsufficient informationvalid from 15 Jun 2026, 04:06Property
Market relevance: Facility identity is required to map exposure to specific property schedules and binder records.
“Delhi data centre fire impacts Google Cloud services in India, causing latency issues for users across the country.” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“Delhi data centre fire sees Google Cloud reroute traffic network capacity” — indiatimes.com · 10 Jun 2026, 12:30 · mainstream media
No root cause for the fire (electrical, mechanical, external, or arson) has been disclosed.▾
fire_root_cause_uncertaininsufficient informationvalid from 15 Jun 2026, 04:06Property
Market relevance: Root cause influences coverage sub-limits, warranties, and potential recovery/contesting actions.
“Delhi data centre fire impacts Google Cloud services in India, causing latency issues for users across the country.” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“Delhi data centre fire sees Google Cloud reroute traffic network capacity” — indiatimes.com · 10 Jun 2026, 12:30 · mainstream media
The root cause of the fire at the Delhi data centre has not been disclosed in sourced reporting.▾
fire_root_cause_unknownperil classification pendingProperty
Market relevance: Root cause (electrical, mechanical, external) influences sublimit and exclusion discussions under property and engineering policies.
Sources conflict on whether the affected Delhi data centre is Google-operated or a third-party colocation facility used by Google Cloud; no authoritative confirmation of ownership has been disclosed.▾
data_centre_ownership_uncertaincoverage pathway ambiguityProperty
Market relevance: Ownership determines coverage pathway: a Google-operated facility routes to property/BI for the cloud operator and dependent BI for tenants; a third-party colo routes to the colo operator's property policy and to tenants' outsourced-IT/BI covers.
“third-party facility used by Google Cloud” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“Fire at Google Cloud data centre in Delhi” — timesofindia.indiatimes.com · 10 Jun 2026, 07:15 · mainstream media
No outage duration has been disclosed in available reporting.▾
outage_duration_undiscloseddata gapvalid from 10 Jun 2026, 16:49Property
Market relevance: Outage duration is a primary driver of business interruption severity for both the facility owner and downstream cloud customers.
Supersession history: 1 prior/revised claim rows.
No figure for affected commercial customers has been disclosed in available reporting.▾
customer_impact_undiscloseddata gapvalid from 10 Jun 2026, 16:49Cyber
Market relevance: Customer count is a key input for estimating cloud outage BI and cyber aggregation.
Sources conflict on whether the affected facility is a third-party data centre used by Google Cloud (three mainstream sources) or a Google Cloud data centre (one mainstream source). The ownership pathway materially affects whether the loss falls on a third-party property/BI policy, on Google Cloud's own property/BI cover, or on downstream cloud customer cyber/BI policies.▾
affected_facility_ownership_conflictloss pathway ambiguityvalid from 10 Jun 2026, 16:49Property
Market relevance: Ownership conflict drives whether property, cyber, or contingency BI covers respond; also affects aggregation analysis for cloud hyperscalers vs. colocation operators.
“Fire at third-party data centre hits Google Cloud services in Delhi, Mumbai, Chennai” — thehindubusinessline.com · 10 Jun 2026, 16:30 · mainstream media
“A fire at a Google Cloud data centre in Delhi has disrupted cloud services for users in the region.” — dailypioneer.com · 10 Jun 2026, 13:00 · mainstream media
“Google Cloud Outage In India As 3rd-Party Data Centre Fire Triggers Shutdown” — cobrapost.com · 10 Jun 2026, 12:15 · mainstream media
The root cause of the fire has not been disclosed in available reporting.▾
fire_cause_undiscloseddata gapvalid from 10 Jun 2026, 16:49Property
Market relevance: Root cause (electrical, mechanical, external) can influence property sublimits, deductibles, and loss prevention findings.
Supersession history: 1 prior/revised claim rows.
The exact name and location of the affected data centre have not been disclosed; dailypioneer.com references Delhi, but other sources do not specify.▾
affected_facility_location_undiscloseddata gapvalid from 10 Jun 2026, 16:49Property
Market relevance: Facility identification is required for property facultative placement and aggregation assessment.
“A fire at a Google Cloud data centre in Delhi has disrupted cloud services for users in the region.” — dailypioneer.com · 10 Jun 2026, 13:00 · mainstream media
The name, operator, and exact location of the affected data centre facility have not been disclosed.▾
affected_facility_identity_unknownseverity gapvalid from 12 Jun 2026, 02:55Property
Market relevance: Facility identity is needed to map exposure to specific colocation or hyperscaler property programmes
One source describes the affected facility as a Google Cloud data centre, conflicting with other reports that identify it as a third-party facility.▾
facility_ownership_google_cloudpathway ambiguityvalid from 10 Jun 2026, 13:09Property
Market relevance: If Google-owned, property exposure sits with hyperscaler self-insurance or dedicated tower; if third-party, colocation operator policy responds
“A fire at a Google Cloud data centre in Delhi has disrupted cloud services for users in the region.” — dailypioneer.com · 10 Jun 2026, 13:00 · mainstream media
The specific name and city/location of the affected third-party data centre in India are not identified in the available source.▾
data_centre_location_unknowncontext
933thedrive.com · 10 Jun 2026, 05:18
The root cause of the fire at the data centre is not identified in the available source.▾
root_cause_of_fire_unknowncontext
933thedrive.com · 10 Jun 2026, 05:18
No description of physical damage extent, facility value, or asset replacement cost has been disclosed.▾
physical_damage_extent_undiscloseddata gapvalid from 10 Jun 2026, 16:49Property
Market relevance: Physical damage scope is required to estimate property severity and BI indemnity period.
Sources conflict on whether the fire-affected facility is a Google-owned data centre or a third-party colocation facility used by Google Cloud.▾
facility_ownership_contradictedcoverage pathway ambiguityProperty
Market relevance: Ownership determination is critical to coverage pathway (facility property policy vs hyperscaler captive)
“Delhi data centre fire impacts Google Cloud services in India” — indianexpress.com · 10 Jun 2026, 14:15 · mainstream media
“Fire at data centre, Traffic rerouted from impacted facility in Delhi” — indiatimes.com · 10 Jun 2026, 07:15 · mainstream media
Sources conflict on ownership: Times of India (indiatimes.com) describes the Delhi site as a Google Cloud data centre, while Economic Times and Moneycontrol state the facility is third-party colocation used by Google Cloud. Google has not confirmed ownership or that its cloud services were affected by the fire.▾
datacentre_ownershipcoverage pathway ambiguityvalid from 10 Jun 2026, 00:00Property
Market relevance: Ownership determines whether the loss sits with a hyperscaler self-insured retention or a third-party colocation operator's property policy; affects reinsurance recovery assumptions.
“Fire at Google Cloud data centre in Delhi” — indiatimes.com · 10 Jun 2026, 07:15 · mainstream media
Sources conflict on whether the fire-hit Delhi facility is a third-party data centre used by Google Cloud, a third-party colocation tenant, or a Google Cloud edge node (e.g., Google Open Connect / GCP PoP). The Hindu identifies the site as a Tata Communications / Singtel / Megaport / Netflix / Google-adjacent carrier-neutral data centre, not a Google-owned hyperscale data centre.▾
facility_ownership_disputed_third_party_vs_googlecoverage pathway uncertaintyvalid from 14 Jun 2026, 13:47Property
Market relevance: Ownership determines whose property policy, whose BI, and whose contingent BI sub-limits respond; ambiguity blocks loss-pathway identification.
The specific name, operator, and exact city of the affected data centre have not been disclosed in available reporting. Delhi is referenced as the fire location in the Daily Pioneer account, but ownership and precise location remain unclear.▾
facility_identity_undisclosedinformation gapProperty
Market relevance: Facility identification is required to assess specific property and BI exposure and to determine which insurers and capacity providers may carry the loss.
Sources are inconsistent on whether the affected facility is a third-party data centre used by Google Cloud or a Google Cloud-operated facility. Three outlets (Hindu Businessline, Pakistan Today, Cobrapost) describe it as a third-party facility, while the Daily Pioneer describes it as a Google Cloud data centre.▾
data_centre_ownership_ambiguousownership ambiguityProperty
Market relevance: Ownership status determines the primary insurance pathway: facility owner's property policy (if third-party) versus cloud provider's own property/BI cover and customer-side contingent BI.
“Fire at third-party data centre hits Google Cloud services” — thehindubusinessline.com · 10 Jun 2026, 16:30 · mainstream media
“A fire at a Google Cloud data centre in Delhi” — dailypioneer.com · 10 Jun 2026, 13:00 · mainstream media
No insured loss estimate, broker or market loss figure, or claims/reserving action has been disclosed for this event.▾
insured_loss_not_disclosedno market loss estimateProperty
Market relevance: Absent any disclosed loss, quantum cannot be assessed; no aggregation signal for London Market carriers at this time.
No insurer, broker, reinsurer, or insured has disclosed an estimated property, business interruption, or cyber loss arising from the fire or linked outage.▾
insured_loss_disclosureuncertaintyProperty
Market relevance: Absence of any disclosed insured loss figure is the binding constraint on market materiality assessment.
No insured loss estimate, claims notification, reserving action, or market pricing reaction has been disclosed for this event.▾
insured_loss_estimate_not_disclosedloss pathway not confirmedProperty
Market relevance: Without an insured loss figure, London Market materiality remains bounded by equipment value only; cannot escalate beyond MEDIUM on current evidence.
No insured loss estimate, BI figure, or claims activity has been disclosed in available reporting.▾
loss_estimate_undiscloseddata gapvalid from 10 Jun 2026, 16:49Property
Market relevance: Absence of loss disclosure prevents severity banding; signal-stage assessment is retained.
“Fire Causes Google Cloud Outage In Key Indian Metros” — rediff.com · 10 Jun 2026, 11:00 · mainstream media
No insured loss estimate, business interruption figure, or claims activity has been disclosed in available reporting.▾
insured_loss_estimate_unknownseverity gapvalid from 12 Jun 2026, 02:55Property
Market relevance: Without loss estimate, no London Market pricing or reserving action can be anchored
No insured loss estimate, business interruption figure, or named insured exposure is available from the source.▾
insured_loss_or_bi_figure_unknownloss
933thedrive.com · 10 Jun 2026, 05:18
No claims notifications, reserving actions, or rating/pricing movements have been disclosed in available reporting.▾
claims_activity_undiscloseddata gapvalid from 10 Jun 2026, 16:49Property
Market relevance: Absence of disclosed market response keeps the event at signal stage.
No source quantifies the number of Google Cloud or colocation customers affected, nor the scope of disrupted services.▾
customer_impact_quantificationuncertaintyCyber
Market relevance: Customer-impact quantification is required to size contingent BI exposure across cloud-dependent insureds.
No source identifies the root cause of the fire (electrical, cooling, battery, external arson, etc.).▾
fire_root_causeuncertaintyProperty
Market relevance: Root cause affects sub-limit and exclusions analysis under property and equipment breakdown policies.
Google has not publicly confirmed that the fire caused the reported outage, has not identified the affected facility as part of its own infrastructure, and has not posted a Google Cloud status entry for the event in the sourced reporting.▾
google_official_acknowledgementuncertaintyCyber
Market relevance: Without Google confirmation, the linkage between fire and outage remains media-attributed; affects how property and cyber underwriters should weight the event.
No source provides an outage start time, end time, or total duration of the reported Google Cloud disruption.▾
google_cloud_outage_durationuncertaintyCyber
Market relevance: Duration is the primary driver of contingent BI severity; absence prevents any credible BI loss estimate.
The extent (scope of services) and duration of the Google Cloud outage in India are not specified in the available source.▾
outage_extent_and_duration_unknownstatus
933thedrive.com · 10 Jun 2026, 05:18
The duration, scope, and root-cause confirmation of any Google Cloud or related service disruption in India have not been disclosed by Google or by authoritative sources.▾
cloud_outage_duration_unknownkey data gapCyber
Market relevance: Outage duration is the single largest driver of contingent BI severity; without it, cyber/dependent-BI exposure cannot be quantified.
Affected countries
🇮🇳 India
Latest developments
- A fire at a Delhi data centre has been reported by multiple mainstream Indian outlets. — indianexpress.com
- Google Cloud users in Delhi, Mumbai and Chennai reported latency and service disruption following the fire. — indiatimes.com
- Reporting is inconsistent on whether the affected facility is Google-owned or third-party colocation, creating uncertainty over the relevant insurance coverage pathway. — indiatimes.com
- No insured loss, outage duration, customer-impact count, or claims activity has been disclosed publicly. — indianexpress.com
- The disruption was reported by users in three Indian metros: Delhi, Mumbai and Chennai. — indiatimes.com
- Outlets have framed the incident as a signal of concentration risk in regional cloud infrastructure. — indianexpress.com
- The event remains at signal stage pending loss or claims disclosure. — indianexpress.com
- Mainstream Indian outlets report a fire at a Delhi data centre linked to Google Cloud disruption in India. — indianexpress.com
Timeline
Corroboration18 Jun 2026, 18:16
A fire at a Google Cloud data center in India is causing ongoing service disruptions. The incident affects cloud computing services used by businesses globally, with potential implications for cyber, property, and business interruption insurance lines. No loss estimate or damage severity is available yet.
Source: datacenterknowledge.com (Mainstream Media) · View source
Corroboration18 Jun 2026, 12:50
A fire in Delhi disrupted Google Cloud services, raising concerns about cloud infrastructure resilience. The event potentially affects businesses reliant on Google Cloud services in India, with possible implications for cyber and technology insurance books.
Source: medianama.com (Mainstream Media) · View source
Status Change16 Jun 2026, 18:30
Status changed to monitoring
Auto-transitioned: no updates for 6 hours
active -> monitoring
Status Change16 Jun 2026, 12:02
Status changed to active
hygiene_sweep: re-evaluated after confidence recalibration
developing -> active
Status Change16 Jun 2026, 12:02
Status changed to developing
evidence_trigger: corroboration >= 2
signal -> developing
Corroboration15 Jun 2026, 04:06
A fire at a Delhi data centre has impacted Google Cloud services in India, causing latency and service disruptions for users. The incident highlights concentration risk in cloud infrastructure and potential business interruption exposure for businesses reliant on Google Cloud services in the region.
Source: indianexpress.com (Mainstream Media) · View source
Corroboration15 Jun 2026, 02:02
A fire at a data centre in Delhi has prompted Google Cloud to reroute traffic and manage network capacity. The incident highlights critical infrastructure fire risk at hyperscale cloud facilities, with potential business interruption and property loss implications for data centre operators and their insurers.
Source: indiatimes.com (Mainstream Media) · View source
Intelligence Refresh15 Jun 2026, 01:53
Corroboration14 Jun 2026, 20:26
A fire at a Google Cloud data centre in Delhi has caused service disruption, with traffic being rerouted from the impacted facility. The incident could trigger business interruption claims for cloud-dependent enterprises and property damage claims for the facility operator.
Source: indiatimes.com (Mainstream Media) · View source
Intelligence Refresh14 Jun 2026, 16:04
Lloyd's classifications
Tracking this kind of risk? Get an email when Energy & Infrastructure events escalate.
Get alerts