Description

The "Still connecting" / "Unable to connect" banner fires today whenever any one enabled EVM network's default RPC is unavailable, which means a single Infura blip — or a wide Infura outage that takes down many *.infura.io networks at once — pops a banner that doesn't reflect anything the user can act on.

This PR keeps the banner UI, timer thresholds, and analytics untouched and only changes the show/hide rule. The banner now shows when failed RPCs span 2+ distinct registrable domains (eTLD+1 via the Public Suffix List), or every enabled EVM network has failed (so single-network setups still get a signal), or any failed RPC is a non-Infura (custom) endpoint — those have no automatic failover. When a custom failure exists, it's surfaced first so the "Switch to MetaMask default RPC" CTA targets the one the user can act on.

Mobile counterpart to extension PR #43073. Same rule, kept inline in useNetworkConnectionBanner rather than split into composed selectors.

Implementation:

• New app/util/url-utils.ts exposing getDomain (psl-backed eTLD+1) and isLocalhostOrIPAddress (ip-regex-backed). Localhost, IP literals, and single-label hosts short-circuit so callers grouping by domain can still distinguish them.
• useNetworkConnectionBanner.checkNetworkStatus collects every failing enabled EVM network instead of breaking on the first, counts distinct domains, and applies the new rule.
• New direct deps: psl, ip-regex (the latter added to transformIgnorePatterns since it ships ESM-only).

Changelog

CHANGELOG entry: Reduced false-positive RPC connection banners — single-provider outages no longer pop the banner, even when many popular networks fail at once.

Related issues

Fixes: WPC-1014

Manual testing steps

Feature: RPC connection banner suppression

  Scenario: single Infura blip during a wide outage
    Given the user has many popular networks enabled
    When all *.infura.io endpoints become unreachable simultaneously
    Then no banner should appear (one registrable domain, suppressed)

  Scenario: two different providers fail simultaneously
    Given the user has Infura- and non-Infura-backed networks enabled
    When both providers' RPCs fail at the same time
    Then the degraded banner should appear at 5s and escalate to unavailable at 30s

  Scenario: user-added custom RPC fails alone
    Given the user has a custom RPC configured for any network
    When only that custom endpoint is unreachable
    Then the banner should appear (custom override) with the "Switch to MetaMask default RPC" CTA targeting that network

  Scenario: only enabled network fails
    Given the user has a single network enabled
    When that network's RPC becomes unreachable
    Then the banner should appear (all-enabled-down escape hatch)

  Scenario: device is offline
    Given the device has no internet connectivity
    When any RPC times out
    Then no banner should appear (existing device-offline short-circuit)

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Performance checks (if applicable)

• I've tested on Android
• I've tested with a power user scenario
• I've instrumented key operations with Sentry traces for production performance metrics

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.