Catchpoint experienced a minor incident on June 19, 2025 affecting Application Data, lasting 3h 10m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Jun 19, 2025, 07:49 AM UTC
We have identified an issue with a subset of our backbone nodes which caused a data gap between 6:09 UTC to 6:49 UTC on June19th 2025. Please find below the list of impacted nodes. * Amsterdam, NL - TELIA * Athens, GR - Cogent * Atlanta, US - Level3 IPv6 * Atlanta, US - Zayo IPv6 * Auckland, NZ - Vocus * Baghdad, IQ - EarthLink * Batam, ID - PT Telekom IPv6 * Berlin, DE - Versatel IPv6 * Billings, US - Lumen IPv6 * Boston, US - VZN IPv6 * Brasilia, BR - EdgeUno * Brasilia, BR - EdgeUno IPv6 * Bucharest, RO - RDS * Chennai, IN - Vodafone IPv6 * Chicago, US - Level3 IPv6 * Chicago, US - Unitas IPv6 * Chicago, US - VZN IPv6 * Curitiba, BR - EdgeUno IPv6 * Dallas, US - NetActuate IPv6 * Dallas, US - Telia * Frankfurt, DE - DTAG * Frankfurt, DE - Verizon * Kathmandu, NP - Data Hub * La Paz, BO - EdgeUno * La Paz, BO - EdgeUno IPv6 * Lima, PE - America Movil * Marseille, FR - Orange * Montevideo, UY - Claro IPv6 * Montreal, CA - IBM Cloud * New York, US - Cogent IPv6 * New York, US - Equinix Metal IPV6 * New York, US - Unitas IPv6 * New York, US - Zayo IPv6 * Paris, FR - Equinix Metal * Philadelphia, US - Crown Castle * Philadelphia, US - Crown Castle IPv6 * Phoenix, US - Cox * Phoenix, US - Lumen * Portland, US - Lumen * Porto Alegre, BR - EdgeUno * Rio de Janeiro, BR - EdgeUno * Rio de Janeiro, BR - EdgeUno IPv6 * San Francisco, US - Comcast * San Juan, PR - EdgeUno IPv6 * Santiago, CL - Cirion IPv6 * Seoul, KR - LG * Shenzhen, CN - Alicloud * Tel Aviv, IL - Cellcom * Toronto, CA - Equinix Metal IPV6 * Toronto, CA - IBM Cloud * Toronto, CA - Lumen * Toronto, CA - Lumen IPv6 * Toronto, CA - Rogers * Washington DC, US - Equinix Metal IPV6 * Washington DC, US - Unitas * Washington DC, US - Unitas Ipv6 * Washington DC, US - Zayo IPv6
- monitoring Jun 19, 2025, 07:52 AM UTC
We are continuing to monitor for any further issues.
- monitoring Jun 19, 2025, 07:57 AM UTC
We are continuing to monitor for any further issues.
- resolved Jun 19, 2025, 04:09 PM UTC
This incident has been resolved.