A 2.7-kilometre outage scenario exposes the unknowns in INFOCERTO's coastal fibre resilience

Summary

• Anatel's May 2026 records report 373 INFOCERTO accesses in Torres: 315 over fibre and 58 over radio. Those are dated provider-reported accesses, not a current customer count, route map, port inventory or measure of bandwidth available during a failure.
• At 08:00 UTC on 16 July, AS270246 originated one IPv4 /22 through one publicly observed neighbour, AS52600. Every one of 380 collected paths crossed that neighbour immediately before INFOCERTO, but BGP cannot show whether the handoff uses one circuit, several circuits or physically diverse routes.
• Torres has documented exposure to strong coastal winds, fallen trees and poles, standing water and utility interruption. No public record identifies INFOCERTO's pole contracts, feeder routes, ring design, network-site backup runtime, current spare stock or the location and depth of its field crews.
• The company presents a 24-hour WhatsApp on-call channel and has historical evidence of hands-on troubleshooting. That is useful evidence of local support, but it does not establish night dispatch, simultaneous-incident capacity or restoration time.

The easy distance is the one on the road

Consider a failure at 05:40 on a damp winter morning in Guarita. This is an analytical scenario, not a report of a real INFOCERTO incident. A small guesthouse still has mains power, its Wi-Fi router is lit, but the optical terminal shows loss of signal. Wind has moved through the coast overnight. The pavement is wet. Somewhere between the premises and the next working optical point, light has stopped.

The public geography makes one part of the problem unusually concrete. INFOCERTO publishes its customer-facing address at Rua Coronel Pacheco 350, Loja 10, Torres, on its contact page. An OpenStreetMap-derived geocoding result for that address places it at the Amalfi Center. A separate Guarita result provides a defensible district-level anchor. A driving-route estimate between those two points returns 2,670.8 metres.

That 2.7 kilometres is useful precisely because it is the least important distance unless several unstated assumptions hold. It assumes that the nearest capable technician begins at the shop. It assumes the shop is a dispatch point rather than only a retail and support address. It assumes the technician can leave immediately, that the road is clear, that the fault can be reached safely, and that the vehicle carries the correct optical test equipment and replacement parts. None of those assumptions is established by the address.

The next distance is harder. If the loss is a damaged drop, the repair may be local. If a distribution cable has failed, the crew must find the break and the affected branch. If a feeder, OLT, radio backhaul or local edge has failed, the relevant point may be elsewhere. If the problem lies at the external handoff, the decisive distance is from INFOCERTO's edge to the next usable path into its visible upstream, AS52600. No public record locates that handoff.

This is the central resilience problem. The road from a public storefront to Guarita can be estimated in metres. The physical path from a Guarita customer to a distribution point, feeder, edge router and alternate upstream cannot. Yet those hidden distances, plus access permission, power, skills and parts, determine restoration.

The scenario is locally plausible without being attributed to INFOCERTO. Torres reported that a July 2023 extratropical cyclone brought fallen trees and poles, blocked streets, standing water and electricity loss, with pole falls specifically mentioned in Guarita. In April 2026, the municipality again issued a strong coastal-wind warning and advised residents to stay away from trees and electricity networks. These records establish the hazard environment. They do not establish that an INFOCERTO cable was on any affected pole.

A live provider, more precisely bounded than its marketing

INFOCERTO's current homepage describes a technology company in Torres, says it has operated there for more than ten years, markets fibre internet from R$109.90, and presents fixed telephony, cloud PBX, computer support, commercial automation, cameras and access control. This is a broad local technology proposition, not merely a commodity broadband price.

The legal and network identity is unusually coherent for a small provider. INFOCERTO's SCM contract names Dalzochio e Matos Ltda, CNPJ 10.433.940/0001-28, at the same Torres address. It cites Anatel process 53500344646202245 and authorising act 1 of 2 January 2023. A recently refreshed corporate-record mirror corroborates the active CNPJ, INFOCERTO trade name, address, telephone and activity codes that include multimedia communications and fixed telephony.

The internet-number records align with that identity. Registro.br assigns AS270246, the IPv4 block 45.191.36.0/22, and the IPv6 block 2804:6910::/32 to Dalzochio e Matos Ltda. Anatel's fixed-broadband records use the same CNPJ and the INFOCERTO name.

That alignment matters. It reduces the risk of confusing a shop, a legal entity and a routed network that merely share a similar brand. It supports a firm conclusion that INFOCERTO is not just an old listing or dormant web page. There is current regulator-reported service and a current routed IPv4 edge.

But the same evidence imposes a boundary. Corporate activity codes do not prove installed fibre. An SCM authorisation does not prove a street footprint. An ASN allocation does not prove that a customer can reach the internet. A routed prefix does not prove that the last mile is intact. Each record answers a different question.

The strongest present operating evidence is the combination: current company contact surfaces, 2026 Anatel access rows and a publication-date BGP observation. The weakest area is physical resilience. No reviewed public material identifies an INFOCERTO POP, OLT site, radio site, cabinet, pole sequence, feeder, fibre ring, upstream handoff, parts store or network-site power system.

The company's own contract anticipates this separation. It says INFOCERTO may employ equipment and infrastructure that it does not own and may use resources from another telecommunications provider. That is normal in regional broadband. It also means a customer experience may cross several ownership and repair boundaries before reaching the public internet. The company remains responsible for the contracted service, but a pole owner, power distributor, property owner or upstream carrier may control the next physical action.

One verified service municipality, not a guessed coastal footprint

The most defensible current service geography is Torres. The company names Torres. Its public address is in Torres. More importantly, Anatel's fixed-broadband archive contains 120 INFOCERTO rows for January through May 2026 under CNPJ 10433940000128, and the reviewed rows all name Torres, municipality code 4321501. Anatel explains that SCM providers submit access information through its access-data collection process.

Torres is not a trivial dot on a map. IBGE gives it an area of 161.63 square kilometres, a 2022 population of 41,751 and a 2025 estimate of 43,344. A municipal coast description says Torres has 24 beaches from the Mampituba boundary in the north to the Arroio do Sal boundary in the south. A provider can be very local in commercial identity while still facing a long, irregular field geography.

Nothing in the access count says how those accesses are distributed. Three hundred fibre customers in a few compact streets produce a different repair problem from three hundred spread along a coastal ribbon, across inland roads and through multiple pole corridors. One feeder serving dense blocks can be efficient but concentrated. Several short feeders can reduce the size of a single failure while increasing the number of powered and maintained sites. Without approximate feeder areas, splitter domains or route kilometres, "315 fibre accesses" has no resilience geometry.

Passo de Torres is the most tempting place to overreach. It is immediately across the Mampituba, which the municipality describes as the state boundary between Rio Grande do Sul and Santa Catarina. IBGE estimates 14,859 residents in Passo de Torres in 2025. The road estimate from INFOCERTO's public address point to a Passo de Torres locality point is only 2,127.6 metres.

INFOCERTO also has visible community associations there. A 2024 Passo de Torres municipal report names InfoCerto among the supporters of a local volleyball team. A 2018 sports document refers to the Taca Infocerto Fibra Optica in Passo de Torres.

Those signals show commercial familiarity, not service. No current INFOCERTO coverage page reviewed here names Passo de Torres, and no reviewed 2026 Anatel row under the INFOCERTO CNPJ names it. The river and bridge make the distinction physical, not semantic. Torres reported in 2024 that the concrete bridge connecting the municipalities had a restriction on vehicles above 10 tonnes because of structural concerns. A normal service van would usually fall well below that threshold, but the notice illustrates a larger point: crossing into an adjacent town depends on specific infrastructure. Fibre would need a particular bridge, pole line, conduit, radio path or other crossing. Proximity does not supply that route.

The evidence therefore supports a disciplined map: verified reported service in Torres; adjacent commercial visibility in Passo de Torres; no public multi-town network map. If INFOCERTO serves beyond Torres, an operator statement or regulator row can establish it. Until then, resilience should be tested inside the one verified municipality rather than projected across the coast.

What 373 reported accesses do - and do not - reveal

The May 2026 Anatel rows report 373 INFOCERTO accesses in Torres. Of these, 315 are recorded as fibre and 58 as radio. The customer-type field divides them into 245 individual-person and 128 legal-person accesses. The fibre rows carry nominal speeds of 50, 100, 200, 300 and 400 Mbps; the radio rows carry 5, 10 and 20 Mbps.

These are valuable numbers because they establish an operating mix that the current homepage alone would not reveal. Fibre dominates, but radio has not vanished from the regulator report. INFOCERTO is therefore better understood as a mixed-access regional provider at that reporting date, even though its current public sales language foregrounds fibre.

The numbers still require restraint. An access is not necessarily a unique human customer. A business can hold more than one access. A household can change plans or technology. A row does not identify an occupied optical port today, an active session, a paying account in good standing or a line that will survive a feeder failure. The records are provider-reported and subject to filing quality.

The monthly sequence makes that caveat impossible to ignore. The same CNPJ totals 323 accesses in January, 29 in February, 522 in March, 363 in April and 373 in May. A fall of roughly nine-tenths followed by a rise to well above the January figure could, in theory, represent extraordinary commercial movement. It is far more prudent to treat it as a possible reporting discontinuity, incomplete filing, revision or classification change. There is no independent evidence of a mass disconnection and reconnection.

May is therefore a dated snapshot, not a customer census. It is useful for four conclusions:

1. INFOCERTO was reporting active fixed-broadband service in 2026.
2. The reported service was in Torres.
3. The reported access mix included both fibre and radio.
4. The scale was in the hundreds of reported accesses, not a basis for claiming thousands.

It cannot answer route density. Dividing 315 fibre accesses by Torres's 161.63 square kilometres would create a meaningless municipal average, because people and fibre are not evenly distributed. It cannot answer installed capacity. A 400 Mbps retail row does not identify the PON line rate, split ratio, uplink, transit commit or busy-hour load. It cannot answer failure-time capacity. A nominal 400 Mbps access on a cut feeder has zero usable throughput until the path is restored.

The customer-type split is similarly informative but bounded. The 128 legal-person accesses show that business connectivity is not hypothetical. INFOCERTO also markets fixed telephony, cloud PBX, cameras, access control and commercial technology services. Yet the records do not identify which businesses buy which services, whether those services use INFOCERTO access, or whether any customer has a protected circuit or service target. The appropriate impact statement is conditional: a broadband failure may also disrupt voice, remote surveillance, access-control administration or retail operations where those services depend on the failed connection.

Poles, power and the difference between a route and a right to repair it

Fibre is often described as if the glass itself were the system. In a small city, resilience may depend just as much on the structure carrying it, the electricity beside it and the permissions governing both.

Torres offers unusually direct public evidence that telecom cables occupy electricity-distribution infrastructure. In January 2022, the municipality reported that CEEE Equatorial would begin inspecting occupants of its distribution network, regularising attachments and removing inactive or undeclared telecom cables and equipment. The notice does not name INFOCERTO. It cannot be used to say that INFOCERTO rents a particular pole or follows a particular street. It does show that aerial telecom infrastructure in Torres sits within a utility-controlled inspection and contracting environment.

That matters in three ways.

First, pole exposure can concentrate failures. A tree can take down electricity and communications together. A vehicle strike can damage several operators on one structure. Wind can harm a drop, distribution cable or power line. The July 2023 municipal incident record documents this combination in Torres: fallen poles, power loss, blocked roads and water on streets.

Second, the physical restoration order may not belong to the internet provider. A telecom crew cannot safely work on a damaged electricity structure before the pole owner and emergency services make it safe. If a pole must be replaced, cable transfer may wait on a sequence of utility, road and telecom crews. The nearest fibre technician may be only minutes away while the legal and safety boundary is hours away.

Third, route diversity can be illusory when two cables share the same poles. Two fibres, two ports or even two upstream circuits are not physically independent if they leave the city on the same aerial line, cross the same bridge, enter the same building or depend on the same power feed. A resilient claim needs failure-domain evidence, not merely a count of logical connections.

Anatel's 2026 account of a national collection on pole-use contracts reinforces the significance of this layer. The regulator said 3,428 providers reported 4,525 contracts covering 70.2% of fixed-broadband accesses. That national figure does not reveal whether INFOCERTO has a contract, how many poles it uses or where. It shows why a company-specific pole record would materially improve the analysis.

Power creates a second demarcation. INFOCERTO's contract requires the customer to provide compatible, grounded electricity and protect internal equipment. It allows provider-supplied routers, modems, ONUs or repeaters, but the customer's premises power remains essential. A customer can therefore be offline while the street network is healthy.

The inverse is also true. A home with a UPS can keep its router and ONU lit while an unpowered cabinet, OLT, radio site, edge router or upstream handoff remains dark. No reviewed public evidence gives INFOCERTO battery runtime, generator capacity, fuel endurance, recharge arrangements or the number of powered field sites.

This is not a theoretical regional concern. During the May 2024 Rio Grande do Sul emergency, ANEEL listed Torres among the areas most affected in CEEE Equatorial territory and reported 54,000 interrupted customers across the distributor at the stated time. That distributor-wide number cannot be assigned to Torres, much less INFOCERTO. It does establish that wide-area utility disruption can reach the municipality.

The unresolved question is not simply whether INFOCERTO owns a generator. It is which elements need power, how long each can run, whether a generator can be safely connected during flooding or wind, and whether the upstream handoff remains powered at the other end. End-to-end survival is limited by the first unpowered mandatory element.

One visible neighbour at the internet edge

At 08:00 UTC on 16 July 2026, RIPEstat's routing-status observation showed AS270246 originating one IPv4 prefix, 45.191.36.0/22. It covered 1,024 addresses and was visible to 325 of 326 IPv4 RIS peers. The announced-prefix record observed that /22 continuously from 1 July through the available endpoint at 08:00 UTC on 16 July.

This is strong evidence of normal-state IPv4 operation. It is not evidence that every INFOCERTO customer was online, that traffic was uncongested or that the route survived any particular failure.

The same routing-status observation found one neighbour. RIPEstat's AS-neighbour result identifies AS52600, Digitotal Networks, as the one observed left-side neighbour. The more granular BGP-state observation collected 380 paths, and all 380 ended with AS52600 immediately before origin AS270246.

The wording must stay exact: one publicly observed logical neighbour. It would be wrong to turn that into "one fibre" or "one circuit". INFOCERTO could have two links to the same upstream ASN. Those links could terminate in different places or in the same place. There could be a backup that is not active, not visible to the collectors or not configured to announce the prefix under normal conditions. Conversely, two nominal circuits could share one conduit or pole route and fail together.

Public routing therefore identifies the external concentration point without revealing its physical severity. If AS52600 disappears from INFOCERTO's edge and no other route becomes active, the /22 loses its observed path to the wider internet. But BGP does not reveal whether the trigger would be a router failure, power loss, local transport cut, upstream policy error, common facility failure or a long-haul break.

The IPv6 evidence is weaker. Registro.br allocates INFOCERTO a /32, and INFOCERTO's PeeringDB record, last updated in July 2022, says IPv6 is supported. Yet RIPEstat observed zero originated IPv6 prefixes and zero of 321 IPv6 RIS peers seeing an INFOCERTO route at the publication timestamp. The allocation is real; public operation was not observed. It may be an unused resource, an internal deployment, a stale declaration or a route outside the observation. None of those possibilities can be chosen from the record.

The IPv4 route also had RPKI status unknown, with no validating ROA found. As the RPKI community's technical guidance explains, unknown or NotFound is not the same as invalid. It means the announcement lacks a covering route-origin authorisation in the validation result. This is a routing-security gap, not evidence of an outage or an unauthorised physical network.

Finally, the 1,024 IPv4 addresses do not measure customers. INFOCERTO's contract expressly permits NAT or CGNAT, under which several users may share a public address. NIC.br's CGNAT explanation describes that sharing directly. Infrastructure addresses, fixed-IP customers and dynamically assigned users can consume the block in different ways. The /22 establishes independent number resources, not subscriber scale or bandwidth.

The upstream may be diverse; the handoff may not be

AS52600 is not a dead end. RIPEstat's routing status for Digitotal showed broad IPv4 and IPv6 visibility and 16 observed neighbours. Its neighbour data identifies AS266220 and AS28283 as strong left-side connections. Digitotal's PeeringDB record, last updated in July 2023, lists operational 10 Gbps ports at IX.br Porto Alegre and IX.br Sao Paulo and a broad 20-50 Gbps traffic band.

This wider connectivity is relevant because INFOCERTO's visible route reaches the internet through AS52600. It would be irrelevant to assign Digitotal's ports and traffic band to INFOCERTO. They belong to the upstream. There is no public evidence showing that INFOCERTO buys a particular port rate, reaches both exchange cities, has a reserved share of any link or can fail between AS52600 paths.

The distinction can be expressed as a chain:

Customer access -> INFOCERTO aggregation -> INFOCERTO edge -> AS52600 handoff -> AS52600 wider network -> exchanges, peers and transit.

Redundancy later in the chain cannot repair a break earlier in it. If AS52600 has two upstreams but INFOCERTO has one physical path into AS52600, the first handoff remains a single failure domain. If INFOCERTO has two circuits into AS52600 but both share one pole line, the pole line remains a single failure domain. If the circuits are physically separate but terminate on one unprotected router or power feed, the equipment or power remains a single failure domain.

The reverse caution also matters. One visible ASN neighbour does not prove that INFOCERTO has designed badly. Multiple circuits to the same upstream can be a sensible arrangement, particularly if they use separate routes, facilities and power. A dormant second carrier may only appear during failover. Public collectors cannot resolve these possibilities.

What would settle the issue is modest compared with publishing a detailed security-sensitive map. INFOCERTO could disclose, in sanitised form, the number of active external circuits, whether they use separate physical approaches, whether a second provider can originate the prefix, whether edge equipment and handoffs have independent power, and the date of the last successful failover exercise. None requires exposing customer addresses or exact cable coordinates.

The present conclusion is narrower: the public internet edge is operational, but all observed routes share AS52600 as the immediate external boundary. The physical distance and independence of that boundary remain undisclosed.

Support availability is not the same as repair capacity

INFOCERTO's local-support proposition is credible at the contact layer. Its contact page gives weekday and Saturday shop hours and describes an internet-provider WhatsApp on-call channel available 24 hours every day. The homepage speaks of a specialised team. Its maintenance page describes computer and peripheral repair capability.

These facts matter. A customer has a local address, telephone numbers, email and an after-hours messaging route. A provider that also repairs equipment may diagnose the blurred boundary between a Wi-Fi problem, failed power supply, router fault, ONU issue and outside-plant failure more effectively than a remote-only seller.

But four clocks begin when an outage is reported:

1. Contact time: How long before a message is received?
2. Diagnosis time: Can support distinguish one-premises failure from a shared optical or upstream problem?
3. Dispatch time: When can a suitably skilled person reach the relevant place?
4. Restoration time: Are access, permission, weather, equipment and parts available?

A 24-hour channel speaks most directly to the first clock. It says little about the other three.

Public labour evidence is thin. INFOCERTO's LinkedIn company page self-reports a company size of two to ten employees. That broad band may be stale, and it does not distinguish owners, retail staff, IT support, network staff, installers or contractors. One public professional profile associated with INFOCERTO lists Intelbras EPON training from 2022. That is a useful indication that relevant optical-access knowledge has existed within the company's public orbit. One self-maintained profile is not a crew roster, a skills audit or proof of current employment.

The best repair evidence is historical and unusually specific. In a November 2017 Intelbras forum post, an INFOCERTO-named account described complaints of slow and unstable service. The operator said it tested fibre, connectors and ONUs before isolating the problem to a router type, then replaced 56 customer routers in one week and reported that the problem ended.

The post should not be romanticised. The account identity is not independently authenticated, the episode is almost nine years old, and the equipment mix may have changed entirely. It cannot establish current vendors, staffing, stock or response time.

It does, however, reveal a useful operational pattern: test the optical path and customer equipment, isolate the common failing component, mobilise replacements, and close the fault at the premises layer. It is evidence that resilience sometimes depends on having dozens of mundane devices available, not just a spare core router.

The present spare question is much wider. A fibre provider may need compatible ONUs, routers, power supplies, SFPs, splitters, pigtails, closures, connectors, drop cable, feeder cable, poles or pole hardware, batteries and generator parts. Radio service adds subscriber units, sector equipment, mounts, injectors and backhaul components. Possessing "spares" is not enough if the correct revision, connector, wavelength, configuration or mounting part is absent.

No public source gives INFOCERTO's current stock, storage location, supplier lead time or minimum reserve. Nor does it say whether the same small group handles broadband, computer repair, telephony, automation, cameras and access control. That service breadth can be an advantage in customer diagnosis. During a regional storm, it can also create competing demands for the same people and vehicles.

The resilience test is therefore concurrency, not a single easy job. One technician can resolve one nearby drop fault quickly. Ten scattered faults, a feeder cut and an upstream alarm require triage, communications, safe access, optical testing, splicing, customer visits and carrier escalation at the same time. The public evidence does not establish how many such jobs INFOCERTO can run in parallel.

Installed capacity is not failure-time usable capacity

INFOCERTO's public numbers belong to different states and should not be added together.

State	Public evidence	Defensible meaning
Marketed	Fibre plans from R$109.90; fixed telephony and technology services	What the company offers, without address-level availability or a current public speed table
Reported sold service	373 May accesses in Torres, including 315 fibre and 58 radio	Dated provider-reported accesses, not unique customers or ports today
Allocated	IPv4 /22 and IPv6 /32	Number resources assigned to the legal entity
Operational	One IPv4 /22 broadly visible at 08:00 UTC on 16 July	A live public route in normal conditions
Installed	Fibre and radio plant must exist to support reported service	Quantity, route, ownership, power and spare condition are undisclosed
Failure-time usable	No public figure	Capacity that remains after a specified cut, power loss, edge failure or upstream loss cannot be calculated

The difference is easiest to see at the customer speed. A 400 Mbps fibre row is a nominal access rate. It is not 400 Mbps of dedicated upstream capacity. It says nothing about split ratio, contention, busy-hour utilisation or how much traffic an alternate circuit can carry. Summing retail rates would produce a theoretical number with no operational meaning.

The same caution applies to INFOCERTO's older PeeringDB self-report of a 1-5 Gbps traffic band. The record does not identify a port, commit, average, peak or current date. It was last updated in 2022. It may be directionally useful as historical operator-reported scale, but it cannot be used to calculate current headroom.

Failure-time capacity has to be tied to a fault. After one customer drop breaks, almost all network capacity may remain usable. After a splitter branch fails, one group may be offline. After an OLT or feeder failure, a larger segment may disappear. After an edge or handoff failure, every access can remain optically lit while external internet reachability falls to zero. After a power loss, survival depends on batteries and generators at every required site.

This is why installed redundancy can disappoint. A second transit circuit with limited public evidence capacity may keep messaging alive but not carry the busy hour. A generator without fuel or a safe connection point has no failure-time value. Spare fibre without a trained splicer and access permission is inventory, not restored service. A second upstream that shares the first route does not survive a common cut.

The correct public conclusion is not that INFOCERTO lacks capacity. The May access file and current route prove normal operation. The conclusion is that no defensible figure exists for capacity after a defined physical or electrical failure.

A layered outage does not respect company boundaries

Return to the Guarita scenario. The customer reports optical loss after wind and rain. A disciplined response works through layers.

Layer one: customer power and equipment

Support confirms whether the ONU and router have power, whether the optical alarm is present, and whether another local device can connect. INFOCERTO's contract makes the customer responsible for suitable grounded internal electricity and equipment protection. A failed power supply or router can resemble a network outage to the user.

Layer two: drop and distribution

If optical signal is absent, the fault may lie in the drop, connector, closure, splitter branch or distribution cable. A single-premises problem requires different equipment and time from a shared branch failure. The 2017 forum episode is relevant here because the reported diagnosis moved across fibre, connector, ONU and router before identifying the common CPE fault.

Layer three: feeder or radio aggregation

Several customers failing together may indicate a feeder, OLT port, powered cabinet, radio site or backhaul issue. The Anatel records show both fibre and radio access, so a complete response capability must cover two physical failure families. The public record does not identify how many aggregation points exist or whether any have alternate feeds.

Layer four: local edge

If local access remains synchronised but the internet is unreachable, the failure may sit at routing, transport or edge power. The /22 can disappear globally even while customer fibres remain physically intact. Conversely, the route can remain globally visible while a local branch is dark.

Layer five: AS52600 handoff

All observed paths cross AS52600 immediately before INFOCERTO. A transport cut, handoff-port failure, edge configuration fault or power loss at either end could break that boundary. Wider AS52600 diversity only helps if the INFOCERTO-to-AS52600 link remains usable.

Layer six: outside owners and access

A fallen electricity pole may require CEEE Equatorial action before telecom work. A blocked road may delay a vehicle. A damaged bridge or restricted area may change the approach. A landlord may control entry to a rooftop or equipment room. An upstream carrier may control a remote handoff. The internet provider can own the customer relationship without controlling each restoration step.

Layer seven: people and parts

The crew needs the correct location, optical readings, safe working conditions and compatible parts. During a broad storm, the nearest person may already be repairing another fault. A replacement ONU does not solve a feeder cut; a spool of drop cable does not solve a failed edge power system.

The customer sees one outage. Operationally, it may be a queue of dependencies. Restoration time is governed by the slowest unresolved layer, not by the 2.7-kilometre road distance.

Who bears the impact

The Anatel customer-type rows support a cautious impact picture. Individual-person accesses mean homes or other personal subscriptions can be affected. Legal-person accesses mean organisations can be affected. The records do not identify any customer, so no school, hospital, hotel, shop or public service should be named as an INFOCERTO user.

The company's own offer shows the kinds of dependency that may exist. A household can lose work, study, entertainment and communication. A business can lose cloud applications, card authorisation, remote support or customer contact. Where fixed telephony or cloud PBX uses the same failed path, voice can be affected. Where cameras or access control rely on remote connectivity, off-site monitoring and administration can be affected. Where commercial automation depends on online services, sales and inventory processes can slow.

These impacts are conditional, not cumulative claims about every access. Some customer systems can continue locally. Mobile networks may provide temporary alternatives. A business may hold another provider or a cellular backup. INFOCERTO may offer protected arrangements that are not public. None can be assumed.

The regional pattern also changes with season. Torres called summer its busiest season while planning infrastructure and urban services for visitors. The report provides no telecom load figure, so it cannot support a peak-traffic estimate. It does identify a period when more occupied premises, hospitality activity and public events may increase the cost of an outage and the number of simultaneous support demands.

A small provider's local advantage is proximity and contextual knowledge. Its risk is that the same local event can affect customers, roads, poles, power, staff homes and supplier access together. Resilience is therefore partly social and logistical: who can answer, travel, enter, diagnose, splice and communicate while the town is under the same stress.

The evidence that would turn a promise into a resilience case

INFOCERTO does not need to publish sensitive cable coordinates to make its resilience more assessable. A concise, sanitised disclosure could answer the decisive questions:

1. Service boundary: Name the municipalities and broad districts currently served, separating fibre and radio.
2. Access design: State the number of independent feeder areas and whether major customer groups are single-ended or protected.
3. Pole and route exposure: Give the share of access plant that is aerial, underground or radio, plus the number of physically independent approaches to the core.
4. External connectivity: State the number of active upstream circuits, whether more than one carrier is available, and whether physical routes and termination sites are independent.
5. Power: Publish minimum tested battery and generator runtimes by site class rather than exact site.
6. Labour: Give the number of trained field responders available in and out of hours, whether contractors supplement them, and how many simultaneous incidents can be handled.
7. Spares: Identify the categories held locally and the replenishment time for critical optical, radio, routing and power components.
8. Testing: Date the last successful upstream failover, backup-power run and major restoration exercise.
9. Communication: Explain how customers receive outage status when the local access network is impaired.

These answers would also improve the economic reading of the provider. Small-city broadband economics is not just revenue per access and transit cost. It includes spare stock that may sit unused, night coverage, vehicles, optical test equipment, pole fees, backup power, contractor retainers and the cost of building a second route that customers may never notice until the first fails.

The May report of 373 accesses provides a scale context without proving the company's revenue or cost structure. At that scale, resilience investments must be selective. A full duplicate network may be uneconomic. The practical question is which small set of measures removes the largest common failures: a protected feeder, a second handoff, a stocked closure and cable kit, tested batteries, a contractor agreement, or a clear storm triage plan.

The public record cannot rank those choices because it does not reveal the current failure domains. It does show where scrutiny should begin. The one visible AS neighbour makes handoff design important. The documented pole and power environment makes route and backup design important. The broad technology offer and small reported scale make labour allocation important. The old 56-router episode makes compatible local stock important.

Resilience remains a physical claim

INFOCERTO has crossed several thresholds that distinguish an operating regional provider from a name on a page. It reports fibre and radio accesses in Torres. It holds its own ASN and number resources. Its IPv4 prefix was broadly visible on 16 July 2026. Customers have a local address and an around-the-clock messaging channel.

The next threshold is not another registry entry. It is evidence that the service can survive and recover from the failure conditions Torres actually presents.

The Guarita scenario captures the gap. The public shop is about 2.7 road kilometres from the analytical fault point. That distance could be covered quickly. But the nearest capable person may start elsewhere; the fault may sit on a utility-controlled pole; the needed closure or optical part may not be in the vehicle; the feeder may have no alternate path; the edge may lack power; and the physical AS52600 handoff may be farther away or share the same hazard.

None of those risks proves a weakness at INFOCERTO. They define the questions that remain open. BGP proves a visible logical route, not physical diversity. Address space proves independent numbering, not subscribers or bandwidth. Anatel's access rows prove reported service, not a route map. A 24-hour published contact points proves reachability of support, not the arrival time of a splicing crew.

For a small coastal provider, resilience is ultimately the ability to convert local knowledge into physical restoration: to know which strand, pole, radio, power feed or handoff failed; to reach it safely; to have the right person and part; and to keep a usable external path alive while the repair proceeds. INFOCERTO's normal-state operation is visible. Its failure-time operating surface remains largely off the public map.