Fabulous Fiber LLC makes a local connectivity bill depend on upstream routes and field repair

Summary

• Fabulous Fiber is a live, locally rooted network rather than a registration without service. Its current website sells business fibre in downtown Kankakee, the city lists it as a local provider, Kankakee County recorded an $8,400 fibre leased-line payment in 2023, and AS54102 was broadly announcing both IPv4 and IPv6 space on 10 July 2026.
• The physical footprint is unusually specific. The company says 6.08 miles of fibre run through Kankakee, with splice points at Court Street and Kennedy Drive, South Schuyler Avenue and East River Street, North Schuyler Avenue and East Oak Street, and East Court Street and South Greenwood Avenue. Its north-south backbone follows the former Illinois Central railway easement.
• Local diversity is not the same as internet diversity. Fabulous Fiber describes a metro ring and multiple paths, but public routing observations show only one neighbouring autonomous system: AS13807, Great Plains Communications. A surviving local ring would not preserve general internet access if that sole visible upstream path failed.
• Installed assets do not reveal recoverable capacity. Six miles of cable, a /23 IPv4 allocation, a /36 IPv6 allocation and advertised symmetrical service up to 1Gbps say little about lit strand count, electronics, uplink headroom, backup power or whether either side of the ring can carry every customer during a fault.
• Local support is the network's advantage and a concentration risk. The company names a president, fibre operations manager, webmaster and fibre specialist, but publishes no repair commitment, spare-parts policy, after-hours dispatch arrangement or measured failover result. For government offices and downtown businesses, restoration can depend on a few people reaching a particular splice point or equipment room quickly.

Six miles make the network concrete

Small internet providers are often described through abstractions: coverage, speed, market share and customer service. Fabulous Fiber can be understood more directly. The company has published the length of its local plant, the streets where it can be opened, the transport corridor it follows and the date of its first active fibre customer. Those details make it possible to see both the utility of the network and its likely points of stress.

The company's account of its origin starts in a Chicago data centre near Cermak Avenue in August 2011. Its servers were housed there because Kankakee did not offer a suitable fibre connection to the company's main premises. The founders had previously operated dial-up access, wireless links and Wi-Fi points in the city. Conversations with carrier technicians led them to consider bringing a fibre route into downtown Kankakee rather than continuing to treat Chicago as the only practical place for bandwidth-intensive equipment.

That history matters because it identifies the original economic problem. Fabulous Fiber did not begin by promising universal household coverage. It began with a local business that could not obtain the connection it wanted at its own premises. Fibre was both an input for its servers and a service it could sell to nearby organisations. The company says it discussed the plan with Kankakee officials in October 2011, received a mayoral letter of support in November, began the first fibre push at North East Avenue and East Oak Street in April 2012, and activated the first customer on 1 December 2012.

The published footprint is precise enough to constrain broad marketing claims. Fabulous Fiber says its network has 6.08 miles in the ground. It names expansion and splice points at Court Street and Kennedy Drive, South Schuyler Avenue and East River Street, North Schuyler Avenue and East Oak Street, and East Court Street and South Greenwood Avenue. It says the main north-south path follows the easement of the Illinois Central railway and that fibre can be extended from the splice locations.

Kankakee's transport geography supports the broad corridor description. The county's 2050 transport plan identifies Canadian National as the north-south railway through Kankakee County and estimates about 40 trains a day across the county. An older county transportation chapter describes the Canadian National line running through Manteno, Bourbonnais, Bradley, Kankakee and Chebanse. The former Illinois Central corridor is therefore not a vague regional reference. It is a heavily used physical axis through the same city where Fabulous Fiber locates its backbone.

The company also describes its topology as a metro ring designed for automatic redundancy. Its current company description says multiple paths branch north and south from a Kankakee network operations centre, with repeater facilities elsewhere in the state and later rings joining the main one. It offers conventional internet access, transport, virtual local-area networks and private links between properties under common control.

Those claims establish an operating concept, not a verified diagram. No public route plan shows where two sides of the ring separate, whether they cross the river or railway at independent points, which segments share duct, and where traffic leaves local plant for long-haul transport. The 6.08-mile figure also lacks a date. It may still describe the full route or only an early stage of a larger system. The safe conclusion is that Fabulous Fiber has disclosed at least a compact downtown fibre system with named access points; the exact current length and physical independence of its paths remain unpublished.

Current service has more than one kind of proof

The operating-status question can be answered more confidently than the topology question. Fabulous Fiber has several independent signs of current activity, and they point in the same direction.

First, the company's present service page offers locally operated fibre in downtown Kankakee and advertises symmetrical download and upload speeds reaching 1,000Mbps. The broader services page offers internet, managed web hosting, backup and small-scale colocation, including 4U of rack space in a local data centre. A separate page identifies six fibre-ready downtown buildings: the Majestic, Executive Centre, Clock Tower Centre, First Trust Bank, PNC Bank and Midland Bank buildings. These are address-specific claims of service readiness, not a national coverage slogan.

Second, local public bodies continue to recognise the company. The City of Kankakee's utilities page calls Fabulous Fiber locally owned, describes diverse paths in the city and lists its internet, transport and private-network services. The Kankakee County economic development organisation includes Fabulous Fiber alongside Comcast under fibre providers. The county chamber of commerce places it in utilities and essential services at 392 East Merchant Street.

Third, the customer evidence goes beyond a name on a website. Kankakee County's fiscal 2023 vendor record lists an $8,400 payment to Fabulous Fiber for a fibre leased line. The county's fiscal 2020 record shows an $8,400 annual web-hosting payment. These records do not reveal bandwidth, endpoints, contract duration or whether the arrangement remains unchanged in 2026. They do demonstrate that the company supplied paid communications services to a local government customer over multiple years.

Fourth, the public internet sees the network. ARIN's AS54102 registration identifies FABFIBERNET and Fabulous Fiber LLC at the Kankakee address. ARIN directly allocated the company 192.81.228.0/23, a block of 512 IPv4 addresses, and 2602:f841::/36, a much larger IPv6 address space. The organisation record was updated in August 2024, and the IPv6 allocation was registered that month.

At 08:00 UTC on 10 July 2026, RIPE's routing-status view showed one IPv4 and one IPv6 prefix originated by AS54102. All 327 sampled IPv4 peers and all 321 sampled IPv6 peers saw the routes. The announced-prefix view identified the same /23 and /36 over the preceding two weeks. Broad route visibility does not prove that every retail circuit works, but it is powerful evidence that the autonomous system is live and reachable.

An outside network inventory supplies a more concrete but less authoritative signal. IPinfo's AS54102 page reports responses from IPv4 and IPv6 addresses, 46 hosted domains and a May 2026 path reaching an address inside the autonomous system. Those observations suggest active hosts and customers. They cannot prove fibre location, subscriber count, uptime or ownership of each responding device. A current operator statement, a dated route map and customer-side measurements would settle those points more directly.

Taken together, this is stronger than any single item. A current offer can remain online after a network closes; a number-resource registration can outlive equipment; and a route can serve only a small hosting system. Here, commercial pages, local-government spending, municipal recognition and live dual-stack routing all align. Fabulous Fiber should be treated as an operating regional provider with a narrow, business-oriented local footprint.

The ownership boundary runs through streets, rooms and contracts

Fabulous Fiber's service depends on infrastructure it controls, infrastructure it probably leases, and infrastructure operated entirely by others. Resilience can only be judged by keeping those boundaries visible.

The clearest company-controlled asset is the local fibre. The business says it put 6.08 miles in the ground and names splice locations. Its offer of dedicated connections between properties and a list of ready buildings imply lateral paths, building entrances and customer handoffs. The company also operates AS54102 and controls the routing of its allocated addresses.

Control is not the same as complete ownership. The backbone follows a railway easement, so access and construction exist alongside an active transport corridor. Street segments require municipal permits and coordination with other utilities. Building entrances depend on property owners. Customer service may traverse risers, conduit and power systems maintained by landlords. Long-haul connectivity comes through a carrier partner.

The original project description names three participating groups: the City of Kankakee, the Daily Journal network operations centre and Great Plains Communications. The company's home page still calls Great Plains its primary partner. Great Plains describes a carrier network of more than 20,000 route-miles, strategic points of presence including Chicago, a round-the-clock network operations centre and wholesale internet connectivity for other providers. Its network map shows regional backbone paths across Illinois and into Chicago.

That partnership solves the economic problem that Fabulous Fiber could not solve efficiently alone. A six-mile local provider does not need to construct its own roughly 60-mile route to Chicago, enter multiple carrier hotels and build a national backbone. It can concentrate capital where local connections are scarce, then buy transport and transit from a larger network whose costs are spread over thousands of route-miles and many customers.

The trade-off is dependency. Fabulous Fiber can repair a local cable and configure its border router, but it cannot independently restore a failed Great Plains long-haul span, core router or Chicago interconnection. It can escalate and enforce a contract. It cannot send its own traffic across an alternative carrier unless such a path has already been bought, built and tested.

The local data-centre boundary is also unclear. Fabulous Fiber's data-centre update announces a new downtown Kankakee facility and describes intended power, cooling and networking capabilities. The page calls the launch upcoming and gives no commissioning date, capacity, backup runtime, location or certification. The current services page nevertheless sells local rack space. That combination suggests a local hosting capability while leaving open whether the announced facility is complete, whether the rack offer uses an older site, and which party operates the building systems.

This distinction matters in an outage. A customer may buy internet, private transport, web hosting and backup from one local company, but the services can fail through different ownership layers. A cut lateral may isolate one building. Loss of the network operations centre can affect routing across the local plant. Failure of long-haul transport can leave local private links working while public internet access disappears. A power event at the hosting site can stop websites while business customers continue to reach the internet. One invoice can conceal several failure domains.

The route table exposes a single visible way out

Fabulous Fiber's own history uses the phrase "single hop to Chicago." As a latency claim, that phrase is imprecise: packets encounter optical equipment and routers even when a route has few routing-domain transitions. As an ownership description, it captures the central dependency. Kankakee reaches the wider internet through a larger carrier network with Chicago connectivity.

RIPE's autonomous-system neighbour view found one neighbour for AS54102 on 10 July 2026: AS13807, Great Plains Communications. Public inventories from IPLocate and IPinfo also identify one upstream. No public peering entry was found for Fabulous Fiber, and PeeringDB returned no network record for AS54102.

This does not prove that only one physical circuit exists. Two geographically separate links can connect the same two autonomous systems. Great Plains could deliver one path north and another south, or one path over fibre and another through a separately routed transport circuit. Private arrangements and backup links may not appear as distinct neighbours in global routing observations. The company says it has multiple paths and repeater facilities north and south, which makes such engineering possible.

The observation still proves a narrower and important point: every broadly visible route from AS54102 enters the public internet through the same adjacent routing organisation. If Fabulous Fiber has two physical Great Plains paths, they provide protection against a local cable or interface failure, but not against every policy, account, backbone or carrier-wide event at Great Plains. Provider diversity requires another independently operated upstream, not merely another port bearing the same carrier's name.

The distinction between local-ring diversity and upstream diversity is easy to miss. Imagine a backhoe cuts the west side of the Kankakee ring. Traffic can reverse around the east side and still reach Great Plains. That is useful local resilience. Now imagine both sides of the ring remain intact but Great Plains withdraws AS54102's routes or loses the only handoff that accepts them. Every customer can still reach the local router, and the local router can still see customer equipment, yet general internet traffic stops.

Routing security adds another unresolved layer. RIPE's IPv4 route-origin validation response and IPv6 response showed no validating route-origin authorisations and an unknown status on 10 July. That is not the same as an invalid route, and the prefixes were broadly visible. It means the cryptographic system did not provide relying networks with an authorisation confirming that AS54102 should originate those blocks.

A second upstream would not fix every routing problem. Both providers must accept the prefixes, filter them consistently and have enough spare capacity. The operator must maintain accurate route records and ensure the same address space can be announced over either path. Customer traffic must return through a working route, and inbound policies must not leave one provider unused until an emergency reveals a configuration error. Real diversity is an operating practice, not a second line on a diagram.

Great Plains itself is changing. In June 2026, its owner announced a plan to combine Great Plains and Ritter Communications as Rightfiber. The announcement says the transaction remains subject to approvals and that service and local relationships will continue. It is not evidence of an impending Fabulous Fiber disruption. It is relevant because the only publicly observed upstream is entering an organisational transition that may eventually alter contracts, systems, escalation paths or network design. Fabulous Fiber's customers need continuity commitments to follow the circuit, not merely the current supplier name.

A ring is only as diverse as its shared ground

The word ring carries a reassuring implication: when one segment breaks, traffic takes the other direction. That behaviour requires functioning electronics and two genuinely separate physical paths. It can fail when paths that look separate on a logical drawing share the same ground.

Fabulous Fiber's public account says the north-south backbone follows the Illinois Central railway easement. Railway corridors are attractive places for fibre because they offer long, continuous rights of way. They also concentrate exposure. Cable on opposite sides of a local ring may converge on one railway crossing, bridge, handhole, building entrance or long-haul connection. A derailment, major track project, flood response or excavation near a shared point can affect more than one nominal route.

The named splice points make repair possible and create operational obligations. A technician responding to a fault near Court Street and Kennedy Drive needs accurate as-built records, access to the correct enclosure, optical test equipment, matching cable and splice materials. The network operations centre must identify the affected span before dispatch. If traffic has already switched around the ring, the repair must avoid disturbing the surviving side.

Illinois law treats underground-facility damage as a serious coordination problem. The Illinois Commerce Commission's one-call enforcement page explains the duties of operators and excavators under the state's Underground Utility Facilities Damage Prevention Act. The current statute requires notification when excavation damages a facility and describes emergency requests for outages requiring action before the ordinary notice period expires.

That system reduces avoidable cuts but does not eliminate them. Maps can be wrong, markings can be incomplete, bores can deviate and private building laterals may be harder to locate. Fibre itself is not electrically detectable unless the installation includes suitable tracer facilities or records. A small operator must participate in locate requests, keep maps current and respond when other construction approaches its plant. This preventive workload competes for the same local labour needed for installation and repair.

Railway access adds another practical question. A splice point beside a city street is different from cable within an active rail corridor. Work may require permission, safety procedures, a flagger or coordination with the right-of-way owner. The county transport plan's estimate of roughly 40 daily trains shows why unrestricted access cannot be assumed. Fabulous Fiber publishes no access agreement or emergency protocol, so the actual response constraint remains unknown.

The best evidence of a resilient ring would be a dated route diagram at a level that protects security while showing separate corridors and entrances. It would identify which customer clusters remain reachable after each segment is isolated. A measured failover test would state the restoration time, packet loss and remaining capacity. Without that evidence, "multiple diverse paths" should be read as a credible design claim, not a guarantee that every common point has been removed.

Installed capacity is not usable capacity

Fabulous Fiber publishes several large numbers: 6.08 route-miles, 1,000Mbps symmetrical customer speeds, 512 IPv4 addresses and a /36 IPv6 allocation. None describes the amount of traffic the network can carry through a serious fault.

Route-miles show geographic extent, not strand capacity. A cable can contain a handful of fibres or hundreds. Some strands may be dark, reserved, leased to another organisation, used for private transport or unavailable because they terminate in the wrong place. Optical equipment determines whether a strand carries one customer wavelength, a shared access system or many high-capacity channels. Fabulous Fiber does not publish cable counts, lit strands, optical design or electronics.

The 1,000Mbps service statement is a customer-port claim. It shows that the company markets gigabit-class access and says its speed tests reach that level. It does not reveal committed information rate, contention, peak utilisation or how many such customers can run simultaneously. A dozen customers with 1Gbps ports do not require 12Gbps at every moment, but a shared uplink must still absorb aggregate peaks and survive failures without unacceptable congestion.

Address space is different again. The IPv4 /23 supports 512 numerical addresses, subject to network design and reservations. The IPv6 /36 contains an enormous number of addresses. Neither moves traffic. Address allocations can support customer circuits, servers, management interfaces and growth while the actual bit rate remains limited by one optical handoff.

The critical figure is recoverable capacity: the throughput left after the largest credible component fails. If two 10Gbps local paths feed one 10Gbps upstream, the network cannot deliver 20Gbps to the internet. If each side of a ring normally carries half the traffic, either side needs enough headroom to carry the whole load during repair. If two upstream circuits share one border router or one power supply, their combined line rate disappears with that common component.

The company says clients are monitored continuously and claims 99.9 percent uptime. A 99.9 percent annual availability level permits about 8 hours and 46 minutes of downtime, although the measurement period, exclusions and service boundary are not stated. The site does not publish a service-level agreement, credits, latency objective, packet-loss limit or repair target. The figure is therefore a marketing claim rather than a contract readers can independently evaluate.

Public routing data provides one useful capacity boundary: AS54102 had one observed adjacent autonomous system. It cannot reveal circuit speed or utilisation. Cloudflare Radar's routing page confirms that the autonomous system announces address space but does not expose Fabulous Fiber's private contract or local port capacity. The most valuable missing figures are the speed of each independent upstream path, normal peak load, remaining headroom after failover and the last date a full-load failover was tested.

Power can stop light without cutting glass

Fibre cable is passive between powered endpoints, but the service is not. Customer equipment converts light to Ethernet. Access switches and optical terminals aggregate circuits. Border routers originate AS54102's routes. Servers, storage and cooling support the local hosting offer. A power failure at the wrong point can leave an intact cable dark.

Fabulous Fiber's route description refers to a network operations centre in Kankakee and repeater or colocation facilities north and south. Its data-centre page promises modern power and cooling but gives no public detail about utility feeds, batteries, generator capacity, fuel, maintenance or runtime. The list of fibre-ready buildings does not say whether each building handoff has backup power or whether customers must protect their own equipment.

The Kankakee County utilities page identifies ComEd as the local electric provider. Grid supply is only the first layer. A resilient communications site needs correctly sized uninterruptible power, generator start capability, tested transfer equipment, fuel and dual power paths to critical devices. CISA's communications dependency guidance notes that communications facilities depend on electricity and that backup generation in turn depends on transportation for fuel.

Customer premises remain part of the power chain. A bank or county building may have its own generator, but a small office can lose its router and optical terminal as soon as local power fails. The provider's network may remain healthy while users report an outage. Conversely, a powered customer can lose service when a remote aggregation cabinet or equipment room lacks adequate backup.

The correct resilience question is therefore not simply whether Fabulous Fiber has a generator. It is which active nodes need power, how long each can run, whether both local paths share a powered site, and whether staff can refuel or replace batteries during a prolonged regional event. A ring whose two sides terminate in one unprotected room has route diversity without power diversity.

The proposed local data centre raises the stakes. Colocation customers expect power, cooling, physical security and upstream connectivity as an integrated service. A hosting outage can also remove monitoring systems, configuration backups or communications used to manage the access network. The company should distinguish the power design of its access network from the design of the rack-space facility and state whether either can operate independently of the other.

Field repair is the local promise under pressure

Fabulous Fiber markets local and responsive support. Its contact page names Tom Small as president, Ron Menard as fibre operations manager, Jennifer Hudson as webmaster and Don Hungerford as fibre specialist. The ARIN registrations name Wade LeBeau and Don Hungerford as technical contacts. For a compact network, direct access to people who know the streets and splices can be a real advantage over a national call centre.

The same structure can create concentration. The public team page names four roles, only two of which are explicitly fibre operations roles. It does not show shift coverage, contractors, on-call rotation or headcount. ARIN's 2014 autonomous-system record says standard network-operations hours are 7am to 5pm Central, while the company says customers are monitored 24 hours a day. Monitoring can detect a failure at night without guaranteeing that a qualified person, a splice trailer and the right materials can reach it immediately.

A fibre cut is not repaired by customer support alone. The response starts with alarms and customer reports, then optical testing to locate loss. Staff must decide whether the cause is a failed optic, dirty connector, damaged lateral, broken backbone or upstream event. A field crew needs safe access, traffic control where required, a prepared cable, splicing equipment and a clean working environment. After joining fibres, the operator must test optical loss, restore protective enclosures, verify every affected service and update records.

Time expands at each ownership boundary. If the damage is on a customer's property, the building owner may control access. If it is in a city street, emergency excavation and traffic arrangements may be needed. If it is near the railway, the right-of-way owner may control safe entry. If the fault lies in Great Plains transport, Fabulous Fiber's field staff can test the local side but must wait for the carrier to restore its segment.

Spares are as important as skill. A compact network needs compatible optics, patch leads, splice trays, closures, fibre cable and replacement routing hardware within reach. An old device can be difficult to replace quickly even when a spare chassis exists, because software, licences and configuration must match. Public materials identify staff and services but not spare locations or restoration stock.

The local-support thesis is strongest when response is measurable. Useful commitments would include a staffed reporting channel, acknowledgement time, dispatch target, escalation path and restoration objective for backbone and building-lateral faults. The operator could publish aggregate performance without exposing customer details: number of unplanned cuts, median restoration time, longest outage and percentage of incidents in which the ring carried traffic around the fault.

Without those figures, local support remains plausible but unpriced operational capacity. It may be excellent. It may also depend on one specialist answering the phone. For an enterprise or public body, the difference belongs in the service agreement before a cut occurs.

Six failure paths define the real bill

The network's economics are clearest when each failure is translated into the work and capacity needed to recover.

1. A downtown lateral or backbone cut

Excavation can sever a customer lateral, one side of the ring or a shared backbone segment. A lateral fault affects one building or customer cluster. A ring-segment fault should trigger protection or routing around the other side, if the topology and electronics support it. A cut at a shared crossing, network operations centre entrance or long-haul handoff can defeat the ring.

The recovery bill includes locating, permits, access, traffic protection, replacement cable, splicing and testing. The resilience test is whether customers remain online during that work and whether the surviving path has full capacity. Named splice points make planned expansion easier, but every added joint is also a place that must be documented and protected.

2. Loss of the Great Plains path

The public route table shows only AS13807 between Fabulous Fiber and the wider internet. Loss can arise from a cable fault, equipment failure, maintenance, account issue or routing-policy error. Local private links may continue while internet-bound traffic fails.

Recovery depends on the number of physical Great Plains circuits and the existence of a second independently operated carrier. If Fabulous Fiber has two Great Plains paths, it should test both and state whether they use separate entrances and long-haul routes. If it has only one upstream path, the economic alternative is a second transit contract whose recurring cost buys protection against a class of outage that the local ring cannot solve.

3. Border-router or optical failure

A single router can terminate multiple circuits and erase apparent diversity. A failed line card, power supply, software image or configuration can withdraw both prefixes. A bad optic can look like a carrier fault. Recovery requires redundant equipment or a tested spare, current configuration, credentials and console access.

The route table cannot identify router count. Broad visibility confirms that the current system works, not that another chassis will take over. The useful evidence is a controlled failover showing that IPv4 and IPv6 remain reachable when each border device is removed.

4. Power loss at a common site

If both ring directions, routing and monitoring pass through one powered room, an outage there can stop the whole service. Batteries cover short interruptions; generators cover longer ones only if they start, carry load and can be fuelled. Customer-side power failures create smaller islands of lost service.

Recovery spending includes batteries, generator maintenance, fuel agreements, dual power supplies and periodic testing. Power diversity can cost more than adding fibre because it must exist at every critical active node. The company provides no runtime figures, so customers cannot yet compare that protection with their own continuity needs.

5. Congestion during failover

A path can remain up while service becomes unusable. If normal traffic is divided over two local routes or links, the surviving path must carry the combined peak after a fault. A gigabit customer port does not guarantee a gigabit through a constrained upstream. Video calls, backups and hosted applications will compete first when headroom disappears.

Recovery is partly engineering and partly commercial. The ISP can add interface capacity, buy more transit, shape non-critical traffic or set clear committed rates. The decisive measurements are peak utilisation and packet loss during a full-path failover, neither of which is public.

6. Too few authorised people

Simultaneous faults expose the limits of a small team. One person may need to diagnose routing while another enters the field. A railway or building fault may require an authorised escort. A carrier escalation may need a contact named on the account. If knowledge, credentials or access reside with one individual, spare equipment cannot restore service by itself.

Recovery capacity therefore includes documentation, cross-training, contractor agreements and access rosters. Fabulous Fiber's named local specialists are an asset. The unanswered question is whether the organisation can sustain round-the-clock response when one person is unavailable or two sites need attention at once.

These scenarios explain the local connectivity bill better than the monthly access price alone. Customers pay for cable and bandwidth, but resilience comes from duplicate paths, spare ports, backup power, maps, contracts and labour that may sit idle until the day they are indispensable.

The affected users sit in a dense downtown cluster

Fabulous Fiber's public footprint is concentrated around central Kankakee rather than spread evenly across the county. The six fibre-ready buildings are clustered on Schuyler Avenue, Court Street and Dearborn Square. The company promotes service for businesses, private links between related properties, hosting and colocation. Its home page names the city and county networks as notable clients, while public spending confirms a county leased line.

That concentration gives the network economic logic. A short route through a business district can reach multiple tenants, banks, government offices and commercial buildings without the cost of passing every suburban home. Shared construction can support higher-value dedicated circuits, private networks and hosting. Local support staff can reach sites quickly from one base.

It also concentrates consequences. A cut near one major junction can affect several fibre-ready buildings. A fault at a shared downtown equipment site can disrupt access, hosted websites and private links at once. Government connectivity can carry administrative services and building systems even when it is not part of an emergency network. The county vendor record does not identify the leased-line endpoint, so its exact criticality should not be assumed.

The residential claim is less developed. The service page says the network can meet business or residential needs, and an older history describes fibre to the home as a future ambition. The published ready-building list is commercial, and the fibre internet page is addressed to businesses. No public address checker, residential price, installation term or household service area defines a broad consumer footprint.

The FCC explains that its National Broadband Map represents mass-market availability reported by providers at serviceable locations. The map shows availability, not performance, affordability or adoption. Fabulous Fiber's strongest documented market is narrower than a citywide mass-market layer: downtown organisations able to justify a site survey and tailored connection.

That is still regionally important. A local carrier can provide a route to buildings that larger operators do not prioritise, connect two local properties without sending traffic far away, and keep technical knowledge in the city. It can also add competitive pressure in a market where the city lists AT&T, Comcast and Fabulous Fiber. The value is not the number of route-miles in isolation; it is which institutions those miles reach and what alternative path they create.

The economics reward density and punish unused resilience

A six-mile network must earn enough from a limited corridor to pay for construction, maintenance, upstream access and skilled labour. The ready-building list suggests how Fabulous Fiber approaches that problem. Pre-positioning fibre or conduit in multi-tenant commercial buildings reduces the cost and delay of each new sale. Once a building is connected, additional tenants can be cheaper to serve than the first.

The service mix spreads fixed costs. Internet access uses the local plant and upstream capacity. Private transport can use local fibre without consuming the same amount of internet transit. Hosting and 4U rack space monetise power, cooling and the network edge. Website work and backups produce service revenue that does not require another street route. A county leased line can provide stable recurring income.

This combination is sensible for a local operator, but it can bundle risks. A customer that buys connectivity, hosting and backup from the same company may simplify support while concentrating failure and supplier exposure. A backup stored in the same downtown power or network domain as the primary system is not geographically independent. The service pages do not state where backups reside or whether hosting has a separate upstream.

Resilience can be difficult to sell because its assets are deliberately underused. A second upstream, spare router, dark fibre path and standby generator add cost before they generate visible customer benefit. A small provider must either recover that cost in every price, charge customers for protected service tiers, or accept a lower margin. Public pages list capabilities but no prices, contract terms or service levels, so the balance cannot be calculated from outside.

Competition sets another constraint. Larger providers can spread backbone, purchasing and support costs across much wider footprints. Fabulous Fiber's advantage is local density, flexible engineering and relationships; its disadvantage is that a few customers or one upstream contract can matter disproportionately. A major customer departure can leave costly plant underused. A large new customer can consume headroom faster than construction adds it.

The announced Great Plains and Ritter combination could eventually improve scale or route options for wholesale customers, but it could also standardise contracts and operations around a larger platform. No public announcement says how Fabulous Fiber will be affected. The local provider's economic protection is to know its physical options: which other carriers pass close enough to supply diverse transit, which buildings can support a second entrance, and which revenue justifies each additional route.

What would turn resilience claims into operating evidence

Fabulous Fiber does not need to publish sensitive customer names or exact cable depths to make its reliability legible. A limited set of dated facts would answer the most important questions.

First, it could publish a current service map that separates active backbone, planned expansion and ready buildings. The map should show independent corridors and common crossings without exposing handhole coordinates. It should date the 6.08-mile figure and state whether the railway-easement path is company-owned fibre, leased fibre or a mixture.

Second, it could define upstream diversity. Customers need the number of physical transport paths, the number of independently operated transit providers, the entrance points and the capacity left after the largest path fails. If both visible paths belong to Great Plains, that should be stated plainly. If a second carrier exists but is not seen as an autonomous-system neighbour, the company can explain its backup role without disclosing commercial rates.

Third, it could document ring performance. A controlled test should isolate each major segment and each border device while measuring convergence, packet loss and remaining throughput. A ring claim becomes meaningful when both directions have carried production traffic and either can support the peak load alone.

Fourth, it could distinguish installed customer speed from committed and recoverable capacity. Published service terms should state whether 1Gbps is a port maximum, best-effort rate or committed rate. Enterprise customers should receive latency, packet-loss, availability and restoration commitments with credits or other remedies.

Fifth, it could define power autonomy at the network operations centre, aggregation sites and local data centre. Useful figures include battery duration, generator load and tested runtime. The company should identify whether both local routes and both border devices share one power domain.

Sixth, it could make local support measurable. A 24-hour fault channel, dispatch objective, current on-call arrangement and aggregate restoration history would show how the named team converts proximity into recovery. Disclosure of spares and contractor coverage can be general rather than security-sensitive.

Finally, route-origin authorisations for the IPv4 and IPv6 allocations would give other networks cryptographic confirmation that AS54102 is authorised to originate them. The current routes are visible and not marked invalid; adding valid authorisations would remove an avoidable uncertainty in a network with one observed upstream.

These are not cosmetic disclosures. They separate capacity that exists in the ground from capacity that will still work during a cut, a power failure or an upstream loss.

Local fibre reaches the internet through a chain, not a slogan

Fabulous Fiber matters because it converted a specific Kankakee bandwidth shortage into local infrastructure. The network has named streets, government customers, commercial buildings, registered address space and live routes. It is not merely a holding company attached to AS54102, and it is not a citywide residential utility on the available evidence. It is a focused regional operator whose value comes from putting fibre where downtown organisations can use it.

Its resilience is harder to establish. The company describes a ring and multiple local paths, but all publicly observed internet routing runs through Great Plains Communications. Its own cable follows a busy railway axis, and its repair promise rests on a small named team. Public materials do not show path separation, backup power, failover capacity, spare equipment or restoration time.

That does not make the network fragile. It makes the proof incomplete. A well-engineered two-path local ring with separate Great Plains handoffs, protected power and practised field repair could be robust. A visually similar network could share one entrance, one router and one long-haul circuit. The difference appears only when each dependency is traced and tested.

For customers, the practical lesson is simple. The local connectivity bill buys more than a gigabit port. It buys a place in a chain running from a building riser to a street lateral, a railway-side backbone, a Kankakee equipment room, a Great Plains path and onward interconnection in Chicago. Fabulous Fiber controls important links in that chain and depends on others for the rest. The network's next measure of maturity is not another speed claim; it is evidence that the chain still carries traffic when one of those links breaks.