Federal / Southwest border
SBInet virtual border system
The federal government cancelled its planned virtual border system in 2011 after it failed cost and viability standards. More than $1 billion had been committed to the program.
Cancelled system; limited deployment
Ask Impact Analyst
Ask about the numbers or evidence. Keep the conversation going with follow-up questions.
By sending, you agree to share your question and this case’s notes with Google Gemini and save the conversation privately for review. Privacy
What was the money for?
Use technology to monitor the border.
The headline is funding committed by January 2011, not a verified total of cash paid. A separate 2011 report described nearly $1 billion spent and 53 miles of deployment.
Exact amount, time period and source wording
More than $1 billion obligated, not a verified disbursement or loss total
Period: 2011-01
Putting the amount in context
of border deployment reported before cancellation
A November 2011 federal report described 53 miles of deployment after nearly $1 billion had been spent.
What this comparison means: That spending figure comes from a different reporting snapshot than the headline committed amount. It cannot be treated as a construction cost per mile.
How we calculated this and where it comes from
53 miles of deployment following nearly $1B spent
Whole-program spending divided by deployed miles would not be a construction cost per mile. Do not substitute a later obligation figure for this spending snapshot.
What actually happened?
The original program ended in January 2011. The cited deployment account covers 53 miles in Arizona.
Keep in mind: Money committed is not the same as money paid, and dividing all program costs by deployed miles would not give a construction price per mile.
Read the detailed findings
GAO recounts cancellation after obligations exceeded $1 billion; previous oversight identified serious requirements and testing risks.
Reported status: Original SBInet program ended in January 2011 after failing cost-effectiveness and viability standards.
An obligation commits funding; it does not establish that the entire amount was paid, lost, or fraudulent.
Can we follow the payments?
A report can tell us the total. To follow the money, we also need to connect each bill to a payment and to what was received.
Payment records and reporting periods · reviewed November 9, 2026
What could a 3-month funding checkpoint have changed?
Trace the money that went out after a checkpoint. The Receipts Act could require independent progress approval before the next funding release.
Assumes review could prevent 100% of later spending. This includes payments for real work. Actual savings depend on which costs were avoidable, contract obligations, recoveries and assets kept.
SBInet border technology ↗
CBP-reported SBInet expenditures through March 31, 2010. Separate from the larger appropriated and obligated amounts.
- Prime contract award month
- Sep 2006
- Funding checkpoint
- Dec 2006
- Cash spending definitely after it
- $0
- In a reporting period crossing it
- $745,900,000
1 cumulative expenditure total · payment timing remains unresolved
The source gives a cumulative amount inside a broad date window. A range starting at $0 means payment timing is unresolved. A $0 result after source coverage ends means later payments are uncollected.
Inspect the amounts, scope and source documents
Imports the SBInet expended column only. Program management, physical fencing and P25 radio rows are outside this scope.
The reporting window crosses the early checkpoint, so the default result spans $0–$745.9 million. The source cannot narrow it.
The collected spending ends before the July 2010 review. A zero post-review amount means later records are absent.
Accepted equipment and services, outstanding liabilities and recoveries require separate valuation.
| Record | Payment date or reporting window | Included amount |
|---|---|---|
| SBInet expenditures | Oct 1, 2005 – Mar 31, 2010 | $745,900,000 |
The lower amount uses records entirely after the checkpoint, counting indistinguishable repeated rows once. The upper amount also includes periods crossing the checkpoint and unresolved repeated rows. Amounts are never spread evenly across unknown payment dates. Missing records remain outside the total. The selected review date may be later than the first warning.
Payment-record search · Cumulative expenditures added
GAO table 6 reports $745.9 million expended on SBInet through March 31, 2010, separately from $958.0 million obligated and $1,469.2 million appropriated.
Still needed Obtain payments within the cumulative window and after March 2010, then value accepted border equipment and services.
Reviewed November 9, 2026
This total is money committed to the project. The amount actually paid has not been verified here.
Complete invoice-to-payment links
- Invoice
- What was charged.
- Payment record
- What was paid.
- Delivery record
- What was received.
Invoice + payment record
$0 linked hereNo matching invoice and payment records have been added to this file.
The circle shows the share of the displayed total with those records. Blue means linked here; gray means not linked here.
0% means no matching records are linked in this file. It does not describe every record the government holds or prove that money was lost or stolen.
Help make invoices, payments and proof of delivery public.
Support the Receipts ActHow this is measured and which records are linked
This file currently links summary-level sources, with no itemized invoice-to-payment records registered against this amount. The pie measures this collection only. More than $1 billion obligated, not a verified disbursement or loss total. Preserve the source qualifier: this is not an exact spending denominator.
Only invoice and payment records tied to this same amount and scope count. Delivery coverage also requires a linked acceptance record. A report showing a total does not count as an individual receipt.
- Invoice, payment and delivery linked
- $0
- Invoice and payment linked; delivery not linked
- $0
- No matched invoice and payment in this file
- $1,000,000,000
0 matching invoice/payment records; 0 also link to delivery.
No individual invoice-to-payment records are registered in this file yet. This does not establish that those records do not exist elsewhere.
What is still missing?
How much was actually paid, and what equipment or working capability remained in use?
Which records would help answer this?
Obligations commit funding; they are not paid receipts. Disbursements, delivered equipment, reusable capability and closeout recoveries require separate reconciliation.
- Link each contract change and payment to tested software, accepted functionality and deployment milestones.
- Publish independent acceptance-test results, unresolved defects and service impacts, with sensitive details protected.
- Reconcile termination costs, recoveries and reused software or equipment.
These records have not all been assembled here. They may exist elsewhere. Personal details should stay protected.
Can we estimate how much was wasted or stolen?
This file does not establish an independent value for everything delivered. Subtracting a guessed value from a headline amount would not establish fraud. A sound estimate needs matching costs, delivered results and evidence about why any money was lost.
Sources and research notes (5 documents)
These documents support the case. A source document can describe many payments; it is not itself an itemized receipt.
- GAO-13-796T IT initiatives testimony
gao.gov · 2013
- GAO-08-1086 SBInet technology risks
gao.gov · 2008
- GAO-12-22, Arizona Border Surveillance Technology
gao.gov · 2011-11-04
- GAO-10-877R, table 6, funds expended through March 31, 2010
gao.gov · Reviewed 2026-11-09
- GAO-10-340, September 2006 Boeing contract
gao.gov · Reviewed 2026-11-09
Research cutoff: November 9, 2026. Older reports may not include later changes. Read our methodology.