Q4 2026 AI infrastructure credit monitor: interim
An as-of-23-October reading of the research register, its composition and the questions still open.
This is an interim research snapshot prepared on 23 October 2026. The fourth quarter is not complete. Counts describe the current InfraCompute register and its review status, not the total market, quarterly issuance or independently verified deal volume.
The register at a glance
Counts include historical facilities, amendments, packages and adjacent businesses. They are not additive funding flows. Segment labels describe primary activity; they do not certify collateral or exclusive use of proceeds.
| Category | Observations |
|---|---|
| Data centre | 359 |
| Cloud / corporate | 73 |
| GPU / compute | 44 |
| mixed unclassified | 35 |
| Powered land | 3 |
| Register total | 514 |
| Category | Observations |
|---|---|
| Inherited; not independently rechecked | 366 |
| Selected fields checked | 145 |
| selected fields checked conflict | 2 |
| Indexed primary passage checked | 1 |
| Register total | 514 |
What the register measures
A financing observation can be an original facility, an amendment, a refinancing, an issue or another dated capital event. The same financing family may therefore appear more than once. Operator profiles include historical issuers and adjacent businesses. These are useful research links, but they are not counts of unique active borrowers.
What comparison is useful now
Asset-segment and review-status counts show where research is concentrated and where evidence remains incomplete. Selected source checks improve particular fields; they do not certify every term or establish a full legal audit. Comparing the database's coverage composition is more defensible than calculating a market-wide average financing cost from incomplete fields.
The next evidence priorities
Reconcile amendments to their predecessors; identify the exact borrowing entity and legal payer; attach named projects only where supported; and retain pricing bases separately. For development finance, resolve power and acceptance milestones. For equipment finance, test principal remaining at customer expiry against net recovery.
Actions for the next review
- Prioritise inherited records with accessible primary documents.
- Reconcile package amounts, tranches and facility histories.
- Collect complete cash flows before publishing any all-in-cost benchmark.
Explore the disclosed examples
Open a register record for its dated amount, classification and source limitations. A link is not certification of all terms.
For in-house counsel
Take it to the documents
The filed wording behind this piece, for the lender’s or the borrower’s side. Previews are open; the full text is free with InfraCompute Weekly.
- Contract libraryGPU contracts, leases, power, equity and JVs, quoted from filed contracts.
- Financing clause libraryCash traps, coverage ratios, cures and step-in, from the filed deals.
- Issues list builderBuild an issues list from the lender’s or the borrower’s side.
- The legal desk for in-house counselEverything for counsel in one place.
Sources for the examples
Selected public sources support the examples. The analytical framework is InfraCompute editorial work; source links do not imply a complete agreement or legal review.
- CoreWeave closes $2.6bn DDTL5.5 ↗Disclosure date: 2026-08-10
- Vantage Data Centers Secures $5B in Incremental Green Loan Financings to Support Demand for North America Platform ↗Disclosure date: 2025-06-03
- Yondr IFC Johor financing ↗Disclosure date: 2024-05-30
