AAA Wireless IT's Colville broadband offer reaches BGP through NoaNet while its last mile stays off the map

Summary

• AAA Wireless IT LLC advertises home and business wireless service from Colville at $59.99 a month for 15/2 Mbit and $79.99 for 25/5 Mbit. Those pages remain live, but their underlying copy was last revised in February 2023 and provides no coverage area, installation terms, usage policy, latency target, service-level commitment or evidence that the prices remain the terms a new customer would receive.
• The strongest evidence of a current network is at the internet edge. ARIN registers active AS11253, 23.158.248.0/24 and 2607:5c40::/36 to AAA Wireless IT, while RIPE's collectors saw AS11253 originate one IPv4 and one IPv6 route with full collector visibility on 15 July 2026. Both observed paths terminate through NoaNet's AS16713, the only public neighbour then visible.
• The physical access network is not publicly mapped. The Colville contact address is private mailbox 163 at a UPS Store inside Super One Foods, not evidence of a tower, network operations centre or point of presence. No attributable tower coordinates, fibre route, licensed spectrum, sector inventory, subscriber-radio type, backhaul rate, power design or repair-stock list was found.
• Confidence is therefore Weak for the customer-facing infrastructure claim despite Medium-strong evidence that a small routed network is currently operating. The main unresolved questions are whether the retail offer is actively accepting installations, where it is serviceable, what physical path joins customers to NoaNet, and what happens after a site, handoff, power or sole visible upstream failure.

The address ends at a private mailbox

At 1250 N Highway in Colville, the address AAA Wireless IT gives prospective customers ends at PMB #163. The UPS Store's own location page places its shop at that street address inside Super One Foods and explicitly offers private mailbox services. AAA Wireless IT's contact page uses the same street address, adds the private-mailbox number, and asks prospective customers for a service street, city, state and ZIP code.

That distinction matters. A private mailbox can be a perfectly ordinary mailing address for a small local operator. It is not, without other evidence, a tower compound, equipment shelter, warehouse, staffed repair office, fibre handoff or network operations centre. Mapping PMB #163 as infrastructure would put a false physical pin on the network before the research had even begun.

The identity around the mailbox is nonetheless coherent. The Washington Department of Labor & Industries' public contractor record for UBI 604837713 and licence AAAWIL*784OH identifies AAAWIRELESSIT LLC, gives the same Colville address and phone number, names Dan Nicolas Dizon as an LLC member, and shows an active general construction-contractor registration effective from October 2022 with a stated expiry in October 2026. The record also lists current bond and liability-insurance coverage. ARIN's current point-of-contact record names Dan Dizon, uses the company domain and the same telephone number, and was validated and updated on 7 July 2026.

Those links reduce the risk that the website, state registration and internet number resources belong to unrelated names. They do not establish the scale or nature of the workforce. The state response returned no active workers' compensation account at the research date; that is not an employee count and cannot distinguish owner labour from subcontracted work or prove that nobody performs installations. A construction registration can support physical contracting activity; it is not a telecommunications franchise, radio authorisation, broadband filing, engineering certificate or proof that AAA Wireless IT owns any particular structure.

The company's own About page supplies the clearest description of its operating identity: a local Christian business, family owned and run, building a network for the community. That is specific enough to anchor the business in Colville and to suggest concentrated local decision-making. It is too broad to define the community's boundary, the number of workers, the number of subscribers or the network's physical reach.

A live offer with a 2023 timestamp

AAA Wireless IT's homepage is unusually concise. It describes "wireless network solutions for home and business" and shows two packages: Standard at $59.99 a month with 15 Mbit download and 2 Mbit upload, and Pro at $79.99 a month with 25 Mbit download and 5 Mbit upload. The page returned successfully on 15 July 2026. Its public WordPress metadata, however, says the page was created in June 2022 and last modified on 26 February 2023.

The difference between a live page and a current commercial offer is important. Continued publication is evidence that the operator has not taken the offer down. It is not confirmation that the rates include installation, equipment rental, taxes, a contract term, a data allowance or support. The site publishes no checkout, availability result, terms of service, acceptable-use policy, speed methodology, outage notice, installation calendar, minimum signal requirement or guaranteed activation date. A buyer has to submit an address and wait for a human response.

That address-led intake is consistent with a small wireless network whose serviceability depends on local conditions, but it does not identify the radio system. The site does not say fixed wireless, Wi-Fi, CBRS, licensed microwave, mobile resale or fibre-fed wireless. It names no frequency, vendor, antenna, customer-premises unit, tower, relay, elevation, line-of-sight test or standard installation. Calling it a particular wireless technology would go beyond the operator's words.

The same website also contains a services page offering an on-premises PBX package for $5,000, including a server, ten phones, configuration, connectivity setup and 30 days of support. The page was last modified in August 2022. This makes the business look partly like a local IT and communications integrator rather than a pure access carrier. The construction registration fits that broader picture. It also means the public evidence cannot tell how revenue, staff time or inventory are divided between internet access, installation work and business telephony.

For a customer, the 15/2 and 25/5 numbers are product ceilings on a page, not network capacity. They say nothing about contention at busy hours, backhaul oversubscription, latency, packet loss, tower-sector load, fair-use controls or the number of connections that can be installed before an upgrade. The higher tier's 5 Mbit upstream may be enough for routine calls and light cloud use, but the page itself does not claim suitability for a certain number of video sessions, cameras or remote workers. No independent speed sample was found that could tie either tier to an active subscriber.

Colville is the identity anchor, not a coverage polygon

The defensible geographic statement is narrow: AAA Wireless IT is publicly anchored in Colville, Washington, and calls itself local. Its website asks for a service address but supplies no list of towns, ZIP codes, counties, road corridors or eligible premises. There is no map with a service boundary, no tower-radius graphic, no installation-distance limit and no statement that all of Colville is covered.

The FCC's National Broadband Map guidance explains that provider footprints come from ISP submissions and can be searched by provider or address. A review under the exact AAA Wireless IT and AAAWIRELESSIT LLC names did not yield a clearly attributable public provider footprint. That is negative evidence of limited weight. A small filer can appear under a different holding name or brand, historical filings can lag, and the public interface is not a complete corporate register. It would be wrong to turn the absence of an obvious exact-name result into a claim that the company has no customers or made no filing.

The same caution applies to radio licensing. No exact-name licence surfaced in the FCC's public Universal Licensing System search reviewed for this profile. Yet a missing individual call sign is not evidence of unauthorised operation. The FCC's fixed-wireless technology guidance distinguishes unlicensed, licensed and licensed-by-rule last-mile service. A provider using only Part 15 unlicensed spectrum for the last mile may operate without an individual spectrum licence, while CBRS General Authorized Access is licensed by rule. Without an operator disclosure or attributable filing, the spectrum category remains unknown.

There is real regional infrastructure around Colville, but it cannot be assigned to AAA Wireless IT merely because it exists. NoaNet says its network has more than 3,800 miles of plant touching every Washington county. Its Stevens County case study says NoaNet and the county agreed in 2012 to bring middle-mile fibre into the county. A later central Stevens County project describes a separate hybrid fibre-to-the-premises and wireless build.

Those facts establish that wholesale and public-benefit network plant exists in the region. They do not show that AAA Wireless IT uses a particular fibre, pole, tower or public project. The BGP relationship with NoaNet is the bridge between the two organisations, but BGP identifies a logical routing dependency, not the street-level path or title to an asset.

AS11253 is the strongest current operating evidence

ARIN registered AS11253 under the name AAAWIRELESSIT on 19 July 2023 and still marks it active. ARIN separately registered 23.158.248.0/24 to AAA Wireless IT on 1 August 2023. That IPv4 block contains 256 addresses, including network and broadcast positions under conventional subnet use. It is a finite address resource, not 256 customers, routers or available installations.

On the publication date, RIPE's routing-status observation for AS11253 saw one IPv4 route representing 256 addresses and one IPv6 route, with one observed neighbour. All 326 responding IPv4 collector peers and all 322 responding IPv6 collector peers saw the origin. RIPE's announced-prefix timeline shows 23.158.248.0/24 and 2607:5c40::/32 continuously visible throughout the 1-15 July window.

That is strong evidence of an operating internet edge. A route visible to every reporting collector is not a dormant ASN sitting only in a registry. It means other networks were receiving a path to the addresses through BGP. Collector visibility still does not prove that a residential radio was connected, that every address answered, that traffic was flowing at a certain rate or that a route would survive the next failure.

The historic first-seen field needs special handling. RIPE's status output associates AS11253 with an old 209.83.37.0/24 observation from August 2000. ARIN's current AAAWIRELESSIT registration dates only from 2023. Autonomous system numbers can have histories that precede a current holder. The 2000 collector record cannot be presented as 26 years of AAA Wireless IT operation; the attributable current network record begins with the 2023 ARIN registration unless the company supplies evidence of an earlier continuity.

The website itself does not sit inside AS11253. Public DNS on 15 July 2026 resolved aaawirelessit.com to 165.140.70.189, whose reverse name was cloud208.cloudwebhosting.com; the domain published no IPv6 address. The site therefore depends on external web hosting rather than demonstrating a server on the access ASN. That separation is ordinary and may keep the contact page reachable during a local network problem. It also means website uptime cannot be used as a proxy for customer-network uptime.

The IPv6 route is larger than the registered block

The IPv6 evidence has a material boundary problem. ARIN's AAA Wireless IT IPv6 record covers 2607:5c40::/36, registered in July 2023 and last changed in August 2025. A /36 contains 4,096 conventional /48 customer or site blocks. Even that mathematical subdivision is not evidence that 4,096 customers are connected or that the operator has configured any of them.

The public route is not the /36. RIPE collectors saw AS11253 originate 2607:5c40::/32, a block sixteen times larger in /48 terms. Addresses in the other fifteen /36-sized portions resolve only to ARIN's broad parent space rather than to an AAA Wireless IT allocation. The visible route therefore covers address space beyond the organisation-specific ARIN record reviewed here.

NoaNet's routing maintainer created the corresponding RADB route6 entity as a proxy registration for AAA Wireless IT in August 2023. Proxy registration is consistent with an upstream helping a customer publish routing policy. It does not resolve why the route object's /32 is broader than the organisation's /36 registration.

The discrepancy should be treated as a question, not a verdict. There may be a registry record, reservation, operational arrangement or correction path not exposed by the records reviewed. It would be reckless to label the route a hijack or to claim that every address in the /32 is unauthorised. It would be equally reckless to count RIPE's reported 65,536 /48 equivalents as AAA Wireless IT's registered, installed or sellable capacity. The company and ARIN are the appropriate parties to clarify the intended scope.

Route-origin authorisation is also absent. RIPE's RPKI check for the IPv4 route and RPKI check for the IPv6 route both returned unknown, with no validating ROAs. Unknown is not RPKI-invalid: it means the cryptographic authorisation was not present for the validator to confirm or reject the origin. A suitable ROA for the registered resource would improve routing assurance, but it would not add bandwidth or redundancy.

Every visible path runs through NoaNet

RIPE's AS-neighbour observation found one neighbour for AS11253 on 15 July 2026: AS16713, Northwest Open Access Network, commonly called NoaNet. It found no right-side downstream neighbours and no uncertain neighbours. Looking-glass paths from many collectors ended with AS16713 AS11253 for the IPv4 route, and the RADB entities for both visible prefixes are maintained by NoaNet.

Taken together, this is persuasive evidence that NoaNet is AAA Wireless IT's public upstream route to the wider internet. The evidence does not reveal the contract, handoff speed, port, commit, billing structure, physical entrance, aggregation router or whether a private backup session exists but is not currently propagated. "One observed neighbour" should be read as one demonstrated public routing relationship, not a complete drawing of every cable.

NoaNet is a substantial wholesale dependency. ARIN marks AS16713 active. NoaNet describes itself as a nonprofit public broadband organisation owned by public utilities, operating an open-access network. Its network-services page says it offers BGP or static internet, IPv4 and IPv6, Ethernet, transport from 1G to 100G, a 96-channel DWDM system, 1G or 10G E-NNI ports, and colocation at 35 regional access points. PeeringDB's AS16713 profile lists two operational 100 Gbps Seattle Internet Exchange connections, a 10 Gbps Northwest Access Exchange connection and a 10 Gbps SpokaneIX connection, plus facilities in Seattle, Portland, Bellingham and Spokane.

None of those figures can be assigned to AAA Wireless IT. They describe NoaNet's network or declared exchange ports, not the capacity delivered to AS11253. A 100 Gbps exchange port in Seattle does not make AAA's last mile 100 Gbps, and a 1G or 10G wholesale product option does not prove which one was ordered. The only customer-facing rates in AAA's own public record are 15/2 and 25/5 Mbit.

NoaNet's statewide reach can still be useful to a small rural operator. A wholesale open-access backbone lets a local company focus capital on access sites, customer acquisition, installation and repair rather than building a route to Seattle from scratch. The economic bargain is concentration: outsourcing middle-mile and transit can lower entry cost, but it moves a significant failure and negotiating boundary to the wholesale handoff.

Public routing shows no second upstream capable of carrying the prefixes if AS16713 withdraws them. No published failover test shows a private or dormant alternative. NoaNet itself advertises resilience, multiple peers and diverse routes, which can protect failures inside its wider network. That resilience does not remove the specific dependency between AAA's edge and NoaNet. A resilient supplier can still be reached through one customer handoff, one access tail, one router or one power domain.

The last mile has no public asset register

Between a customer's service address and AS11253, the public record goes blank. AAA Wireless IT does not identify a tower, rooftop, water tank, grain elevator, mast, relay, shelter, cabinet, fibre terminal, leased circuit, colocation site or radio type. It does not publish tower heights, azimuths, sector counts, frequencies, channel widths, fade margins, installation distances or line-of-sight requirements.

This is not proof that the assets do not exist. Small private operators often lease space, use private land or avoid publishing security-sensitive coordinates. It does mean that no independent reader can reconstruct the access path from the company's materials. A coverage claim cannot be tested against terrain; a route cannot be checked for common poles or conduit; a tower outage cannot be bounded to a known group of subscribers.

The construction registration is relevant but limited. It indicates that the LLC is registered for general contracting in Washington and maintains the bond and insurance shown by the state. It could support installation work. It does not say whether the company climbs towers, buries cable, performs electrical work, uses subcontractors, owns bucket vehicles or keeps certified radio technicians. Licence categories and individual qualifications would have to be matched to the work actually performed.

No attributable FCC antenna registration was identified. That absence does not exclude shorter structures, customer rooftops or structures outside the registration thresholds. No exact-name individual spectrum licence was identified, but unlicensed or licensed-by-rule operation remains possible. No public pole-attachment agreement, tower lease, easement, county permit or environmental filing was found that could place an access site.

Nor does an IP address place the network. Commercial geolocation pages may label AS11253 addresses as Colville or use a generic US location because the ARIN contact is in Colville. Registry address, latency and geolocation are not tower coordinates. The correct map therefore has a Colville administrative anchor, a logical AS11253-to-AS16713 edge, regional NoaNet plant, and a large blank where AAA's physical access topology should be.

Retail speed is not installed capacity

The 25/5 Mbit Pro tier is the largest numeric customer service on the site. If ten Pro customers simultaneously downloaded at the advertised maximum, they would demand 250 Mbit/s before protocol overhead. One hundred would demand 2.5 Gbit/s. Those examples illustrate aggregation arithmetic only; the company publishes neither subscriber count nor concurrent usage, so they must not be mistaken for actual load.

Several capacity states are missing. There is no design capacity for a radio sector or backhaul. There is no installed count of access points, sectors or fibre strands. There is no powered inventory showing which equipment is in service. There is no operational capacity measured after interference, weather and protocol overhead. There is no sold capacity, oversubscription ratio, reserved headroom or threshold for suspending new installations. There is no failure-usable capacity showing what remains after a radio, power supply, backhaul or upstream fails.

The routed /24 also cannot fill those gaps. Public IPv4 addresses may be placed on infrastructure, translated gateways, customer devices, management systems or held unused. Carrier-grade address translation could support more customers than public addresses; one-to-one assignments could support fewer after reserving infrastructure. IPv6 provides a much larger numbering canvas, but numbering is not spectrum, airtime, backhaul, power, tower space or labour.

NoaNet's product catalogue supplies plausible wholesale rate options but no AAA-specific order. The regional middle mile may have ample capacity while the customer-facing bottleneck sits in a wireless sector. The reverse is also possible: a clean radio link can still be constrained by a small handoff. Without measurements at both sides, a buyer cannot locate contention.

The economics of the two advertised plans therefore depend on variables hidden from public view. At $59.99 and $79.99 per month, a small subscriber base has to cover upstream service, site rent, power, equipment replacement, vehicle time, insurance, support, address resources and administration. Density helps because one access site and one repair trip can serve more paying locations. Sparse terrain raises the cost per connection. Those are standard fixed costs for a local access network, not evidence of AAA's profit, loss or customer count.

The PBX offer adds another uncertainty. Integrator revenue may subsidise network labour or compete for the same people during an outage. A family-run structure can make escalation direct and accountable, but it can also concentrate knowledge and availability in very few individuals. The public record does not disclose whether monitoring, field work or customer calls are handled by one person, a family team, employees, subcontractors or NoaNet services.

The wholesale relationship changes the cost curve, not the evidence rule

For a network this small, obtaining an ASN and portable address space is strategically different from merely reselling a larger carrier under that carrier's addresses. AAA Wireless IT can publish its own routing policy, retain an identifiable network edge and, in principle, change upstreams without renumbering every public-facing system. The 2023 registration sequence - ASN in July, IPv6 later in July, IPv4 in August, followed by NoaNet-maintained route objects - is consistent with a deliberate network turn-up. It is not enough to show when customers first received service or how many were migrated.

The arrangement also divides costs and responsibilities. NoaNet can aggregate long-distance transport, exchange connectivity and backbone operations across many users. AAA can concentrate on customer qualification and the local access layer. This can make a low-density market possible where duplicating regional fibre would not be. The trade-off is that the retail provider's service quality depends on a contract and handoff the public cannot inspect. Wholesale backbone scale does not automatically produce retail redundancy.

Route portability has limits as well. A /24 is the conventional smallest widely accepted IPv4 announcement, so AAA's entire visible IPv4 estate sits in one globally routed unit. A filtering or origin error can affect all of it at once. The IPv6 estate has a different problem: the route is broad, but the organisation-specific registration reviewed is narrower. Neither circumstance tells a customer whether their connection uses a public address, private translation or IPv6 delegation.

The absence of a PeeringDB profile for AS11253 reinforces the information gap without proving technical weakness. PeeringDB is voluntary and often incomplete for small access networks. A profile could state whether the network has an open, selective or restrictive interconnection policy and where it can connect. Its absence means there is no operator-declared facility, exchange port, traffic band or public peering contact there; it does not negate the NoaNet relationship seen by route collectors.

The useful economic conclusion is modest. AAA has taken on some of the fixed cost and operational responsibility of running an independent internet edge, while apparently buying the only publicly visible path onward from a public-benefit wholesale carrier. What remains unknown is whether the paying base and installed access plant are large enough to support preventative maintenance, spare equipment, after-hours cover and a second failure path. Those are the investments that turn routing independence into customer resilience.

Six failure boundaries sit between the customer and the internet

The absence of an asset map does not prevent a failure analysis; it changes the analysis from claims about named equipment to questions at each boundary.

First, the customer site. A wireless service ordinarily needs powered equipment at or near the premises, but AAA does not identify its installation. A failed power supply, damaged cable, displaced outdoor unit, router fault or local electrical outage could stop one customer while the network remains healthy. The site publishes no equipment-ownership rule, replacement charge, remote diagnostic method or target for a visit. It also does not say whether a backup battery is supplied.

Second, the radio path. If the service is outdoor fixed wireless, vegetation, obstruction, interference and alignment can affect the path. Because the frequency and architecture are unknown, this article cannot assign a fade margin, range or weather sensitivity. Indoor Wi-Fi, CBRS and licensed microwave have different failure behaviour. The due-diligence question is not "will weather break it?" but "what technology and measured margin support this address, and what minimum signal is accepted at installation?"

Third, the access site. Multiple customers may share a radio, switch, cabinet or mounting structure. A site power failure, software fault or common antenna problem could therefore create a local cluster outage. No site count, backup runtime, remote reboot path or generator procedure is public. NoaNet says backup power of eight to 24 hours is available at its regional colocation sites, but that is a NoaNet facility claim and cannot be transferred to an unidentified AAA access site.

Fourth, the backhaul or access tail. Customer traffic must reach the AS11253 router and the NoaNet handoff somehow. The path could be fibre, licensed or unlicensed wireless, leased Ethernet or a combination. A single cut, radio fault or intermediate power loss could isolate otherwise healthy customer sectors. The regional presence of NoaNet fibre does not prove that the AAA handoff has two physically diverse approaches.

Fifth, the network edge and upstream. Both visible prefixes depend on the public AS16713 path. A configuration error at AS11253, handoff fault, route filter, edge-router failure or loss of the sole observed upstream can make the entire routed estate unreachable. The routes had excellent global visibility on 15 July, but visibility is a snapshot of success, not a failover test. The lack of ROAs leaves origin validation unavailable to networks that enforce RPKI policy.

Sixth, human restoration. ARIN's ASN record states standard NOC hours Monday through Thursday, 7:00 a.m. to 4:00 p.m. PST. The organisation record gives Monday through Thursday, 7:00 a.m. to 3:00 p.m. Pacific. The one-hour conflict and omission of Friday through Sunday are small details with large operational implications. They do not prove that emergencies go unanswered; they show that the public promise is incomplete and internally inconsistent. The website supplies a phone, email and contact form but no 24-hour fault route, priority matrix, response target, status page or escalation tree.

These boundaries can combine. A regional power event can affect a customer, a relay and a wholesale access point at the same time. A spare radio is useful only if a qualified person can reach the site. A second BGP session is useful only if it follows a sufficiently independent powered path. Redundancy has to be attached to the failure being mitigated.

The people exposed by an outage

AAA Wireless IT markets to homes and businesses, not a named vertical. That makes the affected-customer boundary broad but unquantified. A residential outage can interrupt remote work, schoolwork, telehealth access, cloud security cameras and ordinary communication. A small-business outage can stop card authorisation, hosted applications, voice service and customer contact. The PBX offer suggests that some customers may depend on the same local provider for both data connectivity and telephone integration, although no evidence shows that an active PBX customer also buys the internet service.

The lower advertised upload rates deserve attention. Cloud backups, camera uploads and multi-party video calls all compete for upstream capacity. A 2 Mbit or 5 Mbit advertised maximum is not necessarily the continuously delivered rate. A saturated upload can increase latency for other traffic even while downloads remain below their ceiling. The operator publishes no queue-management policy, traffic-priority option or business tier with a committed rate.

Small providers can offer advantages that large carriers struggle to reproduce: local knowledge, a direct decision-maker and willingness to evaluate an awkward address. The contact form's service-address fields support an individual qualification process. But local support is itself an infrastructure dependency. If a small number of people hold the site keys, spares, climbing relationship and router knowledge, their availability becomes part of recovery capacity.

The state response's absence of an active workers' compensation account should not be used as a headcount. Owners and contractors can sit outside that administrative record. It is still a signal that the public record does not demonstrate a staffed field organisation. Buyers who need continuity should ask who is authorised to work on each site, who covers illness or leave, where compatible spares are stored and whether NoaNet or another contractor can act without the principal present.

No historic outage log, customer count, complaint record, mean-time-to-repair series or service-credit history was found. The lack of adverse reports is not evidence of excellent uptime; the lack of public praise is not evidence of poor service. A small network may simply have a small public footprint. The correct conclusion is that performance history is unavailable.

What a customer should ask before installation

A serious serviceability response should identify more than "yes" or "no." It should state the access technology, whether clear line of sight is required, the planned mounting point, who owns the outdoor and indoor equipment, the installation charge, expected signal margin and the conditions that can trigger a resurvey. The customer should know whether the 15/2 or 25/5 rate is an advertised maximum, a shaped rate, a typical busy-hour result or a minimum commitment.

For the path beyond the premises, the operator should identify the failure domains without disclosing sensitive coordinates. How many customers share the serving sector? What is the backhaul medium and rate? Is the handoff to NoaNet single or diverse? Do alternate paths share a pole line, tower, power supply or router? Is there a second upstream that can originate the same prefixes? When was failover last tested under load?

The IPv6 question needs a direct answer. Why does AS11253 advertise 2607:5c40::/32 when the reviewed ARIN organisation record covers 2607:5c40::/36? What resource authorisation covers the broader route? Are customers delegated IPv6 prefixes, and if so, of what size? Will the company publish ROAs for the intended IPv4 and IPv6 announcements? These are routing-hygiene questions, not accusations.

Support terms should reconcile the two ARIN NOC windows and explain Friday, weekend and holiday handling. A business buyer should ask for fault reporting, acknowledgement and restoration targets, planned-maintenance notice, service credits, escalation contacts and the point at which a site visit is dispatched. If the service is best effort, that should be explicit rather than inferred.

Power and spares are equally concrete. How long can the serving access site and edge router operate without utility power? Is backup runtime tested under full load? Is a generator available and refuelled? Which radios, power supplies, surge protectors and routers are kept locally? How quickly can a failed customer unit or sector radio be replaced? No public source answers these questions.

Finally, the buyer should plan an independent path for critical functions. A cellular or satellite backup can fail differently from a local terrestrial route, but only if it is tested and does not depend on the same site power. Voice, payments and cloud authentication should have documented fallback procedures. The need for a backup does not make AAA's service defective; it reflects the consequence of buying a best-effort connection whose redundancy is not publicly demonstrated.

What would raise the evidence grade

The grade would improve first with a current, operator-published service description. It should date the prices, define installation and equipment, identify technology classes, describe typical and minimum performance, and state whether residential and business terms differ. A service-area map could show approximate eligible zones without revealing exact tower coordinates.

Second, the operator could publish a sanitised infrastructure diagram. It need not expose security-sensitive locations. Counts and failure domains would be enough: number of access sites, whether each has backup power, type and nominal rate of backhaul, location class of the NoaNet handoff, number of edge routers and whether a second upstream exists. A dated failover result would be stronger than a generic redundancy claim.

Third, the route records need reconciliation. ARIN and the announced IPv6 scope should align or be explained by an attributable authorisation. ROAs covering the intended announcements would change RPKI status from unknown to a cryptographically testable state. An operator-maintained PeeringDB profile could document scope and interconnection without claiming more than it knows.

Fourth, physical and labour evidence could remain modest but specific: active site leases or permits with sensitive details redacted, a count of installed sectors, a current insurance and contractor boundary, repair coverage, spare inventory categories and after-hours escalation. Publication of customer numbers is not necessary to disclose whether the network is still accepting installations and how it handles capacity limits.

Fifth, performance evidence should distinguish marketing from measurement. Aggregate busy-hour speed, latency, packet loss and availability by tier would be more useful than isolated speed tests. A restoration report can state cause, affected service area and corrective action without naming customers. Repeated, dated evidence would show whether a family-run network converts local proximity into dependable repair.

A real edge, an unproven access network

AAA Wireless IT is not merely a name on an old webpage. The website was reachable, the state contractor registration was active, the ARIN contact was freshly validated, and AS11253's IPv4 and IPv6 routes were visible to every responding RIPE collector on 15 July 2026. The AS11253-to-NoaNet relationship is current and well corroborated. Those are meaningful operating signals for a very small regional network.

The signals stop at the edge. Public evidence does not establish one active paying subscriber, one serviceable street, one tower, one fibre handoff, one backhaul rate or one hour of backup runtime. It does not show a second upstream, a tested failover path, a staffed weekend response or spare capacity after a shared component fails. The advertised packages may still be sold exactly as written, but their 2023 page dates make that a question for the operator, not a fact for the reader.

The final network evidence grade is Weak. That grade does not mean the company or service is false. It means a live routed edge and coherent business identity cannot substitute for evidence of the customer-facing plant, geographic reach, capacity and recovery design. In this case, the most honest map has a precise private mailbox, a globally visible ASN, one visible upstream and a blank last mile. Filling that blank requires current answers from AAA Wireless IT, not assumptions borrowed from NoaNet's statewide network or from the word "wireless."