Fourth incident

Critical Incident - Single Sign On - "Sorry, but we're having trouble signing you in.", Error

Critical Resolved View vendor source →

Fourth experienced a critical incident on October 1, 2026 affecting Fourth Platform & Single Sign On, lasting 23h 42m. The incident has been resolved; the full update timeline is below.

Started
Oct 01, 2026, 04:23 PM UTC
Resolved
Oct 02, 2026, 04:05 PM UTC
Duration
23h 42m
Detected by Pingoru
Oct 01, 2026, 04:23 PM UTC

Affected components

Fourth Platform & Single Sign On

Update timeline

  1. investigating Oct 01, 2026, 04:23 PM UTC

    We are aware of a critical incident that may be affecting some of our customers. This is incident is currently being investigated to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

  2. investigating Oct 01, 2026, 04:48 PM UTC

    We are aware of a critical incident that may be affecting some of our customers. We are continuing to investigate to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

  3. investigating Oct 01, 2026, 05:18 PM UTC

    We are aware of a critical incident that may be affecting some of our customers. We are continuing to investigate to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

  4. investigating Oct 01, 2026, 05:46 PM UTC

    We are aware of a critical incident that may be affecting some of our customers. We are continuing to investigate to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service

  5. investigating Oct 01, 2026, 06:12 PM UTC

    We are aware of a critical incident that may be affecting some of our customers. We are continuing to investigate to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service

  6. investigating Oct 01, 2026, 06:48 PM UTC

    We are aware of a critical incident that may be affecting some of our customers. We are continuing to investigate to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service

  7. investigating Oct 01, 2026, 07:15 PM UTC

    We are aware of a critical incident that may be affecting some of our customers. We are continuing to investigate to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service

  8. investigating Oct 01, 2026, 07:45 PM UTC

    We are aware of a critical incident that may be affecting some of our customers. We are continuing to investigate to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service

  9. identified Oct 01, 2026, 08:15 PM UTC

    We have taken some steps to resolve and are beginning to see some signs of improvement. We are continuing to diligently work towards returning service to normal levels. We will continue to provide updates here every 30 minutes or less until full service has been restored. Again we deeply apologise for this disruption.

  10. monitoring Oct 01, 2026, 09:15 PM UTC

    We have now implemented a solution and are currently monitoring for completeness. The next update will be provided upon confirmation of resolution. We apologise for this disruption to your service.

  11. resolved Oct 02, 2026, 04:05 PM UTC

    This incident has been resolved.