What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
On 27 October 2022, Slovakia’s parliamentary voting system was disrupted and Poland’s Senate website hosting servers were hit by a reported distributed denial-of-service (DDoS) attack. The incidents affected different systems. Slovakia’s Speaker initially called the voting disruption a hacker attack, but later qualified it as a cybersecurity incident whose cause was unknown; a follow-up report said it was not yet clear whether hacking had occurred.
What happened in Slovakia?
During a sitting of Slovakia’s National Council on 27 October 2022, the parliamentary voting system could not be used. Speaker Boris Kollár announced a 15-minute break so technicians could secure voting. The disruption continued to affect proceedings, and he later suspended the sitting until 8 November. The official transcript records that the source had not been identified.
Kollár’s first announcement described the problem as a hacker attack. Later in the sitting, he called it a serious cybersecurity incident while allowing that it might not have been a hacking incident. A report published the next day said the technical problem had been removed but that it was still unknown whether an actual hacker attack had taken place. The distinction matters: the voting disruption is documented, but its cause was not confirmed in these accounts.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Sources: Slovak National Council sitting transcript, 27 October 2022; STVR follow-up, 28 October 2022.
#1 Best Overall
What happened to the Polish Senate website?
The Polish Senate Information Centre reported a DDoS attack on the servers hosting the Senate website during the morning of 27 October. A DDoS attempts to disrupt an online service by directing large amounts of traffic at it. The Centre described the traffic as coming from multiple directions, including Russian territory, and said security procedures were deployed. It reported that the website was functioning normally.
The reference to Russian territory describes reported network traffic, not the identity of the people or organization responsible, and does not attribute the attack to the Russian state.
Source: Polish Senate Information Centre notice via PAP MediaRoom, 27 October 2022.
How the two incidents compare
| Category | Slovakia | Poland |
|---|---|---|
| Affected system | Parliamentary voting system | Servers hosting the Senate website |
| Reported effect | Voting could not proceed; the sitting was interrupted and later suspended until 8 November | DDoS was reported; the Senate Information Centre said the website was functioning normally after security procedures |
| What was established about cause or traffic | The official transcript said the source was unknown; next-day reporting said it was not clear whether the incident was a hacker attack | The Senate Information Centre described a multi-directional DDoS, including traffic from Russian territory, but did not identify the responsible actor |
| Recovery information | Follow-up reporting said the technical problem had been removed | The Senate notice said the website was functioning normally |
Do the incidents prove a coordinated attack?
No. Both were reported on the same date, but they involved separate systems and the available records do not establish a shared attacker, campaign, or cause. Poland’s Senate had adopted a resolution calling Russia’s authorities a terrorist regime during a sitting that ended overnight into 27 October. That timing is context, not proof that the resolution caused the DDoS.
ENISA’s October 2022 Cyber Security Brief discusses pro-Russia hacktivists targeting Polish and Slovakian parliaments. That wider threat context does not identify who caused either specific event or confirm that they were linked.
Quick Recap
Best Value
What is—and is not—known about attribution
- Slovakia: The voting disruption and interruption of proceedings are recorded, but the available official and follow-up accounts do not establish who or what caused them.
- Poland: The Senate Information Centre reported a DDoS and traffic from multiple directions, including Russian territory. It did not name an operator or sponsor.
- Both incidents: The cited records do not establish a common campaign, a motive linking the events, data theft, or persistent compromise.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
