BTW.Media
Daily editionStrategic Internet Intelligence
Sign InRegister

Organisation profile

Organisation

Datacenter on demand LLC

Datacenter on demand LLC appears in public ASN/IP network-resource records for AS35930, giving readers a view into the address-resource layer behind internet reachability.

The available evidence covers Network identity: AS35930, Services: 3, Related networks: 9, and ASNs: 1.

Source description Datacenter on demand LLC is recorded as a company. Current public evidence covers 1 ASN, one supporting public reference; services, assets, and relationship context should be read with that evidence boundary.

GlobalLatest 2026-06-27
  • 1ASNs
  • 9Relationships
  • 3Services
Location
Global
Network identity
AS35930
Services
3
Related networks
9

Confidence

1
Information type
Datacenter on demand LLC is the organisation operating autonomous system AS35930. Public evidence also covers one supporting public reference. BTW tracks it to pin down the responsible operator, the services these number resources support, and the upstream, peer, and customer relationships behind its routing.

Related details

Last updated: 2026-05-18

Network identity

1
AS35930

Services

3
Service:Managed networkNot yet assessed· 1 record
Service:Data centerNot yet assessed· 1 record
Service:ColocationNot yet assessed· 1 record

Related networks

9
Relationship topology: Datacenter on demand LLCMisaka Network, Inc.AS57695Misaka Network, Inc.AS917MISAKA - Misaka Network, Inc.MISAKA - Misaka Network, Inc.COGENT COMMUNICATIONS, LLCAS1239Datacenter on demand LLC
This entityupstream / providerdownstream / customerpeercorporate / legalother

The entity sits in the centre; its customers fan out to the left and its upstream providers to the right (arrows show transit direction). Scroll or use the buttons to zoom · drag the background to pan · click a node to open it in the directory.

Data as of 2026-06

The entity sits on the left and its connections fan out by role on the right; the graph shows each group’s most confident connections, and the full list below carries every relationship.

Full list

MISAKA - Misaka Network, Inc.
downstreamHigh confidence· 3 records· 3 unrated· Latest 2026-06
MISAKA - Misaka Network, Inc.Multiple relationships recorded
downstreamHigh confidence· 3 records· 3 unrated· Latest 2026-06peerHigh confidence· Latest 2026-06
COGENT COMMUNICATIONS, LLCAS1239
downstreamHigh confidence· 2 records· 2 high· Latest 2026-06
Misaka Network, Inc.AS57695
peerHigh confidence· 3 records· 3 unrated· Latest 2026-06
Misaka Network, Inc.AS917
downstreamHigh confidence· 16 records· 16 unrated· Latest 2026-06
Unidentified peer · 1· high 1· Latest 2026-05

Related research

2
  • Datacenter on demand's AS35930 footprint shows a handoff, not a proved cloud estate

    Datacenter on demand LLC can be located in public records through AS35930, two address allocations, recent routing observations and listings at two third-party facilities. That is enough to expose a network handoff surface. It is not enough to prove who operates equipment at those sites, which services run there, how much capacity exists, or whether a multi-location managed cloud is ready for any particular customer.

    Primary articlePublished 2026-07-21
  • Datacenter on demand LLC has to prove whether marketed data-centre capacity can survive power and carrier constraints

    Datacenter on demand LLC presents itself as a cloud and infrastructure provider with named locations in Sheridan, Secaucus and Frankfurt, but the public proof of operating depth is much thinner than the marketing surface. Its own pages point to managed cloud, infrastructure support, modernization and hybrid-cloud work; ARIN records tie AS35930, 23.149.8.0/24 and 2602:FAA2::/36 to the company; PeeringDB lists facility presence at Equinix's New York/Secaucus campus and Telehouse Frankfurt. That evidence is real. It still leaves the harder question unanswered: whether any marketed capacity is backed by resilient power, cooling, carrier access, staffing and customer failover evidence.

    Primary articlePublished 2026-07-12