Summary
- LACNIC's Registration Data Access Protocol, or RDAP, records AS27745 as active and names Telefonia Bonairiano N.V. as the registrant. That is strong evidence about network identity, not a map of physical routes.
- PeeringDB identifies the network as a regional cable, DSL and internet service provider and shows declared operational exchange connections at AMS-IX Caribbean and FL-IX. These are useful interconnection declarations, not live traffic measurements or resilience tests.
- Telbo's published mobile terms describe a wireless telecommunications network installed, maintained and operated on Bonaire. They also state that service availability can be affected by base-station range, physical obstruction, atmospheric conditions and technical faults.
- An ITU Operational Bulletin carrying a 2019 numbering-plan communication assigns fixed-service ranges 715, 717 and 718 and mobile-service ranges 770 and 777 to Telbo N.V. Those assignments do not reveal subscriber totals, coverage or current service quality.
- Official Caribbean Netherlands information says ACM and RDI jointly supervise telecommunications matters under the BES Telecommunications Act. The framework separates licensing, infrastructure and number oversight from frequency assignment and technical frequency conditions.
- None of the reviewed sources proves which submarine cable, landing station, upstream provider or physical path carries a particular Telbo service. Those questions require separate and current operational evidence.
Image note: The featured image is a realistic editorial illustration of generic island telecommunications dependencies. It is not a photograph of a Telefonia Bonairiano facility. No depicted tower, shelter, cable, landing facility, generator, building or route is claimed to be owned or operated by Telefonia Bonairiano.
What happened: six public records describe six different layers
There is no single public document that explains an island communications system from the customer handset to the rest of the internet. Instead, the public record for Telefonia Bonairiano is divided among several sources, each designed for a different purpose.
The BTW directory provides the entity link. It identifies the published company entry as Telefonia Bonairiano N.V. and associates that entry with AS27745. LACNIC's RDAP service provides the registry layer. Its structured record shows AS27745 as active, names Telefonia Bonairiano N.V. as the registrant and dates the autonomous-system registration to 12 July 2004. It also provides administrative, technical and abuse-contact information connected to Telbo NV.
PeeringDB provides a declared interconnection layer. Its public profile names Telefonia Bonairiano N.V., gives Telbo as an alias, classifies the network as a regional cable, DSL and internet service provider, and lists operational public-peering entries at AMS-IX Caribbean and FL-IX. These records help other network operators discover a possible place to exchange traffic.
Telbo's own terms describe a local physical service layer. They define a wireless telecommunications network installed, maintained and operated by Telbo on Bonaire. An ITU bulletin records assigned fixed and mobile number ranges. An official government page explains the regulatory division of responsibilities between ACM and RDI.
Each document adds a piece. The mistake would be to treat one piece as a complete proof of everything else. An ASN record is not a cable map. An exchange listing is not a packet trace. A numbering plan is not a coverage map. A service contract is not independent performance data. A regulator's description of its powers is not a finding about one operator's current compliance.
Why it matters on an island
On a large continental network, a hidden shared dependency can still be serious. On an island, the consequence can be easier to feel because the geography narrows the places where infrastructure can be built and connected. Homes, shops, schools, government offices, healthcare providers and visitors may rely on the same small group of communications systems even when they buy different services.
That does not mean every island network is fragile. It means continuity claims need to be specific. A local service may depend on a radio site, a fibre run, commercial power, cooling, a core router, an exchange connection and some form of off-island transport. Several apparent backups may still share one building entrance, one duct, one power system, one control platform or one external supplier. Conversely, systems that appear simple in public records may contain private diversity that is not published for commercial or security reasons.
The distinction matters to ordinary users because an identifier can remain correct during an outage. RDAP may continue to show AS27745 and the right registrant while a local base station has lost power. PeeringDB may continue to show an exchange connection while a separate transport segment is unavailable. A telephone range can remain assigned while a customer cannot complete a call.
Public coordination records and running service are therefore complementary, not interchangeable. The records help people identify responsibility and communicate. Physical infrastructure and operating practice determine whether the service works. A useful account of island continuity must keep those two layers connected without pretending they are the same.
The technical layer: what an ASN actually does
The internet is made from many separately operated networks. A telecommunications company, university, cloud platform or government network can manage its own routing policy and exchange reachability information with other networks. An Autonomous System Number, shortened to ASN, is the public identifier attached to such a routing domain.
Routers commonly exchange reachability information using the Border Gateway Protocol, or BGP. BGP lets one network tell neighbouring networks which blocks of internet addresses can be reached through it. The neighbours then apply technical and commercial policies to select paths. A path can change because of maintenance, congestion, a new connection, a failure or a policy decision.
AS27745 gives other operators a stable number for the Telefonia Bonairiano routing domain recorded by LACNIC. That is valuable. Without unique numbers and accurate records, it would be harder to distinguish routing announcements, contact the responsible organisation or investigate a problem.
The number does not contain the network's physical design. It does not list towers, radios, street cabinets, fibre routes, cable systems, landing stations, data rooms, power feeds or generators. It does not show whether two paths share the same duct. It does not say how much spare capacity exists after a failure. It does not identify the route taken by one customer's traffic at a given moment.
The word autonomous can also mislead non-specialists. It does not mean that the network is self-sufficient or politically sovereign. An autonomous system can buy transit, use shared exchange infrastructure, lease capacity, occupy another party's facility and depend on local utilities. The autonomy is about presenting a routing policy, not owning every component beneath it.
AS27745 should therefore be read as an identity at the routing layer. It answers who is recorded for this autonomous system. It does not answer how every Telbo service is delivered or how that delivery behaves when equipment, power or transport fails.
The registry is a ledger, not a sovereign map
Internet number registries perform a narrow but critical coordination function. ASNs must remain unique enough for routing systems to distinguish networks. Registration records need accurate holders, contacts and event histories. Changes must be controlled so that unrelated parties cannot simply claim the same resource.
LACNIC's RDAP record performs that ledger function for AS27745. It shows an active record, a start and end value of 27745, the registrant name, relevant contacts and recorded events. During an incident, this information can help another operator identify the party to contact. During due diligence, it can help a customer or journalist avoid confusing similarly named organisations.
A ledger is strongest when its claims remain precise. It records the recognised identity and history of a resource. It does not create the physical network and does not certify its condition. The route is real because routers exchange and accept information. The radio service is real because equipment transmits signals. The customer connection is real because the access system carries traffic. The registry describes the identifier used within that operating reality.
This is why registry accuracy and operational continuity are separate responsibilities. An incorrect registrant or stale contact is a registry problem. A missing BGP announcement is a routing problem. A failed radio unit is an access-network problem. A damaged off-island link is a transport problem. A generator that does not start is a power-continuity problem.
Calling the registry a ledger does not diminish it. Accurate ledgers are essential. It prevents the record from being treated as a sovereign map that supposedly proves where traffic goes or what infrastructure an organisation owns. The public evidence supports the statement that Telefonia Bonairiano N.V. is the registrant of AS27745. It does not support a claim that the company owns every circuit involved in traffic associated with that ASN.
What PeeringDB adds, and what it does not
PeeringDB is a directory used by networks, internet exchanges and facilities to publish information about interconnection. An internet exchange is a shared environment where networks can connect and pass traffic directly. Direct exchange can reduce path length, lower some transit costs - fees for having another network carry traffic onward - and give operators more control over how traffic moves.
The PeeringDB profile for AS27745 identifies Telefonia Bonairiano N.V., uses Telbo as an alias, classifies the network as a cable, DSL and internet service provider, and marks its scope as regional. It lists operational public-peering entries at AMS-IX Caribbean and FL-IX. Those facts make the network's declared interconnection surface more visible.
The word declared matters. Participating networks maintain PeeringDB profiles for operational usefulness. The directory is not a continuous independent measurement of BGP paths or packet flows. A profile can say that a connection exists without showing how much traffic it carries, which prefixes use it, whether it is available at this instant or which physical systems it shares with another connection.
An exchange name also does not establish a complete route from Bonaire to a destination. Traffic may cross local access systems, aggregation equipment, transport services and other networks before or after an exchange. The public profile does not identify which submarine cable, landing facility or upstream transport supports a listed connection. It does not prove that AMS-IX Caribbean and FL-IX provide failure-independent paths for a particular customer.
The displayed zero-prefix fields require similar caution. A directory field showing zero must not be converted into a claim that AS27745 announces no routes. Establishing live route origination requires current routing observations from suitable collectors or network operators, taken at a stated time.
The responsible conclusion is narrow: PeeringDB shows that AS27745 declares operational public-peering entries at those exchanges. Whether a particular application benefits from those connections requires fresh evidence about live routing, capacity and shared physical risk.
Declared connections are options, not automatic resilience
More than one declared interconnection can create more options. It can allow a network to exchange traffic in different places, work with different peers or change policy when conditions change. Options can improve continuity, but the count of options alone is not proof of resilience.
Two logical connections can share the same physical transport. They may enter a building through the same conduit, use the same power system, depend on one router or cross the same coastal segment. A single failure can then affect what appeared to be separate paths. Engineers call this shared risk: apparently different services still have a common point whose loss can remove both.
Capacity creates another distinction. A backup path may be technically available yet too small to carry normal demand. During a fault, the service may remain reachable while becoming slow or unreliable. A connection can also be useful for some destinations but not others, depending on routing policy and the networks present at the exchange.
Timing matters too. BGP does not instantly guarantee an ideal replacement path. Routers need to detect a failure, withdraw or update information and choose alternatives. Applications may time out or active sessions may break during that process. An operator may deliberately prefer stability over rapid switching in some situations.
To assess resilience, a customer would need more than directory rows. Useful evidence could include current route observations, physical route diagrams under confidentiality, identified shared-risk groups, normal and failure-state capacity, maintenance procedures and test results. The evidence should be specific to the purchased service, because a provider can have several network products with different dependencies.
Nothing in the reviewed sources establishes that Telefonia Bonairiano lacks such arrangements. The point is that the public records do not prove them. A declared connection is evidence of a declared connection. Resilience is a conclusion that needs a broader and more current evidence set.
The local physical layer begins with a wireless network
Telbo's published mobile terms identify the company as Telefonia Bonairiano N.V. in Kralendijk, Bonaire. The terms define Telbo's network as a wireless telecommunications network installed, maintained and operated by the company on Bonaire. They say the service can carry traffic to access points on Telbo's network or to other telecommunications infrastructure.
That wording connects the public routing identity to a more tangible local service layer without providing a full engineering map. Wireless access depends on radio equipment, antennas, sites, backhaul, power and the environment between a device and a base station. The terms themselves acknowledge several constraints: base-station range, physical obstruction, atmospheric conditions and technical faults can affect availability.
For a non-specialist, a base station is the fixed radio site that communicates with mobile or wireless devices in its area. Range depends on radio design and geography. Physical obstructions such as buildings or terrain can weaken or block a signal. Atmospheric conditions can affect some radio links. Technical faults can occur in the radio, power, transport, control or supporting systems.
These statements are useful because they place service in the physical world. They prevent an analysis from assuming that an ASN or telephone number reaches customers by itself. They also show why local continuity cannot be inferred from off-island interconnection declarations alone. A healthy exchange connection cannot restore a customer whose local radio site has no power or whose access path is obstructed.
The terms are operator statements, not independent performance measurements. They do not give current coverage, outage rates, repair times, present-day equipment inventory or disaster-recovery results. The correct use is to describe the nature of the local network and the kinds of dependency Telbo itself identifies, while leaving performance conclusions to current evidence.
A simple journey from a phone to the wider internet
It helps to follow a hypothetical connection without pretending to know Telbo's unpublished topology. A person on Bonaire opens an application on a mobile or wireless device. The device first needs a usable radio link to local access equipment. That local site needs power and functioning radio hardware.
Traffic then needs a path from the access site into the operator's wider network. That may involve fibre, microwave, switches, routers or other transport, but the reviewed sources do not identify the exact combination for a particular service. The network must direct the traffic toward the appropriate destination, possibly through another telecommunications infrastructure provider or an interconnection point.
If the destination is outside Bonaire, some form of off-island transport is necessary. Geography makes that unavoidable as a general fact, but the source set does not identify which cable, landing station, carrier or route Telbo uses. It would be misleading to attach a named cable to AS27745 without authoritative evidence.
At each step, identity and delivery play different roles. The telephone number helps calls reach the intended service. The IP address identifies an endpoint in internet communication. AS27745 identifies a routing domain. Exchange declarations describe possible interconnection locations. None supplies electricity to a radio site or repairs a damaged transport segment.
This layered journey explains why an outage can have several causes that look identical to a user. The application may fail because the local radio path is unavailable, an internal transport link is down, a route has changed, an external provider has a problem or the destination itself is unavailable. Good incident reporting identifies the failed layer instead of treating the ASN as the cause of every symptom.
Telephone-number assignments add another identity layer
An ITU Operational Bulletin carries a 2019 numbering-plan communication for Bonaire that assigns several number ranges to Telbo N.V. The record lists fixed-service ranges beginning 715, 717 and 718, and mobile-service ranges beginning 770 and 777.
Telephone numbers and ASNs are both coordination resources, but they solve different problems. A telephone number helps a communications system reach a subscriber or service. An ASN identifies a network's routing domain on the internet. A company can be responsible for both without the records revealing the physical path used by either service.
The numbering record is useful evidence of regulated responsibility at the stated date. It shows that Telbo had specified fixed and mobile ranges in the official plan. It does not provide a current subscriber count. It does not establish present-day coverage, market share, number portability outcomes, call quality or service availability.
The date is important. A 2019 communication should be described as a 2019 record, not silently presented as a live operational dashboard in 2026. Number plans can change, services can evolve and ranges can be reassigned or used differently. A current commercial or regulatory decision should refresh the plan with the responsible authority.
Still, the record strengthens the main analysis. Telefonia Bonairiano is not merely a name attached to an ASN. The reviewed sources connect it to a local wireless network and official fixed and mobile number ranges. That creates real continuity responsibilities. It does not remove the need for evidence about how the underlying systems are operated.
The regulatory layer divides responsibility
Official information from Rijksdienst Caribisch Nederland says that the Authority for Consumers and Markets, known as ACM, and the Authority for Digital Infrastructure, known as RDI, jointly supervise telecommunications matters in the Caribbean Netherlands under the BES Telecommunications Act.
The page says ACM supervises compliance with licensing regulations by telecommunications companies. It also supervises the construction, maintenance and removal of telecommunications infrastructure and the use of numbers. Responsibility for assigning frequencies and supervising the technical conditions attached to frequency use lies with the radio authority described on the page.
This division matters because telecommunications is not one undifferentiated activity. Numbers, frequencies, physical infrastructure and licensing require different expertise and legal powers. A user may experience one failed call, but identifying the responsible layer still requires evidence about the radio conditions, local infrastructure and network operation involved.
The official page describes the framework. It does not state that Telbo complied or failed to comply in a particular case. It does not certify AS27745, measure coverage or validate route diversity. Using the page to make such a claim would turn a description of jurisdiction into an unsupported verdict.
For accountability, the framework helps identify where questions should go. A number-use issue is not necessarily the same as a frequency issue. A licensing question is not necessarily a BGP incident. A construction or maintenance obligation may matter even when the registry record remains correct.
The practical lesson is that continuity depends on both engineering and clear responsibility. During a failure, knowing who maintains the radio site, who provides transport, who controls the routing policy and which authority oversees the relevant obligation can shorten confusion. A broad claim that the regulator supervises telecoms is less useful than a precise map of the problem and responsible party.
Physical continuity depends on power, equipment and access
Every operating network eventually depends on physical systems. A radio site needs electricity. Routers and switches produce heat and need a suitable environment. Fibre, microwave and copper links need intact paths and functioning endpoints. Staff or contractors need access to diagnose and repair faults.
The featured image makes these generic dependencies visible by showing a fictional coastal telecom site with radio equipment, an equipment shelter, cooling, power, a standby generator and conduits. It is an explanatory illustration, not evidence of Telbo's facilities. The source set does not establish that Telefonia Bonairiano owns or uses any asset depicted in the image.
Power continuity is more than having a generator. Batteries may bridge the interval between utility loss and generator start. A generator needs fuel, maintenance, controls and a safe connection to the load. A shared switchboard can affect both utility and backup power. The useful questions are what load is protected, for how long, under which failure and when the arrangement was last tested.
Equipment continuity is more than owning spare hardware. A spare must be compatible, configured and reachable. Some failures affect software or control systems shared by both active and backup equipment. Cooling and ventilation can become limiting even while power remains available.
The public terms acknowledge that physical obstruction, atmospheric conditions and technical faults can affect radio availability. That is a useful starting point. A complete continuity case would add service-specific design, maintenance and test records.
Off-island transport is the largest unanswered public question
An island network that reaches services elsewhere needs off-island connectivity. The general requirement is obvious. The specific implementation is not. The reviewed sources do not identify a cable system, landing station, satellite service, transport provider or physical route used by Telefonia Bonairiano.
PeeringDB's exchange entries cannot fill that gap. They show declared interconnection at named exchanges. They do not show the transport chain between Bonaire and those exchanges. A packet reaching an exchange may cross several facilities and services controlled by different organisations.
This boundary is important because named infrastructure can create a false impression of certainty. If an article guesses a submarine cable from geography, readers may assume Telefonia Bonairiano owns it, lands on it or uses it for all traffic. None of those claims follows from AS27745, the exchange profile, the operator terms, the numbering plan or the regulatory page.
It is also possible for a provider to use leased capacity rather than own a physical asset. Leasing does not make the service unreal or automatically less resilient. The continuity questions are contractual and operational: which party controls restoration, what capacity is committed, what alternate paths exist, which risks are shared and how performance is tested.
An authoritative assessment could use carrier contracts, network diagrams, landing-station records, route observations and controlled failover evidence. Some of that information may properly remain confidential. A public summary could still state the number of failure-independent paths, the classes of shared risk and the date of the last test without revealing sensitive details.
Until such evidence is available, the honest conclusion is simple. The public record identifies an island network and declared exchanges. It does not map every route off Bonaire.
Running systems outrank labels
Infrastructure reporting often gives too much weight to labels because labels are easy to find. Active appears in RDAP. Operational appears in PeeringDB. Fixed and mobile appear in a numbering plan. Wireless network appears in service terms. Each label has meaning inside the system that produced it.
The running system provides a different kind of evidence. Are expected routes visible from suitable viewpoints? Can customers reach the service? Does a backup path carry the required load? Does the radio network remain available under the stated conditions? Can staff restore a failed component within the promised time?
These questions do not make records irrelevant. They test the operating reality that records are meant to support. An accurate ASN record helps coordination when a route is wrong. A current contact can shorten an incident. An exchange declaration can help another operator find an interconnection option. A numbering plan keeps numbers unique and reachable.
The principle is to avoid letting an administrative label override observed reality. A connection marked operational in a directory should not be cited as proof of current packet delivery when fresh measurement shows otherwise. Equally, one failed customer session should not be used to declare an entire autonomous system offline without wider evidence.
What failure evidence would look like
Resilience is the ability to continue or recover when something goes wrong. It cannot be proved by one number or one diagram. Useful evidence connects a defined failure to an observed result.
For wireless access, a review could examine coverage design, site power, radio redundancy, backhaul options, alarm response and repair time. It could test the effect of taking one component out of service under controlled conditions. It should distinguish expected coverage limitations from equipment failures.
For routing, evidence could include time-stamped BGP observations from several viewpoints. A Route Origin Authorization, or ROA, is a signed statement used in Resource Public Key Infrastructure, known as RPKI, to indicate which ASN is authorised to originate a block of addresses. RPKI status can improve route-origin validation, but the reviewed sources do not establish the status of every prefix related to Telefonia Bonairiano.
For interconnection, a review could record which peers and exchanges carry traffic, the available capacity during normal operation and the remaining capacity after a connection is removed. It should identify shared transport and facility risks.
For off-island continuity, evidence could describe independent paths without disclosing sensitive route details. It could state whether paths use different landing points, providers, conduits or technologies, and whether a controlled test moved traffic as intended.
For incident response, a useful report would identify detection time, affected services, mitigation, restoration, root cause and corrective action. A restored service is not always a repaired system; temporary routing or equipment changes may remain in place.
None of these tests is supplied by the six reviewed public records. They are examples of the additional evidence needed to turn a reasonable design claim into an accountable operational conclusion.
Who is affected
Residents are affected because voice and internet access support family contact, banking, education, healthcare and government services. They need clear information about affected services and expected restoration, not only a statement that the network's registration remains active.
Small businesses are affected because a lost connection can interrupt payments, reservations, cloud applications and customer support. A business may need a backup from a genuinely different failure path rather than a second product that shares the same local or off-island dependency.
Tourism operators and visitors are affected because communications support bookings, navigation, emergency contact and card transactions. Demand can also change with visitor patterns, so continuity needs capacity as well as technical reachability.
Government and public services are affected because they may depend on communications during the same event that makes repair more difficult. Their contracts should identify priorities, escalation contacts and the evidence required after an incident.
Other networks are affected because accurate ASN and PeeringDB information makes coordination easier. When contacts, policies and exchange records are current, operators can investigate routing and interconnection problems more quickly.
Telefonia Bonairiano is affected because careful evidence boundaries prevent two opposite errors. The company should not receive unsupported credit for submarine-cable ownership, route diversity or failover performance. It should also not be blamed for lacking systems merely because the public sources do not describe them.
Regulators are affected because a failure can cross several legal and technical layers. Clear jurisdiction helps, but oversight still needs service-specific facts. Researchers and journalists are affected because directories make quick stories tempting. Accurate verbs and dated evidence produce more useful public accountability.
Questions customers can ask
Start with the purchased service. Is it fixed access, mobile service, dedicated business connectivity, voice or another product? Different products can use different equipment and recovery paths even under the same company name.
Ask about the local access path. Which site or system serves the location? What happens if that site loses commercial power? Is there backup power, how long is it designed to operate and when was it last tested under load?
Ask about backhaul, the link carrying traffic from the local access system into the wider network. Are alternate paths physically separate? Do they share a tower, building entrance, conduit, power source or transport provider?
Ask about off-island connectivity. How many failure-independent paths can support the service? What capacity remains if one is unavailable? Who controls restoration, and what evidence shows that traffic has successfully moved during a test or real event?
Ask about routing. Which prefixes and ASN are relevant to the service? Are route-origin authorisations used where appropriate? How are unexpected routing changes detected and escalated?
Ask about interconnection. Do the listed exchange connections serve this product? Are they live and adequately sized? Which dependencies are shared even when the exchange names differ?
Ask about communications. Who provides status updates, how often and through which channel? Does the report distinguish detection, mitigation, temporary restoration and permanent repair?
Ask for bounded evidence. A customer does not need sensitive network blueprints. A dated test summary, independent assurance statement or contractual description of failure-independent paths can provide confidence without publishing exploitable details.
Finally, ask who owns each action. The operator, power utility, transport carrier, equipment vendor and customer may each control a part of continuity. A written responsibility map is often more useful during an incident than a general promise of reliability.
How to read the evidence during an outage
Begin with the symptom. Record the time, location, device and service that failed. Check whether voice, messaging, local websites and external sites are affected in the same way. One failed application does not prove the access network is unavailable.
Keep the registry layer separate. RDAP may continue to return the correct AS27745 record throughout an outage. That means the public ledger remains accessible and the identity remains recorded. It does not prove customer traffic is moving.
Treat PeeringDB the same way. An exchange entry can remain on the page while a live session is down. The directory is useful for contacts and declared topology, not for real-time status.
Fresh routing observations can narrow the problem. If expected routes disappear from several independent viewpoints, routing becomes a stronger lead. If routes remain visible, local access, internal transport, congestion, name resolution or the destination may still be responsible. A visible route does not guarantee that every customer can send and receive traffic.
Operator telemetry can add physical detail. Radio alarms, power events, interface errors, optical levels and repair tickets can show where the service chain changed. Customers may not see this data, so status updates should identify the affected layer as clearly as operational security allows.
Restoration also needs precise language. Moving traffic to a temporary path is mitigation. Bringing service back is restoration. Removing the cause and returning to a stable intended configuration is repair. These may happen at different times.
After the event, compare what happened with the continuity claim. Did the backup carry the required load? Were communications timely? Did any shared dependency defeat the intended diversity? That evidence is more informative than repeating that the ASN remained active.
How journalists and researchers should describe AS27745
Precise verbs protect readers. LACNIC records AS27745 to Telefonia Bonairiano N.V. PeeringDB lists declared operational exchange connections. Telbo's terms describe a wireless telecommunications network on Bonaire. The ITU bulletin records assigned number ranges. The government page describes regulatory responsibilities.
Registered is not the same as physically owned. Listed at an exchange is not the same as carrying all traffic there. Operational in a directory is not the same as independently measured availability. Assigned a number range is not the same as serving a stated number of customers. Supervised by a regulator is not the same as found compliant or non-compliant in a particular case.
Time should be visible. The RDAP registration dates to 2004, and the record was retrieved in 2026. The numbering communication is from 2019. Service terms are operator materials and should not be presented as a current independent audit. PeeringDB entries can change, so interconnection decisions should refresh them.
The BTW directory's relationship graph also needs caution. Observed and inferred relationships can help discovery, but they do not establish provider-customer direction, physical transport or resilience. The exact directory entity and ASN binding are the facts used here.
This language may seem cautious, but it is more useful. It separates what the records genuinely establish from what an operator, customer, regulator or independent tester would need to demonstrate next.
What the public sources still do not tell us
The sources do not list the current prefixes originated by AS27745. They do not provide multi-vantage BGP paths or a complete route-origin security assessment. Those questions require time-stamped routing data.
They do not disclose the topology of Telbo's local radio and transport network. They do not identify the location, power arrangement, coverage or backhaul of individual sites. The operator terms describe the type of network and possible availability constraints, not a present-day asset inventory.
They do not identify a submarine cable, landing station, satellite service or off-island carrier used by Telefonia Bonairiano. They do not show route diversity, shared-risk groups, spare capacity, failover speed or disaster-recovery results.
They do not show how much traffic passes through AMS-IX Caribbean or FL-IX. They do not establish that a particular customer path uses either exchange. They do not prove that the exchange connections are physically independent.
They do not provide current subscriber numbers, market share, service-wide availability, outage frequency or repair-time distributions. The 2019 numbering assignments should not be used as a proxy for those figures.
They do not contain a regulatory finding about Telefonia Bonairiano's present compliance. The official oversight page explains responsibilities, not case results.
They do not settle ownership of every tower, fibre strand, route, generator, building or exchange port. Telecommunications services commonly combine owned and leased components. The relevant continuity questions are who controls each dependency, what obligations apply and what happens during failure.
These gaps are not defects in every source. Each source was created for a narrower job. The gaps mark the point where identity evidence ends and operational evidence must begin.
What to watch next
Watch the RDAP record for identity and contact changes. Accurate registrant and contact data help coordination, but a change should be interpreted as a registry event, not automatically as a physical network change.
Watch the PeeringDB profile for updated exchange entries. A new or removed entry can show a declared interconnection change. Current route observations are still needed to understand traffic effects.
Watch for public or customer-facing continuity evidence. A bounded summary could describe failure-independent local and off-island paths, remaining capacity after a fault and the date of the latest controlled test without exposing sensitive details.
Watch number-plan updates from the responsible authority. The 2019 ranges establish a dated allocation record. Current decisions need current confirmation.
Watch how incidents are explained. Useful reports distinguish local access, internal transport, routing, external provider and destination problems. They state the time, affected services, mitigation, restoration and corrective action.
Watch the status words. Registered, declared, designed, installed, active, operational, available and tested are not interchangeable. Clear wording prevents an administrative record from becoming an unsupported resilience claim.
Watch customer-specific contracts. A provider's network can support products with different priorities and backups. The relevant question is not only what the company operates in general, but what continuity the purchased service includes.
The reality behind AS27745
AS27745 is a meaningful public identifier. LACNIC's ledger names Telefonia Bonairiano N.V. as its registrant. PeeringDB shows a regional network profile with declared exchange connections. Telbo's own terms describe a wireless network on Bonaire and acknowledge physical and technical conditions that can affect service. The ITU bulletin records assigned fixed and mobile number ranges, while official government information explains the oversight framework.
Those records make the network easier to identify and discuss. They do not make the company, the regulator or the registry sovereign over every physical fact. They do not reveal every path or turn a directory entry into a resilience certificate.
Operational continuity lives in the running system. Radio links must reach users. Local transport must carry traffic. Power and equipment must remain available or recover. Off-island connectivity must have enough working capacity. Routes must be accepted. Staff and suppliers must detect, communicate and repair faults.
This conclusion is neither praise nor accusation. Telefonia Bonairiano may have additional private evidence and resilience arrangements that the reviewed public records do not show. It may also have dependencies that require continued work. The article does not decide between those possibilities without evidence.
For a non-specialist, the final distinction is straightforward. Use AS27745 to identify the public routing domain. Use PeeringDB to understand declared interconnection. Use the operator terms and numbering plan to understand the service context. Use current measurements, physical-path evidence, capacity data and controlled failure tests to judge continuity.
The ledger should remain accurate because networks need a dependable record. The running code and physical systems should remain the final evidence of whether service works. On an island, confusing one for the other can hide the exact dependency that matters most.