THERMAL ALERT ANALYSIS: NOVOKUYBYSHEVSK OIL REFINERY, RUSSIA
SITE
• Novokuybyshevsk Oil Refinery, Russia, refinery (crude refinery in Rosneft's Samara group)
• Owner-operator: Rosneft
• About 8.3 to 8.8 million tonnes per year nameplate (5.74 Mt processed in 2024); Volga-region refinery producing gasoline, diesel, jet fuel, bitumen and coke; struck repeatedly in this war (verified strikes 19 Oct 2025, 18 Apr 2026 and 22 Aug 2026)
• Adjacent major sites within about 10 km: none (Kuibyshev refinery and the Samara terminals sit more than 20 km away)
DETECTION
• No satellite thermal detection in the event window: a direct NASA FIRMS pull (VIIRS Suomi NPP, NOAA-20, NOAA-21 and MODIS, 2026-10-29 00:00 UTC to 05:50 UTC) returned zero detections within 15 km of the site for 2026-10-30, and none after 2026-10-29 08:35 UTC
• The only detections near the site in the pull are two small routine daytime pixels on 2026-10-29: Suomi NPP, 08:16 UTC, 3.53 MW, confidence nominal, 4.31 km WSW of the site; NOAA-20, 08:35 UTC, 1.98 MW, confidence nominal, 4.26 km WSW. Both predate the claim by about 18 hours and match normal complex heat
• Pass coverage of the window: the one regional pass before the reported attack, NOAA-20 at 00:07 UTC, predates ignition on every reported timeline (drone danger announced 01:05 UTC, attack underway by about 02:00 to 02:54 UTC). No post-ignition satellite pass had occurred or published by pull time; the next looks are Terra MODIS at about 07:10 UTC and the VIIRS day cluster from about 08:00 UTC. The null is therefore unproven, not a contradiction: it carries little weight until a post-ignition pass is checked, and a fire of the photographed scale still burning at the day passes would register strongly
• Map package attached: site, satellite and region views plus the plume view, which is rendered from the most recent NASA GIBS scene, dated 2026-10-29 and pre-event; the 2026-10-30 scene was not yet published at generation time, and no plume is shown or claimed
CONFIDENCE
• Event real at the site: HIGH, 85-92%
• Cause (Ukrainian drone strike): HIGH, 80-88%
• Damage or impact: no basis (no damage specifics have been claimed by officials or verified; which units, if any, are hit is unknown)
• Rationale: three different photographs from three different vantage points, all published between 03:57 and 05:02 UTC, show multiple thick black smoke columns over the town's industrial zone at dawn, and Samara's governor confirms on the record that a Ukrainian drone attack was being repelled over the oblast at the time. The satellite null does not cut against this yet because every satellite pass so far predates the reported ignition.
CORROBORATION
• Claimed: Osinttechnical on X, 04:15:38 UTC: the refinery is on fire this morning after reports of a Ukrainian drone attack; locals reported multiple pillars of smoke. One photo attached (town view at dawn, three smoke columns merging into one dark cloud, shot through a window)
• X cluster, same morning, same Ukrainian OSINT ecosystem but separate imagery: BohuslavskaKate at 03:57 UTC posted a CCTV-style still of three smoke columns from a low residential vantage; Exilenova+ on Telegram published its own dawn photo (golden-domed church in frame, two to three columns) carried by Ukrainian press by 05:02 UTC. Earliest located reporting is local Samara news at 03:06 UTC (07:06 local): Novokuibyshevsk in smoke, several fire sources in the industrial part of the city
• Russian officials: Governor Vyacheslav Fedorishchev posted the drone danger warning at 01:05 UTC and at about 02:54 UTC stated an attack by the Ukrainian Armed Forces was being repelled, with air defenses and mobile fire groups working, and told residents not to publish aftermath footage. Rosaviatsiya closed Samara Kurumoch airport under plan Kovyor at about 02:27 UTC, with Ulyanovsk, Kazan, Penza and Saratov also restricted, confirming a mass drone raid across the region that night. Russian operational services had not disclosed the fire's cause or scale as of 04:39 UTC, and regional authorities had not commented on the refinery itself
• Ukrainian officials: no General Staff claim yet as of about 05:55 UTC (their strike confirmations usually land later in the day). Context from Wall Street Journal reporting carried in Ukrainian press on 29 Oct: Kyiv had paused refinery strikes for about two weeks under US pressure, with the last large refinery strikes on 18 Oct; multiple outlets frame this attack as the pause ending
• Photo check: the claim photo is one of at least three mutually consistent dawn images from different vantage points published inside the same morning window, which is not the signature of a single recycled frame. No earlier use of the claim photo was found in the searches run; the X-served copy carries no EXIF, so its capture time cannot be proven from the file itself, and a frame-level match against the Aug 2026 and Apr 2026 strike imagery could not be completed with the tools available
• Status: UNVERIFIED; strongly corroborated by the governor's on-record attack confirmation and multi-vantage local imagery, but no wire confirmation of the refinery fire itself yet, damage unknown, and the satellite check is inconclusive rather than negative
WHY IT MATTERS
• Novokuibyshevsk makes jet fuel and diesel for the Russian military and has already lost primary processing once this year; a fresh outage lands while Ukraine's reported refinery-strike pause was the live question, so confirmation or a shutdown report moves the Russia products story
• The decisive open checks are the post-ignition satellite passes (Terra about 07:10 UTC, VIIRS day cluster from about 08:00 UTC) and any Reuters or General Staff confirmation later today
Coordinates: 53.09453, 49.9413 (district-level approximate)
Show more
THERMAL ALERT: ARAMCO RAS TANURA, SAUDI ARABIA
SITE
• Aramco Ras Tanura, Saudi Arabia, refinery (crude refinery)
• Owner-operator: Saudi Aramco
• 550 kbpd, the kingdom's largest refinery; Gulf coast at Ras Tanura, Eastern Province, beside the crude export terminal
• The same detection pixel also fired the adjacent Ras Tanura crude export terminal, about 2 km east; the two records are one physical event
DETECTION
• Aqua (MODIS), 2026-10-27 00:09 UTC: 1 hotspot, peak FRP 75.6 MW, confidence 100
• Single pass so far. The pixel sits 1.75 km east of the refinery center and 1.13 km from the export terminal center, on the complex's eastern side. Site baseline median is 3.0 MW, so this is 25.4x baseline; it is the only MODIS detection at the complex in 5 days, against routine flaring of 2 to 5 MW on VIIRS
• Timing: 5 minutes after the Civil Defense Eastern Province warning (00:04 UTC), inside the window in which the coalition says 3 ballistic missiles were intercepted
CORROBORATION
• X: the claim traces to one cluster resting on this same satellite pixel: man_600 at 02:34 UTC (unusual fire, began 3:09 AM, nine minutes after sirens; 3:09 AM local is 00:09 UTC, this detection), amplified by CocoPostel and by Hexagone Intel's post naming the refinery; Arabic posts repeat the same line. No ground photos, video, or local reporting from Ras Tanura itself
• Silent: Aramco and Saudi officials on the refinery specifically; tonight's wire reporting covers the interceptions and the all-clear and names no Ras Tanura impact. The prominent Ras Tanura fire stories in search results are from March 2026, a different incident
• Web: no news found yet for tonight
• Status: UNVERIFIED; cause unknown. Emergency flaring during the alert, interception debris, and an impact fire are each consistent with a single pixel; no damage extent is known
WHY IT MATTERS
• Ras Tanura is 550 kbpd of refining plus the kingdom's largest crude export terminal; a confirmed fire there is a supply event, which is why the call waits on a second pass or official word
• The next VIIRS passes decide persistence: a real blaze re-fires, a flare spike does not. The attached plume view is the most recent daytime scene (October 26), cloud over the coast; the detection was at night, so no plume is shown or claimed
Coordinates: 26.693, 50.0958
Show more
THERMAL ALERT: PETRORABIGH RABIGH, SAUDI ARABIA
SITE
• PetroRabigh Rabigh, Saudi Arabia, refinery (crude refinery, integrated refining and petrochemical complex)
• Owner-operator: PetroRabigh (Rabigh Refining and Petrochemical Co), Saudi Aramco and Sumitomo Chemical joint venture
• 400 kbpd; Rabigh, Red Sea coast, Makkah Province; the kingdom's west coast refining hub, next to the East-West pipeline's Red Sea corridor
• Adjacent sites within 10 km: none
DETECTION
• Hit 176, opened today: Terra, 2026-10-26 05:53 UTC (1:53 AM EDT): 2 hotspots, peak FRP 41 MW, confidence 77% (second pixel 31 MW at 59%)
• Escalation pass: NOAA-20 VIIRS, 2026-10-26 11:04 UTC (7:04 AM EDT): 1 hotspot, peak FRP 61 MW, confidence nominal
• All 3 pixels cluster 2.5 to 3.8 km southeast of the complex center, on the footprint. Site baseline median is about 2 MW, so today's peaks run 23 to 34 times baseline
• A fresh satellite pull at 18:40 UTC found no further detections. The VIIRS 10:09 and 10:43 UTC passes cited in the Hexagone post do not appear in the satellite record; the record holds the 05:53 and 11:04 passes only
• Plume check: the event-date NASA GIBS true-color scene (2026-10-26) shows no visible smoke plume over the complex
CORROBORATION
• X: Hexagone Intel (osinthexagone) posted at 15:12 UTC that the thermal hits suggest a possible fire or emergency flaring. The post reads the same NASA FIRMS imagery behind this alert, so it is an independent analyst on the same satellite evidence, not independent confirmation of a fire
• New claim layer: Sabereen News, a pro-Houthi outlet, claims a fire broke out at the refinery after a Yemeni strike (relayed in a Newsquawk market roundup). BrettErickson28 amplified at 16:11 UTC with unverified video said to show the refinery ablaze. Recycled footage is a proven risk at this site: a Reuters fact check on October 15 debunked a circulated Rabigh attack video that was actually a March 2026 fire in Fujairah
• The morning claim cluster stands: MerruX at 07:19 UTC plus pro-Houthi amplifiers, one information ecosystem
• Silent: sentdefender, AuroraIntel, and ELINTNews have posted nothing on Rabigh; Osint613 carries only the October 24 interception-debris item. No Aramco or PetroRabigh statement, and no Saudi official statement about the refinery
• Web: Reuters today reports Monday's Houthi claims as the East-West pumping stations and Riyadh airport; Saturday's claim named Rabigh among eight targets, with no Saudi confirmation of any hit. No wire reports a fire, damage, or shutdown at Rabigh today
• Site history: this complex had a satellite-verified major fire on October 5 (storage tanks damaged, 60 km smoke plume), Houthi-claimed and never confirmed by Saudi officials. That episode is closed; today's is a new episode at the same site
• Status: UNVERIFIED; cause unknown, damage unknown. Emergency or upset flaring remains fully consistent with pixels of this size
WHY IT MATTERS
• A second real fire at Rabigh inside a month, on top of the October 5 tank damage, would tighten Red Sea product supply while the East-West pipeline is the kingdom's Hormuz bypass, and Rabigh sits in the active claim theater around that pipeline
• The signal is still satellite-only. It upgrades on a wire or Saudi confirmation of damage, or growth on later passes; it downgrades if the pixels fade with no follow-on
Coordinates: 22.7293, 39.0133
Show more
THERMAL ALERT: RYAZAN REFINERY, RUSSIA
SITE
• Ryazan refinery, Ryazan, Russia: 17 Mt/year nameplate capacity (about 340 kbpd), effective throughput about 262 kbpd (13.1 Mt processed in 2024), operated by Rosneft
• A key fuel supply source for Moscow, about 300 km northwest, via product pipelines, though not the capital's sole source
• The plant has been shut down since the Ukrainian strike of September 6, 2026, which caused major damage to CDU-6 and CDU-4. Reuters industry sources describe CDU-1, CDU-3 and CDU-4 as continuing to operate, which implies partial operation rather than a complete stop
DETECTION
• NASA FIRMS satellite thermal data at the plant: daily peak fire radiative power of 0.71 MW on October 12, 6.19 MW on October 15, and 20.38 MW on October 16, a clear two-day thermal event at a plant that should be near cold
• Independent reporting of the same satellite data detected at least one fire at the tank farm overnight October 15-16
THE EVENT
• Wave 1, October 15: mass Ukrainian drone and missile attack. Governor Pavel Malkov confirmed a fire at the refinery, with material damage being assessed and no casualties, plus a warehouse and vehicles damaged at a separate Ryazan enterprise. The Defence Ministry said 4 Flamingo cruise missiles and 69 UAVs were intercepted and that falling debris caused the fire. Reuters and AP carried the strike the same day
• Wave 2, overnight October 15-16: Ukrainian OSINT reported the fire continued all night, with one to three tanks burning. Governor Malkov's overnight statement conflicts: five drones intercepted, no damage or casualties
• No official Ukrainian General Staff claim for Ryazan as of the latest wires; an unnamed Ukrainian official confirmed the hit to AP
THE VIRAL POST, CLAIM BY CLAIM
• The video: not this event, high confidence. The clip shows a huge fireball inside the plant with snow covering the ground. Ryazan's night low on October 15-16 was about 46F, with no snow cover. Verified footage of this strike is a distant smoke glow over the city, and state TV showed a relatively small black smoke plume with no fire visible. The clip's scene and season match the January 24, 2025 Ryazan strike. Treat it as winter archive footage
• Unit AT-6 stopped: half true and materially incomplete. Reuters reported on October 16, citing two industry sources, that CDU-6 (AT-6 is the same unit's Russian designation) was halted after Thursday's attack and several pipelines were damaged, with CDU-1, CDU-3 and CDU-4 operating. But CDU-6 had already been suspended after the September 6 strike. An already-down unit's halt was renewed, not a fresh kill
• 17 Mt/year: correct as nameplate. Effective throughput is about 262 kbpd
• Supplies Moscow: confirmed, as qualified above
• Another refinery down: wrong framing. The plant has been down since September 6. This is a re-strike on a damaged plant, extending its outage and hitting its tank farm, not a new loss
DAMAGE PICTURE
• Confirmed by officials: fire at the refinery on October 15, no casualties
• Sourced but single-lineage: CDU-6 halt and pipeline damage (two unnamed industry sources via Reuters; Rosneft has not commented)
• OSINT only: one to three tanks burning overnight, consistent with the satellite thermal data. Nothing credible yet on storage volumes destroyed or on second-wave unit damage
WHY IT MATTERS
• Re-striking an already-down plant is a keep-it-down campaign: every additional hit on distillation units, pipelines and tankage pushes a restart further out, and Ryazan is the largest single supply source for the Moscow region
• The open question that matters: if CDU-1, CDU-3 and CDU-4 are genuinely running, the plant is partially operating at reduced rates rather than fully shut, and Russian product balances sit between the two readings
Coordinates: 54.5759, 39.7437
Show more
THERMAL ALERT: PENGERANG COMPLEX, MALAYSIA
SITE
• A single thermal hotspot generated alerts for three co-located sites at Pengerang, Johor, Malaysia
• Pengerang Refining (RAPID/PRefChem), Malaysia, refinery: 300 kbpd crude throughput, operated by Pengerang Refining Company, owned by Petronas 50% and Saudi Aramco 50%
• Pengerang Independent Terminals (PITSB), Malaysia, bulk terminal: 1,700,000 m3 storage, operated by Pengerang Independent Terminals Sdn Bhd
• Pengerang Terminal (Two) Phase 2, Malaysia, bulk terminal: 2,100,000 m3 storage, operated by Pengerang Terminals (Two) Sdn Bhd
• The detection pixel sits about 0.2 km from the two terminal sites and about 2.2 km from the refinery site, so the terminal sites are the nearer candidates
• Adjacent watchlist sites within about 10 km include the rest of the Pengerang complex: Pengerang Deepwater Terminal, Pengerang Petrochemical Complex, Pengerang Gas Separation Plant, Pengerang Co-generation Plant, Pengerang Integrated Complex Utilities and Facilities, and Pengerang LNG Regasification Terminal
DETECTION
• Hits 143, 144 and 145: Terra, 13:25 UTC on October 16, 2026 (9:25 AM EDT, 9:25 PM local): 1 hotspot, peak FRP 65 MW, confidence 100%
• Single pass, single pixel, night detection. Site baseline median 2 MW, alert threshold 30 MW
• One physical detection created all three alerts. This is not three separate events
CORROBORATION
• X: no posts found for Pengerang fire, Pengerang explosion or PRefChem fire. Standing OSINT accounts checked were silent
• X posts mentioning Pengerang today cover regional haze and air quality readings in Johor, not a plant incident
• Silent: the operator and official sources have not posted any incident statement found in this check
• Web: no news found yet for an October 16, 2026 incident. Search results were historic Pengerang incidents only
• Status: UNVERIFIED. No damage extent is known
WHY IT MATTERS
• Pengerang is a major Southeast Asia refining and petrochemical complex. A confirmed fire at the 300 kbpd refinery or its supporting terminals would matter for regional product supply
• With no corroboration so far, this stays a satellite-only signal until a second source confirms or clears it
Coordinates: 1.37495, 104.15937
Show more
THERMAL ALERT: SOHAR, OMAN
SITE
• Sohar industrial port area, Oman, on the Gulf of Oman
• Two candidate sites share one detection: OQ Sohar refinery (198 kbpd, operated by OQ, the Oman state energy group) and the adjacent Oiltanking Odfjell Terminal Sohar (Advario), 1,294,780 cubic meters of clean products and petrochemicals storage in 66 tanks
• The detection sits 2.58 km southeast of the refinery center and 5.72 km southeast of the terminal center, so it reads closer to the refinery
DETECTION
• Terra MODIS, October 15, 2026, 16:09 UTC: 1 hotspot, 30.56 MW, confidence 90
• Single nighttime pass. The site baseline median is 3.8 MW, so this is 8.1 times baseline and just above the 30 MW alert threshold
• One pixel generated both site alerts. This is likely one physical event, not two separate fires
CORROBORATION
• No post found on X about a Sohar refinery or terminal fire, strike, or explosion
• No news found yet for an onshore Sohar incident. The only Sohar fire reporting today is a separate offshore tanker engine-room fire about 21 nautical miles northeast of Sohar at 06:05 UTC, a different location and time
• Status: UNVERIFIED. Damage extent unknown, no damage claimed by any source
WHY IT MATTERS
• A 198 kbpd refinery and a major products terminal sit next to each other at Sohar. A real fire at either would matter for regional product supply
• A single pass just above threshold, with no ground confirmation, is as consistent with a flare or process upset as with a fire. A second satellite pass or ground reporting decides it
Coordinates: 24.46508, 56.6285
Show more
Thermal Grizzly and Noctua have teamed up on a new WireView Pro II that monitors a GPU’s 12V-2×6 power connector.
It tracks power through each pin, warns of uneven load, and can trigger an emergency shutdown if it detects a serious problem.
The Noctua version adds an aluminium heatsink and a 40 mm fan that stays off at lower loads and only turns on when needed, keeping the device quieter while helping with cooling.
It costs $189.90, which is not cheap for a GPU monitoring device.
Show more
Thermal Insulation Coating Market Report- Forecast to 2023
🛑 Thermal ICE Tase 🛑
ICE put an illegal alien on the ground in Thermal, California, and the video looks like a tase after he refused to go easy.
I’m noticing more illegal aliens fleeing and fighting ICE instead of complying. Either they are desperate to keep living the good life off the backs of U.S. citizens, or somebody is telling them to put up a fight. Either way they are paying for it with pain. Resisting or assaulting federal officers is how you turn a removal into a federal case under 18 U.S.C. § 111.
And this is California. SB 54, the California Values Act, is the sanctuary statute that limits how much locals can help ICE inside the jails, which is exactly why street arrests look like this. Riverside County Sheriff Chad Bianco joined Huntington Beach’s federal challenge to that law, and DOJ has already called the Values Act unlawful.
Even under SB 54, Riverside’s sheriff reported 43 transfers to ICE in 2025, up from 13 the year before. The state still makes federal officers do the hard part in public, and illegal aliens who resist are finding out what that costs.
Show more