Iristel incident

PSTN Outage - Val d'Or, Quebec

Major Resolved View vendor source →

Iristel experienced a major incident on July 8, 2025 affecting QUEBEC, lasting 2d 2h. The incident has been resolved; the full update timeline is below.

Started
Jul 08, 2025, 03:46 PM UTC
Resolved
Jul 10, 2025, 06:41 PM UTC
Duration
2d 2h
Detected by Pingoru
Jul 08, 2025, 03:46 PM UTC

Affected components

QUEBEC

Update timeline

  1. investigating Jul 08, 2025, 03:46 PM UTC

    Dear Iristel customers, Please be advised that we are currently experiencing an outage in Val d'Or, Quebec. We suspect the cause is a device failure, and unfortunately, PSTN inbound and outbound calls are impacted. All other sites remain operational except for this region. Our engineering teams are sourcing a replacement. ETR is unknown. Issue start time - 7/7/25 8:15:43 PM EDT We will keep you posted as we receive additional information, we appreciate your patience. Sincerely, Iristel NOC

  2. identified Jul 09, 2025, 05:34 PM UTC

    Dear Iristel customers, We would like to provide an update regarding the ongoing service outage in Val-d'Or, Quebec. Our teams have identified the root cause as a failed DS3 multiplexor. Unfortunately, the replacement unit is delayed due to a shipping issue. We sincerely apologize for the inconvenience and appreciate your continued patience. Further updates will be shared as soon as more information becomes available. Sincerely, Iristel NOC

  3. identified Jul 09, 2025, 06:33 PM UTC

    Dear Iristel customers, We would like to provide a further update on the service outage affecting Val-d'Or, Quebec. The replacement DS3 multiplexor is en route, and the ETA is 1830h EDT today. Once received, our engineering teams will proceed with the replacement and testing to restore services as quickly as possible. We appreciate your continued patience and will provide confirmation once service has been fully restored. Sincerely, Iristel NOC

  4. monitoring Jul 09, 2025, 11:07 PM UTC

    Dear Iristel Customers, Greetings, we have been informed that the trouble was fixed by our engineering team. Resolution time: 18:35 EST If you continue to face challenges, please reach out to our support teams. We thank you for your patience and will continue to closely monitor the issue.

  5. resolved Jul 10, 2025, 06:41 PM UTC

    This incident has been resolved.