Skip to main content
developingCyber

Russian Hosting Provider Beget Suffers Renewed Cyberattacks, Disrupting Major Platforms

Russian hosting provider Beget has experienced renewed cyberattacks, including a confirmed 850 Gbps DDoS attack, disrupting its infrastructure and causing outages for major Russian platforms Ozon, Wildberries, and Sber.

AI disclosure: Model-written assessment of the linked reports, not a verified fact. Check the sources. How Mosaic works

Reported3 of 6 key facts linked
Not measuredno reporting-volume measure is served for situations
Not assessedno severity is rated for situations
2 publishers2 reports

: Escalating (the model's assessment, not a measurement)

Nov 15First seen Nov 15Assessment written Nov 15
Why now
Newest report Nov 15: Hackers hit Russian hosting provider Beget again, disrupting Ozon, Wildberries, Sber (Important Stories).from the newest member report, published 15 Nov 13:35 UTC
Why it matters
These disruptions have potential cascading effects on Russian e-commerce and banking sectors, highlighting escalating cyber threats against critical infrastructure.
Affected
Russia (lead)countries named in the evidence; the lead is the country it is filed under, not an event location
Next catalyst
No scheduled catalyst known.Mosaic holds a schedule only for economic-calendar releases; 3 indicators to watch below
Watch in Monitor Export brief

Save keeps it in Monitor › Saved, without alerts. Watch opens Monitor with “Russian Cyber Disruption” as the subject.

Known and unknown

key facts by their own evidence status

Known

  • ReportedThe DDoS attack disrupted Beget's infrastructure.
  • ReportedBeget suffered a renewed cyberattack while attempting to restore infrastructure.
  • ReportedThe renewed cyberattack caused outages at major Russian platforms Ozon, Wildberries, and Sber.

Not established

  • Beget, a Petersburg-based cloud provider, suffered a large-scale DDoS attack peaking at 850 Gbps.
  • The origin and method of the renewed cyberattack.
  • The full impact of the DDoS attack.

stated, not yet supported by linked evidence

Indicators to watch

  • →Confirmation of attack attribution and methodology.
  • →Duration and scope of service disruptions at affected platforms.
  • →Official statements from Beget or Russian authorities regarding recovery efforts.

what would change the read; not a schedule

Evidence

Reported · 2 reports · 2 distinct outlets

Central claim Hackers hit Russian hosting provider Beget again, disrupting Ozon, Wildberries, Sber

2 reports, newest first. Each time is when the report was published, or when Mosaic recorded it if no publication time was given; event times are not recorded. Several outlets can carry one story, so a number of reports is not independent confirmation.

  1. published
  2. published
    Russian cloud provider Beget hit by 850 Gbps DDoS attackInterfax · Reported · Context · does not support the central claim

Connected

named in this situation's reports; not a claim that one causes another

Other situations in Russia

Loading…

Actors

Loading…

Anomalies

Loading…

Assessment

model confidence: under Technical details
Read the full assessment

Russian hosting provider Beget has experienced renewed cyberattacks, including a confirmed 850 Gbps DDoS attack, disrupting its infrastructure and causing outages for major Russian platforms Ozon, Wildberries, and Sber. The attacks suggest a deliberate effort to disrupt Russian digital services, with the origin and full impact remaining unclear.

AI disclosure: Model-written assessment of the linked reports, not a verified fact. Check the sources. How Mosaic works

Topics cyberattack · hosting · outage · russia · beget · ozon · wildberries · sber · ddos · cloud · infrastructure

Technical details
Impact score
5.1 / 10 · a priority score, not confidence
Model confidence
Medium: evidence reported (3 of 6 key facts linked to evidence; the model marked a key fact as unclear); 2 distinct outlets
Coverage focus
50% in primary evidence group
Coherence
0.87
Review state
published
Refreshed
Updated Nov 15, synthesized Nov 15. Not evidence time.
Cluster type
story
Member signals
2
Situation id
e5e23afe-885a-43ce-af7f-aa74bd823cd1
Last evidenceNov 15, 13:46 UTC
Last successful evaluationSuccessful evaluation timestamp unavailable (legacy)
Last attempt·

Public comments

…

Anyone who opens this situation can read these comments, with the author's display name. They are not private notes.

Sign in to post a public comment, contribute a source, or challenge the assessment.