Who Owns the 801 Tenth Street Modesto CA Data Center? The Operator vs. the Building Owner

The data center at 801 Tenth Street in Modesto is associated with Ayera Technologies, Inc., the company behind the local hosting and colocation facility. That identifies the data-center operator—not necessarily the owner of the City Tower building or the land.

At 6:48 a.m. in Modesto, a clinic operations director is reviewing a planned network change before the first appointments. The carrier’s work order names 801 Tenth Street as a connection point. If the handoff fails, staff may lose access to scheduling and the electronic health record. The director needs more than a company name: who can authorize access to the facility, who can investigate the hosting environment, and who owns the recovery decision?

That is where the word “owner” can cause confusion. In a real incident or vendor review, the data-center operator, building owner, carrier, and customer each control different parts of the answer.

So, who is the 801 Tenth Street data center owner?

If “owner” means the company operating the data-center service at that address, the best-supported answer is Ayera Technologies, Inc. Ayera identifies its Modesto datacenter at 801 Tenth Street, and the City of Modesto describes Ayera as a commercial facility there that provides managed cloud hosting, web services, and localized ISP solutions.¹

If you mean the legal owner of the real estate—the deedholder of City Tower—that is a different question. The public facility descriptions identify Ayera and its services, but do not establish who holds title to the building or parcel. Don’t treat the operator’s address as proof that the operator owns the property. For a lease, purchase, easement, or legal notice, verify the parcel and recorded ownership through the appropriate county property records.

What “owner” might mean	What the evidence supports	What to verify for a decision
Data-center operator	Ayera Technologies, Inc. is associated with the 801 Tenth Street hosting facility.	Which services, equipment, and support responsibilities are covered by your contract?
Building or land owner	Not established by the facility descriptions.	The deedholder, parcel, lease rights, and who controls building access.
Network carrier	The address is a local connectivity point; that does not make a carrier the facility operator.	Which carrier provides each circuit, and where are its demarcation and escalation points?
Your organization	You remain responsible for deciding which systems must recover, in what order, and who can approve a workaround.	Named decision-makers, recovery targets, and a tested path if a provider or circuit is unavailable.

The practical takeaway: call Ayera for a question about its hosting or colocation service; call the building’s authorized property contact for a question about tenancy or premises access; call your carrier for a circuit or handoff problem. A service agreement should make the boundaries explicit rather than leave your team to discover them during an outage.

What do we know about the facility at 801 Tenth Street?

The City’s description is useful because it distinguishes this local facility from a purpose-built, large-scale data-center development. It calls Ayera a 2,200-square-foot commercial facility at 801 10th Street and says it provides managed cloud hosting, web services, and localized ISP solutions. That area refers to the commercial facility described by the City; it should not be assumed to be the building’s total area or the amount of data-hall space available to a customer.¹

Ayera’s own facility information describes a Modesto datacenter in the City Tower building and lists infrastructure such as redundant cooling, distributed UPS power, a standby diesel generator, and fire suppression. Those are useful starting points for diligence, not a substitute for confirming what is included in a particular service, how it is maintained, or how your workloads are protected. A facility feature does not tell you your application’s recovery time, your contract’s service remedy, or whether a second site is available to you.

That distinction matters for a Modesto clinic considering colocated equipment, for a county IT team planning continuity, and for a mid-market business evaluating hosted applications. The right question is not simply “Is there a generator?” It is “What has to stay available, for how long, and what evidence shows that our recovery plan can work if the facility, carrier, or application is disrupted?”

Why does the operator-versus-property-owner distinction matter?

Because an outage crosses organizational boundaries. A building manager may control the doors and common areas. The data-center operator may control racks, power distribution, cooling, and facility access procedures. A carrier may control the circuit up to its demarcation point. Your team may control the firewall, identity platform, backup policy, application dependencies, and the decision to switch users to a workaround.

Those roles can overlap, but you should not assume they do. For example, a clinic’s operations team can see that staff cannot open the EHR, while its IT provider sees a reachable server and the carrier sees a working circuit. Without a shared escalation map, each party can report that its own layer is “up” even while the appointment workflow is down.

A sound review of the 801 Tenth Street option should therefore map the workflow—not just the hardware. List what users need to do, the systems and connections involved, who supports each layer, and who has authority to declare an incident. NIST’s contingency-planning guidance frames recovery around evaluating information systems and operations to determine planning requirements and priorities; that is a better starting point than choosing a facility based only on a marketing label.²

What should a Modesto buyer ask before relying on a data center?

We would put the questions below into the vendor discussion and write the answers into the operating runbook. CISA advises customers to clarify provider security expectations, provider access, logging visibility, incident notification, and the division of responsibilities in their arrangements with managed service providers.³

• Who is the actual service counterparty? Confirm the legal company in the agreement, the entity operating the facility, any subcontractors, and the party that can approve a physical-access request.
• Where does the provider’s responsibility end? Document the handoff for building access, rack equipment, facility power, carrier circuits, firewalls, servers, backups, and application support.
• What happens during a 2 a.m. incident? Record the phone number, escalation sequence, response expectations, and who can authorize emergency access or a failover.
• Can you see what is happening? Agree on which facility, network, and administrative events are logged, how your team receives relevant alerts, and how you can review provider activity.
• What does recovery mean for your workflow? Set a recovery time objective and recovery point objective for each important service, then identify dependencies that must come back first—such as identity, DNS, internet access, and the application itself.
• How does the relationship end? Specify how data and equipment are returned, what happens to access credentials, and how the provider will support an orderly migration or contract termination.

For power resilience, ask for evidence rather than accepting a feature list. How are generator and UPS systems maintained? What is tested, how often, and who receives the test record? What are the assumptions for fuel supply and extended operation? CISA’s resilient-power guidance recommends scheduled maintenance and load testing for backup generation systems, giving buyers concrete subjects to include in a diligence conversation.⁴

How should recovery planning fit the service you buy?

Start with the business consequence. A local government team may need dispatch and records workflows to remain usable during a network interruption. A clinic may need a defined downtime process for check-in, clinical documentation, and later reconciliation. A finance team may need to know whether approvals, payment files, and audit records remain available. Those are not interchangeable recovery requirements, and a provider’s general availability statement does not decide them for you.

For healthcare organizations, HHS says a covered entity or business associate using a cloud service to create, receive, maintain, or transmit electronic protected health information must have a HIPAA-compliant business associate agreement with the provider and otherwise comply with the HIPAA Rules. HHS also highlights availability, backup and recovery, and the handling of data at the end of service as contract-relevant considerations.⁵ That makes provider identity and contract boundaries practical questions—not merely procurement details.

For a county or public-safety system involving criminal justice information, the FBI’s CJIS cloud guidance tells agencies to understand contractual provisions and procedures for availability, backup and recovery, and disaster recovery, and to check that they meet continuity and contingency needs⁶.⁷ The important operational point is to name which party performs each task and how the agency verifies it. A hosting relationship does not, by itself, answer who restores a dispatch workflow or who communicates status to the people relying on it.

In either case, keep the test focused on the service users need. A server booting is not the same as a clinic completing check-in or a dispatch team accessing the information it needs. Rehearse the sequence: who reports the outage, who confirms the affected layer, what workaround users follow, which data is reconciled afterward, and who approves return to normal operations. NIST’s recovery guidance also treats dependencies, recovery communications, and alternate facilities as planning concerns, not just equipment questions.⁸

Where does Datapath fit?

A local data center can be one component of an organization’s technology plan. It is not the whole plan, and choosing an operator is not the same as assigning accountability for the systems your staff depend on. We help organizations in Modesto and across the Central Valley connect vendor responsibilities to real operating needs: who responds, what must recover first, how teams communicate, and what evidence shows the plan is usable.

For a clinic, that can mean aligning infrastructure decisions with a practical downtime and recovery process through our healthcare IT services and disaster recovery services. For county IT and public safety, we can help map responsibilities around critical services and, where relevant, work with your team on CJIS-focused IT support. The FBI’s CJIS resource is the authority for requirements; a service relationship should support your agency’s own accountability and verification.⁵

Our approach is not to sell a rack, a ticket queue, or an abstract promise of “support.” We bring a named team, clear ownership of assigned tasks, and a recovery discussion tied to the workflows your people actually use. If you are evaluating 801 Tenth Street or another hosting arrangement, bring us the proposed service scope and one critical workflow. We can help you identify the unanswered handoffs before an outage forces the conversation. Talk with Datapath about your Modesto environment.

---

Footnotes

1. Frequently Asked Questions Regarding Data Centers in Modesto • Modesto, CA ↩ ↩²

2. Contingency Planning Guide for Federal Information Systems ↩

3. Protecting Against Cyber Threats to Managed Service Providers and their Customers | CISA ↩

4. Fact Sheet for Resilient Power Best Practices CISA ↩

5. May a HIPAA covered entity or business associate use a cloud service to store or process ePHI? | HHS.gov ↩ ↩²

6. Criminal Justice Information Services (CJIS) Security Policy ↩

7. Appendicies — LE ↩

8. Ayera Datacenter Services ↩