Skip to content

Which companies just had a verified incident, who lends to them and who owns them. Every claim carries its evidence level and its source. How we decide what is confirmed

US critical infrastructure monitor

Column

Banking · CA (headquarters)

Monitoring
Not checked: the site's robots.txt does not allow it.: last success Nov 6 12:35 UTC
Public findings
0
Provider status posts on record
6

Cyber and operational findings

Analyst-reviewed records. The grade states how well the cause is established; event, first public observation and acknowledgement are separate dates.

No public findings for this organisation.

Provider status posts

Collected from the organisation's own public status page. These are its words; DFX adds only the wording classification.

  • High database latencyApr 7 19:28 UTC · resolved
    Restoration reported
    1. Apr 7 19:28 UTC identified: We are experiencing high database latency leading to elevated API timeouts. We have identified the issue and working on a fix.
    2. Apr 7 19:32 UTC identified: We are continuing to work on a fix for this issue.
    3. Apr 7 19:46 UTC resolved: This incident has been resolved.
    View on the provider's status page
  • Increased Endpoint LatencyMar 27 19:50 UTC · resolved · minor impact
    Restoration reported
    1. Mar 27 19:50 UTC identified: We are triaging some database latency which is leading to occasional API endpoint timeouts.
    2. Mar 27 23:03 UTC resolved: This incident has been resolved.
    View on the provider's status page
  • High number of API timeoutsMar 3 16:31 UTC · resolved · major impact
    Restoration reported
    1. Mar 3 16:31 UTC identified: We are experiencing an elevated number of timeouts across several of our production endpoints.
    2. Mar 3 17:55 UTC monitoring: A fix has been implemented and we are monitoring the results.
    3. Mar 3 18:54 UTC resolved: This incident has been resolved.
    View on the provider's status page
  • International WiresNov 24 05:15 UTC · resolved
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Nov 24 07:15 UTC investigating: We are currently investigating this issue.
    2. Nov 24 07:25 UTC investigating: The interruption has been resolved due to an issue with the SWIFT network
    3. Nov 24 07:26 UTC investigating: This incident has been resolved.
    4. Nov 24 07:32 UTC resolved: This incident has been resolved.
    View on the provider's status page
  • Scheduled maintenanceJun 24 17:41 UTC · resolved
    No classified wording
    1. Jun 24 17:41 UTC resolved: Maintenance scheduled to begin at 9:35 AM PST and conclude at 9:50 AM PST.
    View on the provider's status page
  • This is an example incidentFeb 13 20:51 UTC · resolved
    No classified wording
    1. Feb 14 20:09 UTC investigating: When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.
    2. Feb 14 20:09 UTC identified: As you continue to work through the incident, update your customers frequently.
    3. Feb 14 20:09 UTC monitoring: Let your users know once a fix is in place, and keep communication clear and precise.
    4. Feb 14 20:09 UTC resolved: Empathize with those affected and let them know everything is operating as normal.
    View on the provider's status page