Summary

  • AS211392's self-reported peering entry claims 50 IPv4 prefixes, three IPv6 prefixes, 50–100 Gbps of traffic and an Asia-Pacific open-peering footprint; three separate sources put the IPv4 count at 16, 19 and 22 and reported no IPv6 prefix at all in the same 25 September 2026 window.
  • The registry layer is administrative rather than ownership: a RIPE aut-num object names the holder DREAM CLOUD INNOVATION LIMITED, country GB, with the free-text as-name "softbank", while a second IRR object in RADB carries the name "DREAMCLOUDINNOVATIONLIMITED".
  • Route-origin validation is uneven by prefix: one panel counted 17 of 19 prefixes as RPKI-originated-valid; another reports prefix 154.83.23.0/24 as NOT-FOUND.
  • Neither self-report nor observation is a corporate record, a product document or a customer reference. The gap between them is measurable — and it is what a careful reader should price before relying on either.

Four kinds of evidence, one autonomous system

On 25 September 2026, this briefing examined six public records describing AS211392, the autonomous system operated under the name "softbank DREAM CLOUD INNOVATION LIMITED". They fall into four kinds: registry objects maintained at the request of the network's own administrators; a peering-fabric entry the operator writes about itself; measurement panels that observe the global routing system from outside; and derived statistics that blend the two. Each kind answers a different question. Read together, they disagree about size, reach and even name.

The registry layer: a name is not an owner

The RIPE Database aut-num object for AS211392, as mirrored by IPGeolocation, records the holder organization as DREAM CLOUD INNOVATION LIMITED (ORG-DCIL3-RIPE), country GB, status ASSIGNED, created and last modified on 3 May 2021. Its free-text as-name field carries the single word "softbank". The object declares routing policy toward two networks only, AS59117 and AS4809, and is maintained under RIPE-NCC-END-MNT and a UK LIR maintainer; the same mirror reports 16 IPv4 routes and no IPv6 routes for the ASN.

None of those fields is proof of ownership. An aut-num object is an administrative registration; the as-name is a short label chosen by the maintainer, not a trademark, a contract or a corporate-structure statement. The same number also carries a second description: Hurricane Electric's BGP toolkit reproduces a RADB aut-num object whose as-name reads "DREAMCLOUDINNOVATIONLIMITED", maintained under MAINT-AS59117-1. One ASN, two registry descriptions, two different names — and neither one establishes who controls the network.

The self-report layer: capability as a claim

PeeringDB network record 28020 is the operator's own description of the network: type NSP, 50 IPv4 prefixes, three IPv6 prefixes, traffic level 50–100 Gbps, balanced traffic ratio, Asia-Pacific scope, open peering policy, IRR as-set AS211392:AS-CUSTOMERS, and an operational presence at AT TOKYO (CC1/CC2) in Japan. The record was last updated on 6 June 2025; its RIR status field was last updated on 26 June 2024.

PeeringDB entries are self-reported by design. They are what an operator wants prospective peers to know, and they may describe provisioned capacity, intended capacity or a stale snapshot — the record itself does not say which. That is not a defect of this operator; it is a property of the genre. The figure 50 is a claim, not a measurement.

The observation layer: what the counters see

Panels work from outside, and they do not fully agree with each other either. Hurricane Electric counted 19 IPv4 prefixes originated and announced by AS211392 — 17 of them RPKI-originated-valid — zero IPv6 prefixes, seven observed BGP peers and 4,864 originated IPv4 addresses, with the page footer showing data updated 7 May 2026 (toolkit page). ping.pe lists 22 announced prefixes attributed to "softbank - DREAM CLOUD INNOVATION LIMITED", with per-prefix RPKI states that include prefixes marked VALID and prefix 154.83.23.0/24 marked NOT-FOUND. IPinfo reports 3,566 hosted domains, 2,048 IPv4 addresses, zero IPv6 addresses, network type Hosting, six peers and three upstreams — AS23764 CTGNet, AS58453 China Mobile International and AS139076 EnjoyVC Japan — with about 54% of traffic geolocating to Japan and 44% to Hong Kong, and none in the United Kingdom, the country of the holder's registration.

Each of these counts describes a retrieval window, not a permanent state; panels differ by vantage point, by how they treat origin prefixes, and by when they sample. But they agree on two things the self-report does not: none of them reported an IPv6 prefix originated by AS211392, and none came close to 50 IPv4 prefixes.

The organization layer: three maps that do not line up

PeeringDB organization 30519 is named DREAM CLOUD LIMITED and carries a Las Vegas, Nevada address (220 Emerald Vista Way). It lists two networks: AS211392, labeled "DREAM CLOUD", and "DREAM CLOUD INNOVATION AS135074". Meanwhile the holder of AS211392 is registered in GB, the observed traffic concentrates in Japan and Hong Kong, and the peering organization is addressed in the United States. Administrative geography, operational geography and observed traffic are three different maps, and nothing in this record set reconciles them.

What the divergence does — and does not — mean

The likeliest explanation for a self-report larger than any observed count is mundane: records are written once and updated slowly, panels see only what is announced and visible from where they stand, and "prefixes" can mean registered objects, announced prefixes or a whole customer cone, depending on the tool. Two of the six records point at a customer set: the peering entry's IRR as-set is named AS211392:AS-CUSTOMERS, and the organization record lists a second network, AS135074. Neither fact proves what is counted where.

What the records cannot settle matters more than what they can. No source in this set documents a corporate relationship between the free-text string "softbank" and any company of that name; the string appears only as an unvalidated field value that third-party pages then repeat. No customer-facing cloud product, contract or corporate filing for the holder appears in these records. Who controls AS135074, MAINT-AS59117-1 or the UK LIR maintainer is not established. And the administrative timestamps — the PeeringDB update of 6 June 2025, the RIPE object of 3 May 2021 — are record dates, not operational events.

What to verify before relying on any of it

A reader who needs to treat AS211392 as a peer, a supplier, a competitor or an investment case can do what the records do not: separate the layers and timestamp each one. Check announced prefixes from more than one vantage point, over more than one week. Check per-prefix RPKI state rather than an aggregate. Check the registry object's history and maintainers. Check corporate registers and customer references before treating a network as a counterparty. And treat free-text names as labels rather than identities: "a network whose registry label says softbank" is not the same statement as a verified corporate relationship, and only the first is evidenced here. The BTW directory entry for softbank DREAM CLOUD INNOVATION LIMITED collects the same public records for readers who want to follow them.

The practical consequence is bounded but real. A reader who takes the self-report at face value would overstate the observed IPv4 footprint by roughly two to three times and would assume dual-stack capability that no source observed. These records cannot say whether that is ambition, staleness or something else. They can say the gap exists — and that it is measurable.