Ciberataques alegados contra Conviasa atribuidos a Anonymous

What this source supports

• @White_Hunters explicitly claimed the Conviasa portal was down and associated the action with Anonymous/CyberHuntersOp
• the 1144x768 actor-controlled Check-Host image names http://www.conviasa.aero/ and shows all visible locations as Connection timed out
• the image has blank time/code/IP columns and the screenshot does not preserve the permanent report target or a visible capture time
• the post and image establish claim provenance, not DDoS, cause, continuous duration, access or operational impact

Evidence limits

Actor-controlled screenshot lacks raw telemetry, baseline, visible time and reproducible permanent-report URL.

Relevance to this case

Exact primary provenance for the later target-specific claim; not proof of mechanism or causality.

What this source supports

• reports minister and Conviasa president Ramón Velásquez's public statement that Conviasa had been targeted by a cyberattack attributed to Anonymous
• says authorities acted to safeguard company information
• the article additionally says an attempt was made to access the database, but the quoted minister statement itself does not establish access or provide forensics
• does not publish outage duration, flight impact, technical mechanism or independent attribution

Evidence limits

Government allegation is primary for official attribution but lacks public technical evidence; database-attempt wording is the outlet paraphrase.

Relevance to this case

Strongest source for the initial 2 August government report and stated data safeguarding.

What this source supports

• reports a new ministerial allegation against the Conviasa portal on 11 August and says technical teams neutralized it
• separately reports attacks on Metro/Metrobus fare systems and a collapse/restoration of card-recharge service
• does not say Conviasa flights or booking operations stopped and supplies no target telemetry

Evidence limits

Several pages repeat one government statement; they are not independent technical confirmation.

Relevance to this case

Establishes a separately reported second Conviasa episode, not continuity from 2 August.

What this source supports

• reports the 11 August ministerial allegation about Conviasa and Metro/Metrobus payment systems
• reports a 21 August statement that Conviasa had recovered from attacks against several institutions
• most of the article concerns a distinct ASTRA/CNE claim and must not be treated as Conviasa evidence

Evidence limits

Derivative, advocacy-framed reporting combining unrelated CNE and Conviasa claims.

Relevance to this case

Later chronology/context only; ASTRA/CNE portions rejected for this incident.

What this source supports

• reproduces the 2 August government allegation and exact minister wording that information was safeguarded
• adds no independent target observation, technical evidence, operational effect or attribution

Evidence limits

Later archive of a derivative wire copy; confirms publication lineage, not the event technically.

Relevance to this case

Corroborates circulation of the initial official allegation.

What this source supports

• one sentence says Ramón Velásquez had reported a Conviasa cyberattack earlier that Friday
• the article principally documents a separate Ministerio Público portal outage
• provides no independent Conviasa observation, mechanism, duration or impact

Evidence limits

Single derivative sentence about Conviasa within an article about another victim.

Relevance to this case

Initial-report context only; not independent corroboration.

What this source supports

No supported claims are recorded for this source.

Evidence limits

Official-domain potential cannot substitute for inaccessible content, author/date metadata or archive.

Relevance to this case

Retained as provenance pointer only; rejected as independently verified official evidence.

What this source supports

• reports the minister's 11 August statement that the Conviasa portal had again been attacked and the attack neutralized
• states he recalled a similar 2 August episode
• separately reports Metro fare-system collapse/restoration; does not establish Conviasa flight or data impact

Evidence limits

Repeats a government allegation without telemetry; stored URL was not the indexed canonical slug.

Relevance to this case

Useful corroboration and chronology for the separate second episode.

What this source supports

• repeats the 325-site actor claim and names Conviasa in a broad alleged target list
• repeats the initial minister allegation and says information was safeguarded
• cites Canal Patria but adds no independent observation or technical evidence

Evidence limits

Low-transparency derivative source; later archive and no independent measurement.

Relevance to this case

Campaign/initial-statement corroboration only.

What this source supports

• reports that multiple users observed the Conviasa website down on the afternoon of 2 August
• carefully calls the cyberattack alleged/possible and reproduces the minister statement
• does not identify the users, preserve probes, establish duration or independently attribute the condition

Evidence limits

Unnamed user observations without raw measurements; medium support for a point-in-time public-site outage only.

Relevance to this case

Best non-government report of observed 2 August site unavailability.