Signal briefing / Global Cloud Services Trends

Commerce Bank

The bank's presence in the RIPE registry creates a dependency for network operators who may need to reach the responsible party for AS210992. If the registry record is accurate, it correctly routes incident reports; if it is stale or inaccurate, misdirected communications could cause delays. Tracking this subject helps analysts maintain an up-to-date picture of who handles network operations for this autonomous system.

Commerce Bank

Sources

Public references used for this article.

  • Registry RDAP / WHOIS recordpublic-source identity and registry context (source risk: low risk)
  • RIPE registry recordRIPEstat provides a public ASN overview page for AS210992, supporting that the ASN exists as a publicly visible routing/registry entity. (source risk: low risk)
  • swift.comThe public SWIFT BIC directory lists DEMIBGSF as COMMERCE BANK AD, Sofia, Bulgaria, supporting that a Bulgarian bank using the English name Commerce Bank publicly exists. (source risk: low risk)
  • Operator websiteThe public website at dbank.bg presents the bank's corporate web presence and aligns with the domain used in the published abuse contact details. (source risk: low risk)
CategoryGlobal Cloud Services Trends

Commerce Bank serves as the publicly listed abuse contact for AS210992, which means external parties will direct network abuse reports and technical inquiries related to that autonomous system to the bank. Because AS210992 carries no active prefix announcements in public observation, the role is limited to a registry-based contact function rather than active routing operations.

ImpactMedium

Stale or changed RDAP records for AS210992 would alter the public contact pathway, potentially causing abuse reports to go to an outdated or incorrect destination. If AS210992 begins announcing BGP prefixes, the bank's infrastructure relevance would rise, making it an active entity in internet routing rather than a passive registry contact.

ConfidenceHigh confidence (95%)

Several public sources

Commerce Bank is a Bulgarian bank appearing in RIPE registry records as the abuse contact for AS210992. No active BGP prefixes are observed, limiting its operational profile to the registry entry. Evidence includes the RDAP record, SWIFT BIC directory, and the bank's website. The exact legal name and the employment status of named contacts remain unverified. Key watchpoints are record changes and routing emergence.

Commerce Bank

Commerce Bank is a Sofia-based Bulgarian bank that appears in RIPE registry records as the organisational abuse contact for autonomous system AS210992 (autonomous system name DBANK). The institution has no observed BGP routing activity, keeping its internet infrastructure footprint minimal but making its registry record the primary signal for any network operator who needs to contact the party responsible for that autonomous system.

Why It Matters

Stale or changed RDAP records for AS210992 would alter the public contact pathway, potentially causing abuse reports to go to an outdated or incorrect destination. If AS210992 begins announcing BGP prefixes, the bank's infrastructure relevance would rise, making it an active entity in internet routing rather than a passive registry contact.

What Public Sources Show

Commerce Bank is a Sofia-based Bulgarian bank that appears in public internet registry records as the organisational abuse contact for autonomous system AS210992, which uses the name DBANK. The bank is a legitimate financial institution verified through its SWIFT BIC listing and corporate website, but its role in network infrastructure is limited to that registry entry because no active BGP prefix announcements are observed from the ASN.

Public sources include the RIPE RDAP record for AS210992, which names Commerce Bank as the abuse contact with a domain-based mailbox. The RIPEstat ASN overview confirms the entry exists, while the SWIFT BIC directory lists “Commerce Bank AD” in Sofia. The bank’s own website at dbank.bg matches the registered domain. These records together establish a consistent, though narrowly defined, public identity.

As the registered abuse contact, Commerce Bank is the designated recipient for network abuse reports and technical queries that involve AS210992. However, because no BGP prefixes are announced by this autonomous system, the bank does not currently participate in internet routing. The control surface is therefore limited to the ability to update the registry record and manage the associated domain, rather than operating network hardware or peering.

If the registry data is up to date, external operators will properly route inquiries to the bank, facilitating incident response. Stale or inaccurate data could misdirect those communications, potentially delaying remediation or attributing issues to the wrong party. A change in the registry record or the start of routing activity would directly alter how infrastructure observers assess the bank’s involvement.

Key watchpoints include any modification to the RDAP or WHOIS records for AS210992, which would change the public contact baseline. The appearance of BGP prefix announcements from AS210992 would indicate live routing operations and raise the bank’s infrastructure significance. Resolving the legal name discrepancy between “Commerce Bank” and “Commerce Bank AD” through an official Bulgarian corporate registry entry would strengthen the identity picture.

The lack of a Bulgarian corporate registry or banking supervisor record means the precise legal name and registration details are not independently confirmed. The employment status of the two named contacts—Bisser Hadjimarkov and Stoyan Stoyanov—is unclear; they may be bank staff or external representatives. The internal network infrastructure of the bank remains opaque, and the operational relevance of AS210992 could shift if the bank activates it.

Commerce Bank’s profile is a registry-based snapshot. It provides a starting point for analysts monitoring internet number resources assigned to Bulgarian financial institutions, but it does not describe an active network operator. The most important signals to watch are record changes and routing activity, either of which would necessitate a reassessment of the subject’s infrastructure relevance.

Operating Surface

Commerce Bank serves as the publicly listed abuse contact for AS210992, which means external parties will direct network abuse reports and technical inquiries related to that autonomous system to the bank. Because AS210992 carries no active prefix announcements in public observation, the role is limited to a registry-based contact function rather than active routing operations.

The bank's presence in the RIPE registry creates a dependency for network operators who may need to reach the responsible party for AS210992. If the registry record is accurate, it correctly routes incident reports; if it is stale or inaccurate, misdirected communications could cause delays. Tracking this subject helps analysts maintain an up-to-date picture of who handles network operations for this autonomous system.

Watchpoints

Commerce Bank's registry entry represents a dormant number resource that, if activated, would link a Bulgarian financial institution to active internet routing. Tracking it supports dependency mapping for network operators who may need to contact the responsible party.

Modifications to AS210992's RDAP/WHOIS records, initiation of BGP announcements, and resolution of the legal name discrepancy through a Bulgarian corporate registry.

No Bulgarian corporate registry or bank supervisor record confirms the legal name and registration. The employment relationship of the named contacts to the bank is unknown. The absence of BGP announcements makes the network footprint unconfirmed.

Sources

  • Registry RDAP / WHOIS record - public-source identity and registry context for Commerce Bank.
  • RIPE registry record - RIPEstat provides a public reference page for AS210992, supporting that the ASN exists in RIPE-related public internet number resource data.
  • swift.com - The public SWIFT BIC directory lists DEMIBGSF as COMMERCE BANK AD, Sofia, Bulgaria, supporting that a Bulgarian bank using the English name Commerce Bank publicly exists.
  • Operator website - The public website at dbank.bg presents the bank's corporate web presence and aligns with the domain used in the published abuse contact details.

Signal Brief

  • Signal: Commerce Bank
  • Region:
  • Market Class: Global Cloud Services Trends

Operating Footprint

  • public operating records
  • official service pages
  • documented relationships updates

Market Context

  • Stale or changed RDAP records for AS210992 would alter the public contact pathway, potentially causing abuse reports to go to an outdated or incorrect destination. If AS210992 begins announcing BGP prefixes, the bank's infrastructure relevance would rise, making it an active entity in internet routing rather than a passive registry contact.
  • Operational relevance: Medium
  • Time Horizon: Next quarter

What To Watch

  • official company sources
  • public registries
  • operator-published records

Member Briefing

Deeper Trend Context

Sign in with the right membership level to unlock the full briefing and source notes.

Only for Strategic Circle

Strategic Circle

Open to all readers. Unlock trend briefings after joining and signing in.

Join Strategic Circle

Only for Leadership Alliance

Leadership Alliance

For operators, investors, and policy teams that need relationship evidence, failure paths, and source notes. Sign in to unlock.

Join Leadership Alliance
BackMore Coverage: Global Cloud Services Trends