Infrastructure Stress Event · h3xa-derived
country PH · PH
Unclassified disruption — derived from 1 independent signal across 13 observations.
Stress score460–100
Confidence15%
TrajectoryRESOLVED
Statusresolved
Explainable score
Stress score components
Anomaly magnitude100%
Breadth2%
Persistence100%
Corroboration0%
Baseline deviation5%
Confidence
Confidence factors
15%
method diversity25%
source agreement0%
timestamp overlap0%
infrastructure overlap0%
alternative explanations50%
statistical significance100%
Affected infrastructure
Scope
ASNs—
Services—
RegionsPH
Started2026-08-12 14:05
Last observed2026-10-02 10:00
Evidence
Underlying observations
voidly-atlas
Internet connectivity disruption in Philippinesincident--d62d5995-d76c-59ec-3eaf-90f1e2fb6721
voidly-atlasInternet connectivity disruption in Philippinesincident--683be88e-4ef4-530f-f329-95a7099fc159
voidly-atlasInternet connectivity disruption in Philippinesincident--31bcf9b3-b380-508d-95fd-6bc6a0405eee
voidly-atlasInternet connectivity disruption in Philippinesincident--5511521c-f630-59a6-cd53-331c44ac1ff1
voidly-atlasInternet connectivity disruption in Philippinesincident--4d6df2fb-0c7b-507f-4641-66409eb49905
voidly-atlasInternet connectivity disruption in Philippinesincident--1585f7dc-9b95-5c3a-4fcf-6227ba61d709
voidly-atlasInternet connectivity disruption in Philippinesincident--74dc02b8-d658-51e9-0c0a-1df305dd401f
voidly-atlasInternet connectivity disruption in Philippinesincident--bbac3683-ca61-5707-c9b5-8bbe37354050
voidly-atlasInternet connectivity disruption in Philippinesincident--fc9eae36-55d1-5d72-50d8-3b9f06a92dd7
voidly-atlasInternet connectivity disruption in Philippinesincident--a6fd5637-bf35-5f84-1b27-fd69ead9c87a
voidly-atlasInternet connectivity disruption in Philippinesincident--097061f7-efbd-558f-0acd-5c8761431a76
voidly-atlasInternet connectivity disruption in Philippinesincident--e45f46a4-c947-53bf-3b98-97f7616bb20b
voidly-atlasInternet connectivity disruption in Philippinesincident--97826e91-d1de-5162-be51-a2b102da8cde
Alternative explanations
What else could this be?
- single-source signal
- insufficient corroboration
Provenance
Ownership boundary
This event is an h3xa-derived analytical product. The evidence references above point to source-owned STIX observations; h3xa claims no ownership of the underlying data.