v4Guard incident

Instability in Miami

Minor Resolved View vendor source →

v4Guard experienced a minor incident on March 1, 2025 affecting Miami,‎ ‎ 🇺🇸 United States (MIA), lasting 51m. The incident has been resolved; the full update timeline is below.

Started
Mar 01, 2025, 01:21 AM UTC
Resolved
Mar 01, 2025, 02:12 AM UTC
Duration
51m
Detected by Pingoru
Mar 01, 2025, 01:21 AM UTC

Affected components

Miami,‎ ‎ 🇺🇸 United States (MIA)

Update timeline

  1. investigating Mar 01, 2025, 01:21 AM UTC

    We are currently investigating an issue affecting performance in Miami region.

  2. monitoring Mar 01, 2025, 01:49 AM UTC

    We have initiated a new batch of instances and gracefully shut down the conflicting ones. We are actively monitoring the situation to ensure the PoP is stabilized and returns to its normal state. We apologize for any inconvenience caused.

  3. resolved Mar 01, 2025, 02:12 AM UTC

    The incident has been resolved.