Rublon incident

Phone Call Delivery, SMS Me...

Minor Resolved View vendor source →

Rublon experienced a minor incident on October 20, 2025 affecting Rublon Infrastructure (Phone Call Delivery) and Rublon Infrastructure (SMS Message Delivery), lasting 1h 20m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 09:03 AM UTC
Resolved
Oct 20, 2025, 10:23 AM UTC
Duration
1h 20m
Detected by Pingoru
Oct 20, 2025, 09:03 AM UTC

Affected components

Rublon Infrastructure (Phone Call Delivery)Rublon Infrastructure (SMS Message Delivery)

Update timeline

  1. investigating Oct 20, 2025, 09:03 AM UTC

    We have detected a degradation affecting the following service component(s): Phone Call Delivery, SMS Message Delivery. User reports indicate issues in the Amazon Web Services (AWS) – US-East-1 region that are impacting Rublon MFA’s SMS Passcode, SMS Link and Phone Call authentication methods, as well as phone number enrollment. At this time, the root cause lies within AWS’s infrastructure, and our systems are dependent on their resolution. Our team is monitoring the situation closely and awaiting updates from AWS. We will communicate further as soon as more information becomes available. Thank you for your patience and understanding during this service disruption.

  2. resolved Oct 20, 2025, 10:23 AM UTC

    We have confirmed that the recent degradation impacting the following service component(s): Phone Call Delivery, SMS Message Delivery was caused by an infrastructure issue within AWS. Our engineering team has confirmed that the dependency has now returned to normal operation and full service functionality has been restored. We apologize for any inconvenience this disruption may have caused, and thank you for your continued support as we strive to maintain the highest standards of service reliability.

  3. resolved Oct 20, 2025, 10:23 AM UTC

    We have confirmed that the recent degradation impacting the following service component(s): Phone Call Delivery, SMS Message Delivery was caused by an infrastructure issue within AWS. Our engineering team has confirmed that the dependency has now returned to normal operation and full service functionality has been restored. We apologize for any inconvenience this disruption may have caused, and thank you for your continued support as we strive to maintain the highest standards of service reliability.