Updated daily at 09:00 (EET) Index 5.1 = 0.0 elevated
Issue of October 4, 2026 · SundayNo. 124

Vilnius: a yellow alert, NATO fighters scrambled, the object not found

5.1/10 elevated = 0.0vs. previous issue
In this issue ▾
  1. Top stories of the day
  2. By area, in detail
  3. Contradictions and discrepancies
  4. Escalation risk assessment (0–10)
  5. Sources

Issue of 4 October 2026 — for the period 3–4 October 2026.

Note: On the morning of 3 October Lithuania issued a yellow air alert in Vilnius County and Ukmergė: NATO fighters took off, the airport closed its controlled airspace for a time, the object was not found and has not been officially called a drone. In the evening CERT closed the Saeima election day with no incident affecting the vote. The overnight list of 559 drones does not include the northwest, and there was no shot. (Previous issue — 3 October 2026, risk 5.1/10.)


Top stories of the day

  1. 03.10 — Vilnius: a yellow alert, NATO fighters scrambled, the object not found. LRT (English version, 03.10, 09:52) writes that at about 09:50 a yellow alert for a possible air threat was issued, indicating that a possibly dangerous object had crossed into Lithuania's airspace; the warning affected Vilnius County and was called off about 50 minutes later. The Lithuanian LRT live page (03.10, 09:50) records the cancellation at 10:37 and quotes Darius Buta of the National Crisis Management Centre (NKVC): the object flew into Lithuania from Belarus. 15min (03.10, 09:48, updated through 14:00) writes that the yellow alert in Vilnius County and Ukmergė was cancelled at 10:30. Vakarų ekspresas (03.10, 10:06, updated 10:59) quotes an armed-forces post: all-clear in white, the fighters recorded no object in the area, and an air-force helicopter will additionally inspect the place where the radar mark disappeared; the airport resumed operations and warned of possible delays. The afternoon LRT text (03.10, 13:22, updated 13:40) and 15min (03.10, 13:40) carry the afternoon press conference of NKVC director Vilmantas Vitkauskas: the object was not identified and not found, and the search was stopped at about 13:00; the mark was recorded outside Lithuania, on Belarusian territory, the heading was toward Vilnius and on toward Ukmergė district, and the mark disappeared before reaching Vilnius. 15min, in a direct quote, adds that visibility was lost in Vilnius district. Vitkauskas says it was not necessarily a drone: the speed was lower than usual for an unmanned aircraft, and an anomaly or a flock of birds is possible. The same afternoon LRT quotes the armed forces: a helicopter surveyed the place where the contact vanished and the surrounding area, found no suspicious objects, and is returning to Kaunas. The NATO mission fighters took off from Šiauliai. These texts do not describe a shot. There was no red alert. Neither the figure nor the fact is presented as an established airspace violation: the morning wording about an entry and the afternoon refusal to call the object a drone diverge, and no wreckage was found. The figure of 12 flights is only in the afternoon LRT; there is no second count, and it is not used as established. Sources: LRT, English version (03.10.2026, 09:52); LRT, Lithuanian live page (03.10.2026, 09:50); LRT, search closed (03.10.2026, 13:22); 15min, press conference (03.10.2026, 13:40); 15min, alert and all-clear (03.10.2026, 09:48); Vakarų ekspresas (03.10.2026, 10:59).

  2. 03.10 — The Saeima election day is closed: CERT recorded no cyber incident affecting the vote. The CERT.LV entry of 3 October at 20:30 says the election day as a whole passed without incident, and that no threats or cyber incidents that could affect the conduct of the vote were identified. Monitoring found unsuccessful attempts to look for vulnerabilities on individual government websites; they did not affect residents' data or the operation of the resources. Sites with names similar to those of agencies and media outlets were also found, as were resources copying the Central Election Commission site. No malicious content was found on them, and monitoring continues. The overall cyber-threat level is still called high, and the situation in cyberspace stable. Jauns.lv (marked "yesterday, 21:00", that is 3 October) retells that entry and adds that one unofficial site republished public CEC information on candidates' debts, arranged differently from cvk.lv; CERT found no malicious code and no attempt to harvest data. This is one agency bulletin in two texts, not two independent counts of attacks. They do not describe an attack that affected the vote. The next CERT review is set for 4 October at 10:00; at compilation, 09:06 Tallinn time, it was not out. Sources: CERT.LV — entry of 03.10.2026, 20:30; Jauns.lv (03.10.2026, 21:00).

  3. 04.10 — The night is closed by a tally of 559 drones; the northwest is not on the list. Interfax (04.10, 08:31) and Kommersant (04.10, 08:40) carry a defence-ministry tally: from 20:00 on 3 October to 08:00 on 4 October, 559 drones were shot down over Astrakhan, Belgorod, Bryansk, Volgograd, Voronezh, Kaluga, Kursk, Oryol, Rostov, Smolensk and Tula oblasts, the Moscow region, Krasnodar krai, Adygea, Crimea, and the Azov and Black seas. Kommersant calls this 15 regions and two seas. Leningrad, Pskov and Kaliningrad oblasts and St Petersburg are not on the list. This is one ministerial tally in two outlets, not two counts. The daytime list for 4 October, from 08:00 to 20:00, was not closed at 09:06. Sources: Interfax — 559 (04.10.2026, 08:31); Kommersant — 559 (04.10.2026, 08:40).

  4. 03.10 — Daytime: 244 in Interfax, the northwest absent; the overnight 218 is now also in Kommersant; "680 in a day" does not add up with these windows. Interfax (03.10, 20:15): from 08:00 to 20:00 on Saturday, 244 drones were shot down, including over the Moscow region, and the oblast list names Belgorod, Bryansk, Kaluga, Kursk, Oryol, Smolensk and Tula, plus Adygea, Crimea, Krasnodar krai, and the Azov and Black seas. The northwest is not on that list. A second retelling outside the restricted-source list was not found. Vzglyad — access blocked by Baltic regulators, no direct link — and RIA Novosti (Crimea) — an EU-sanctioned outlet, no direct link — repeat the same ministerial tally; that is not an independent count. The night of 3 October, 218, which the 3 October issue had seen only in Interfax by 09:02, is now also in Kommersant (03.10, 08:54): the same oblasts, without the northwest. It is still one tally, not a second count. A separate Interfax text of 3 October says that "over the day" 680 drones and six guided bombs were neutralised, and that strikes were delivered on 149 areas. The 680 item has no oblast list. 218 and 244 sum to 462, not 680. 680 is not used as the geography of the Baltic line and is not added to 218 and 244. Sources: Interfax — daytime, 244 (03.10.2026, 20:15); Kommersant — overnight, 218 (03.10.2026, 08:54); Interfax — overnight, 218 (03.10.2026, 08:53); Interfax — "over the day", 680 (03.10.2026).

  5. 03–04.10 — No confirmed violation of NATO airspace; no new Polish scramble was found. The yellow alert in Vilnius (item 1) was cancelled without identification and without a find. There was no shot. For 3 October and the morning of 4 October, the LRT, LSM, ERR and Polish pages reviewed contain no new RCB alert for the eastern border, no new pause at the Lublin and Rzeszów airports, and no new Operational Command notice of a scramble. No violations of Latvian or Estonian airspace were found for the window. No new official kilometre count for Eastern Shield dated 3–4 October was found. Sources: item 1; no separate Polish release for this window was found.


By area, in detail

Construction of military facilities and fortifications

  • No new section of the Baltic Defence Line and no new kilometre count of ditches, dragon's teeth or Eastern Shield dated 3–4 October was found. An Onet podcast of 3 October about a visit to the border retells the programme and is not a new army tally of length; old round figures are not repeated here as a fresh report.
  • Rūdninkai and Rukla remain the statement of 2 October. No new construction text was found for this window.

Deployment and movement of forces

  • The German brigade. No text was found after the Lithuanian draft of 2 October, already covered, and the English page stamped 3 October. There is no battalion arrival in this window.
  • "Vyčio skliautas 2026" ends on 3 October on the dates announced earlier. No separate report that the training camp in Lazdijai had opened was found. The calendar end is not used as a completed fact of the camp.
  • Namejs 2026 runs until 8 October. No dated Namejs episode for 3–4 October was found.
  • "Perkūno griausmas 2026" runs until 15 October. No new dated episode was found.
  • The Estonian Military Academy in Tartu. The announcement of 29 September of an exercise running until 5 October remains background. There is no new episode in the window. No page is opened.
  • Four German Eurofighters at Lielvārde remain the fact of 24 September. No report of a departure on 3–4 October was found.
  • No new decision on the timing of the U.S. rotation to Lithuania was found for this window.
  • No new named exercise with dates, scale and content, confirmed by two sources and not already given a page, appeared. "Zapad-2026" is not being held. "Ussisõnad-2026" is not independently confirmed. A completion of "Tvirtas skydas 2026" is not confirmed by a fresh Lithuanian text in the window; the previously announced end date of 2 October is not presented as a new fact.

Agreements and spending

  • No fresh European Commission answer to the letter on €500 million for counter-drone defence was found for 3–4 October.
  • No new budget law and no new contract sum were found for the window.

Military aid and air defence / electronic warfare

  • The Vilnius alert (item 1). A fighter scramble and a helicopter survey, not an intercept and not a new battery entering service. SkyFortress remains the pilot of 2 October. The May timing for the radars of the second NASAMS battery was not updated by a fresh text.
  • Polish identification procedures remain the fact of 30 September. No use of weapons on 3–4 October was found in the texts reviewed.
  • CERT.LV (item 2). Election day is closed by the negative bulletin of 20:30. The 4 October review set for 10:00 was not out at compilation.
  • The training incident at Ādaži received no new medical update in the window.

Kaliningrad and Russia's border regions

  • The night of 4 October (item 3) and the day of 3 October (item 4). The northwest is absent from both closed lists. The day of 4 October is not closed by a general list.
  • The night of 3 October, 218. The second non-registry retelling is Kommersant, 08:54. The northwest is absent. The 3 October issue honestly said that a second retelling had not been found by its compilation.
  • "680 over the day" (item 4). One Interfax item without geography. It is not tied to the Baltic line.
  • Belgorod, the evening of 3 October. Kommersant (03.10, about 22:40) carries Governor Alexander Shuvaev on injured people, including children. This is one regional text. The number of injured is not used as established. Belgorod is not the Baltic northwest.
  • Bryansk, 145, and Kursk, more than 200. Governors' posts carried by Interfax (03.10) are separate regional windows. They are not added to the national figure and do not touch the northwest.
  • The Baltic Fleet. AiF-Kaliningrad (03.10, 08:36) carries a fleet press service: the submarine Velikiye Luki, on a range in the Baltic Sea, practised detecting a notional submarine, a training torpedo shot and evasion. The text does not date the shot itself. The same item on 2 October, before the window, is in Vzglyad citing RIA Novosti; Vzglyad — access blocked by Baltic regulators, RIA Novosti — an EU-sanctioned outlet, no direct links. This is one press-service statement, not two independent observations and not combat firing. The shot is not counted as a driver of these days.
  • Belarus. No separate dated text of 3–4 October on drills by the Polish or Lithuanian border was found. The morning link of the Vilnius mark to a heading from Belarus is covered in item 1 and did not become a found aircraft by the afternoon.
  • The FSB regime by the Estonian border. No separate note of 3–4 October on extending or lifting the previously stated period was found.
  • No new note on Kaliningrad and no new NATO reply were found for this window.

Statements by officials

  • Lithuania — V. Vitkauskas, 03.10, afternoon press conference (LRT and 15min): the object was not found, the search was stopped, and it is not necessarily a drone. One press conference in two outlets.
  • Lithuania — D. Buta, morning of 03.10 (LRT): the object flew in from Belarus. That is an early formula; the afternoon text does not confirm it as an established drone (item 1).
  • Lithuanian Armed Forces, 03.10: the fighters recorded no object (Vakarų ekspresas); the helicopter found no suspicious objects (LRT).
  • No new statement by the Russian defence minister on the Vilnius alert or on the CERT bulletin was found in non-registry sources by compilation.

⚠️ Contradictions and discrepancies

  • "Flew in from Belarus" and "not necessarily a drone". Morning LRT carries Buta: the object flew into Lithuania from Belarus. English LRT at 09:52 writes that the alert indicated a crossing of the airspace. In the afternoon Vitkauskas says the mark was recorded on Belarusian territory and disappeared before reaching Vilnius, that the parameters do not fully match a drone flight, and that until the object is found they will not call it a drone. LRT's paraphrase says the mark was recorded outside Lithuania. 15min, quoting the same conference, adds the loss of visibility "in Vilnius district". Vilnius district is Lithuanian territory, while the city of Vilnius is not described as reached. None of the formulas is used as an established violation with a found aircraft.
  • The time of the all-clear. 15min writes 10:30. The Lithuanian LRT page writes 10:37. English LRT says "about 50 minutes" after about 09:50. Vitkauskas in the afternoon speaks of a process of about 40 minutes. The score uses a short yellow alert with an all-clear the same morning, not a choice of one minute.
  • "12 flights". Only the afternoon LRT. There is no second count.
  • 218 + 244 and 680. The overnight and daytime windows of 3 October in the defence-ministry texts carried by Interfax and Kommersant do not sum to 680. The 680 text has no oblast list and also describes six bombs and strikes on 149 areas. That is a different daily form, not the geography of the Baltic contour.
  • Injuries in the south. Evening Belgorod in Kommersant is one governor. It is not tied to the score. The Kaluga injuries on the night of 3 October remain what the 3 October issue left them as: one regional post.
  • No substantive error in previous issues was found that needs an entry in corrections.json. The 3 October issue was compiled at about 09:02, before the yellow alert at about 09:50, and wrote that no new violation had been found by its compilation. That is not a claim that the alert of 3 October did not happen. The score for 3 October is not recalculated.

📊 Escalation risk assessment (0–10): 5.1 / 10

Overall score: 5.1 / 10. Unchanged from the issue of 3 October. The nearest historical analogue is a tense late-Cold-War confrontation (≈3–4), with a premium for the drone shootdown over Lithuania on 15 September, for strikes a few kilometres from the Polish border in earlier windows, and for nuclear-tinted rhetoric around Kaliningrad. Noticeably below Able Archer 1983 (≈7) and the run-up to 2008/2014 (≈6–7): the object near Vilnius was not found and has not been officially called a drone, there was no shot, the northwest is absent from the closed lists, and the brigade remains a plan for 2027.

Drivers on the Russian side and its ally:

  • Strikes on Russian territory continue. The night of 4 October (559) and the day of 3 October (244) do not include the northwest. The figures are ministerial. The day of 4 October is not closed by a general list and is not presented as "quiet". "680 over the day" is a different form without geography.
  • Injuries in Belgorod are one evening text. They are not tied to the Baltic line.
  • The training torpedo shot by Velikiye Luki is one press-service statement, the text does not date the shot, and the same item was already in a registry retelling on 2 October. It is not combat firing.
  • Belarus. There is no fresh text on drills by the border. The morning link of the Vilnius mark to a heading from Belarus did not become a found aircraft after the afternoon refusal of the word "drone" and an empty survey.
  • The FSB regime by Narva was not extended or lifted by a fresh decision.
  • No new note on Kaliningrad.

Drivers on the NATO side and individual members:

  • The yellow alert in Vilnius is a fighter scramble and a temporary closure of the airport's controlled airspace. It is a defensive procedure. The object was not identified, the helicopter found nothing, and no weapon was used.
  • The German brigade draft added no new people in these days.
  • Polish identification procedures remain in force as the measure of 30 September. No use of weapons and no new scramble were found in the window.
  • "Vyčio skliautas 2026", Namejs 2026 and "Perkūno griausmas 2026" run on previously announced dates. There is no new episode in the window.
  • The CERT bulletin describes an election day without an incident affecting the vote, and does not describe an attack that took place.

Mutual / structural factors:

  • The Russia–Ukraine war remains the background of the overnight and daytime lists.
  • The calendar: the Saeima election was held on 3 October, "Vyčio skliautas" ends on 3 October by plan, and the Lithuanian constitutional vote is set for 6 October.
  • There is no nuclear topic in this window. The CERT review for 10:00 on 4 October was not out at compilation.

Stabilisers (both sides):

  • The object near Vilnius was not found, the alert was cancelled the same morning, and there was no shot. No new Polish scramble was found.
  • The northwest is absent from the closed lists for the night of 4 October and the day of 3 October. The day of 4 October is not closed by that.
  • The submarine's training shot is not described as combat and is not dated to these days inside the text itself.
  • Election day is closed by a bulletin with no incident affecting the vote.
  • Belarusian drills are not tied to the border by a fresh text.
  • No talks on nuclear weapons were announced in this window.

Why this score: holding 5.1 follows from the yellow alert not becoming an established violation and not becoming a use of weapons. Closed lists without the northwest do not add a strike on the Baltic contour. The class of events that has held the score since mid-September did not change.

Delta from the previous issue: = (0.0) — 5.1 (3 October) → 5.1 (4 October). Reason: a cancelled alert without a find and without a shot does not create a new contact with the NATO line beyond the September shootdown already counted.

Disclaimer: this is an analytical assessment from open sources, not a forecast.


Sources