iQmetrix incident

RQ Disruption - Multiple RQ Services

Notice Resolved View vendor source →

iQmetrix experienced a notice incident on March 3, 2025 affecting General RQ and Logins, lasting 22h 55m. The incident has been resolved; the full update timeline is below.

Started
Mar 03, 2025, 04:52 PM UTC
Resolved
Mar 04, 2025, 03:47 PM UTC
Duration
22h 55m
Detected by Pingoru
Mar 03, 2025, 04:52 PM UTC

Affected components

General RQLogins

Update timeline

  1. identified Mar 03, 2025, 04:52 PM UTC

    Currently we are seeing a service disruption related to multiple services within RQ. Our Incident Management Team has identified this may be related to a larger Microsoft outage that is currently on going. More updates to follow.

  2. identified Mar 03, 2025, 05:05 PM UTC

    Currently our Incident Management team is moving traffic to restore service. The issue has been identified as a Microsoft issue however we are attempting to failover to see if it will mitigate the impact. More updates to follow.

  3. identified Mar 03, 2025, 05:30 PM UTC

    After the failover we are still seeing timeouts but invoicing is showing improvement. Our team is continuing to work on mitigating the incident. More updates to follow.

  4. identified Mar 03, 2025, 05:54 PM UTC

    Our team has implemented additional mitigation measures and is currently monitoring to see impact. More updates to follow.

  5. identified Mar 03, 2025, 06:03 PM UTC

    Our team is continuing to monitor and investigate mitigation steps related to the Microsoft incident. The majority of impact appears to be for Canadian clients however may not be limited to them. We have currently not seen invoice impact for US Clients and will continue to monitor. Additional updates to follow.

  6. identified Mar 03, 2025, 06:26 PM UTC

    Our Incident Management Team has confirmed everything is looking healthy. Largest impact was on Canadian clients however we did see timeouts in RQ for a subset of American clients, if you were experiencing issues during that time please reach out to our Support team to investigate further. We will continue to monitor but at this time we are resolving this incident.

  7. identified Mar 04, 2025, 03:27 PM UTC

    Resolved

  8. resolved Mar 04, 2025, 03:47 PM UTC

    This incident has been resolved.