Banking Circle incident

Intermittent connection errors affecting BC Connect UI and API.

Major Resolved View vendor source →

Banking Circle experienced a major incident on July 20, 2026 affecting Connect UI Login, lasting 7d 1h. The incident has been resolved; the full update timeline is below.

Started
Jul 20, 2026, 01:49 PM UTC
Resolved
Jul 27, 2026, 03:04 PM UTC
Duration
7d 1h
Detected by Pingoru
Jul 20, 2026, 01:49 PM UTC

Affected components

Connect UI Login

Update timeline

  1. identified Jul 20, 2026, 01:49 PM UTC

    Some of the clients may experience difficulties accessing BC Connect, with the login page remaining in a continuous loading state, as well as timeouts on some of our API's. Our engineering team is currently investigating the issue.

  2. identified Jul 20, 2026, 01:53 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Jul 20, 2026, 03:46 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Jul 20, 2026, 06:01 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Jul 20, 2026, 08:21 PM UTC

    We are continuing to monitor for any further issues. Next update is planned for 06:00 UTC or in case of any major development.

  6. identified Jul 21, 2026, 06:36 AM UTC

    Some of the clients may experience timeouts on some of our API's. Our engineering team is currently investigating the issue and monitoring further.

  7. identified Jul 21, 2026, 07:50 AM UTC

    Some of the clients may experience difficulties accessing BC Connect, with the login page remaining in a continuous loading state, as well as timeouts on some of our API's. Our engineering team is currently investigating the issue.

  8. identified Jul 21, 2026, 08:34 AM UTC

    We are continuing to work on a fix for this issue.

  9. monitoring Jul 21, 2026, 10:50 AM UTC

    A fix has been implemented and we are monitoring the results.

  10. monitoring Jul 21, 2026, 01:59 PM UTC

    We are aware some clients are reporting API Connectivity issues on certain end points. This is continually being monitored and we are aware of this. Updates to follow.

  11. monitoring Jul 21, 2026, 06:40 PM UTC

    We are continuing to monitor for any further issues.

  12. monitoring Jul 22, 2026, 10:08 AM UTC

    We are aware that some clients may still experience intermittent difficulties accessing the BC UI, as well as occasional timeouts on some of our APIs. The situation is being closely monitored, and our engineering team is continuously working to address each issue individually as soon as it arises. We appreciate your patience and understanding while we work to restore full stability

  13. monitoring Jul 22, 2026, 12:37 PM UTC

    We are continuing to monitor for any further issues.

  14. monitoring Jul 22, 2026, 06:28 PM UTC

    We are continuing to monitor for any further issues.

  15. monitoring Jul 23, 2026, 07:34 AM UTC

    We are continuing to monitor for any further issues.

  16. monitoring Jul 23, 2026, 01:50 PM UTC

    We are continuing to monitor for any further issues.

  17. monitoring Jul 24, 2026, 05:34 AM UTC

    We are continuing to monitor for any further issues.

  18. monitoring Jul 24, 2026, 11:16 AM UTC

    We are continuing to monitor for any further issues.

  19. monitoring Jul 24, 2026, 12:34 PM UTC

    We are continuing to monitor for any further issues.

  20. monitoring Jul 24, 2026, 04:11 PM UTC

    We are continuing to monitor for any further issues.

  21. monitoring Jul 25, 2026, 06:52 AM UTC

    We are continuing to monitor for any further issues.

  22. monitoring Jul 25, 2026, 08:28 PM UTC

    We are continuing to monitor for any further issues.

  23. monitoring Jul 26, 2026, 07:27 AM UTC

    We are continuing to monitor for any further issues.

  24. monitoring Jul 26, 2026, 08:09 PM UTC

    We are continuing to monitor for any further issues.

  25. monitoring Jul 27, 2026, 08:56 AM UTC

    We are continuing to monitor for any further issues.

  26. resolved Jul 27, 2026, 03:04 PM UTC

    This incident has been resolved.