Your Tech Electronics and Your Shop Enterprise sells hosted capacity that still depends on racks, transit and repair windows

Summary

• Your Tech Electronics and Your Shop Enterprise, also identified publicly as SMJ3 Corporation, markets residential fibre in Koronadal City, Banga and Tantangan. Its current storefront shows 50, 80 and 100 Mbps plans, but no public VPS, bare-metal, colocation, managed-server, backup or cloud-compute offer.
• APNIC records tie the enterprise to AS154262, a portable IPv4 /23 and an IPv6 /48. On 10 July 2026, routing collectors saw 512 IPv4 addresses announced in three overlapping routes with route-origin authorisation, while no IPv6 route was visible.
• The observable external route boundary is narrow. RIPEstat and bgp.tools identify Aioni Digital and Data Solutions, AS153174, as the one visible neighbour and upstream. That does not prove there is only one physical circuit, but no independent second transit network is publicly demonstrated.
• PeeringDB lists AS154262 at VITRO Makati 2 and in a self-reported 5-10 Gbps traffic band. It lists no public exchange connection for the network. A facility listing supports presence, not ownership of the building, a quantified rack allocation, reserved power, dual entrances or a tested second-site recovery plan.
• The retail site runs on Shopify and says submitted information may be processed in other countries. The local access network and the commerce account therefore have different locality boundaries: packets may enter AS154262 in South Cotabato while order, contact or payment-related data depends on an external commerce platform.
• Customers and counterparties need contract-level answers before treating the public footprint as resilient capacity: where equipment is installed, who owns each segment, how many failure-independent routes exist, what support is available outside shop hours, how spares are held and how service or data can be moved after a facility, upstream or supplier failure.

A trading name, a shop and a routed network

The name sounds like two businesses joined together because, in public, that is close to what it is. The company's about page identifies SMJ3 Corporation as doing business under the name Your Tech Electronics and Your Shop Enterprises and describes it as an Internet service provider in South Cotabato. The same site is an online shop. Its catalogue has carried residential Internet plans beside a commercial ice machine, a smart cutting machine and a mobile television. The footer gives a physical shop on Zulueta Street in Koronadal City and opening hours of 8am to 6pm from Monday to Saturday.

Those retail signals are useful identity evidence. The contact page names Koronadal City, Banga and Tantangan as service locations. The physical address and telephone contact recur across the storefront. APNIC's AS154262 registration names Your Tech Electronics and Your Shop Enterprise, uses the network name SMJ3CORPORATION-AS-AP, records the Philippines as the country and links the resource to organisation ORG-YTEA1-AP. Its organisation record gives the same Zulueta Street locality. PeeringDB's network entry uses Your Tech Electronics and Your Shop Enterprise as the organisation, SMJ3 Corporation as the alternate name and smj3corp.com as the website.

Together, these records support a careful identity alignment: the shop, the SMJ3 corporate name and AS154262 are publicly presented as parts of the same operating business. They do not support a more expansive conclusion that every service associated with the website is delivered directly from equipment owned by the enterprise. A trading identity can sell access while leasing transport, rack space and upstream bandwidth. A commerce site can take an application while a separate platform processes the account. An autonomous-system registration can establish routing authority without revealing the balance-sheet owner of a router or fibre span.

The singular and plural forms of "Enterprise" and "Enterprises" also need restraint. APNIC and PeeringDB use the singular directory name. The website uses the plural in its masthead and about page. That variation is not enough to split the public identity into separate organisations, and nothing reviewed supports doing so. The company entity here remains Your Tech Electronics and Your Shop Enterprise, aligned to AS154262, with SMJ3 Corporation treated as the disclosed alternate business name.

This matters because infrastructure analysis fails when identity clues are converted into asset claims. A shop address is not necessarily a network operations centre. A contact telephone is not proof of a staffed overnight desk. A data-centre listing is not evidence that the shop owns a data centre. A routed prefix is not a count of customers, servers or spare machines. Each clue has a proper scope. The evidence is strong enough to show an operating local access business with its own routing resources; it is not strong enough to turn that business into a fully disclosed cloud operator.

What a customer can actually buy

The company's home page advertises Wi-Fi solutions for homes and businesses and repeats the three South Cotabato service areas. The product pages are more specific and narrower. The Basic plan advertises unlimited fibre Internet for residential consumers at up to 50 Mbps for PHP1,000 a month. The Standard plan offers up to 80 Mbps for PHP1,200 a month. The Premium plan offers up to 100 Mbps for PHP1,500 a month. Each page tells the visitor to apply through the buy button and wait to be contacted.

That is current commercial evidence, but it leaves important terms unstated. The product pages do not specify installation charges, contract length, minimum speed, committed information rate, contention ratio, traffic-management policy, equipment ownership, public-address entitlement, repair target, service credit, cancellation process or what "unlimited" excludes. The Standard and Basic listings describe recurring purchases in the commerce interface, while availability indicators are inconsistent enough that a buyer still needs direct confirmation. A price in a cart is not a complete service agreement.

Nor do the pages substantiate the hosting proposition suggested by the infrastructure category. There is no visible product for a virtual machine, dedicated server, rack unit, managed operating system, object storage, backup repository, database, domain hosting or disaster-recovery seat. No public page sets out processor, memory, storage, bandwidth, address, operating-system or backup specifications. No service page identifies a customer portal for hosted workloads. No migration guide explains how an existing server image or data set would be brought in, exported or restored.

One commercial site associated with an autonomous system does not change that conclusion. IPinfo's AS154262 summary has reported one hosted domain and 512 IPv4 addresses, while classifying the network as an ISP and showing an access-network usage rhythm. A hosted-domain count is an observation about DNS and addresses, not a catalogue of compute services. The domain could be an operator service, a customer page, a router interface or another web endpoint. It does not prove that the company sells general-purpose hosting.

The defensible description is therefore more modest than the headline category. The company sells customer-facing network capacity in the form of residential Internet access. Its own website depends on a hosted commerce platform. Its autonomous system has a declared data-centre presence and Internet routes. These facts put it inside the economics of hosted and networked infrastructure, but the public record does not establish a separately purchasable cloud or server estate. Any claim that a customer can rent a machine, rack or managed workload from the company requires a current offer, contract or customer handoff that has not been published.

This negative finding is useful. Buyers often group broadband, "cloud," hosting and data-centre presence under one supplier label. The technologies can share racks and upstreams, yet their obligations differ. Residential access promises a path from premises to the Internet. Colocation promises space, power, cooling and physical access. VPS promises allocated compute and storage under a virtualisation boundary. Managed hosting adds patching, monitoring and recovery obligations. A company can provide one without providing the others. Here, only the first is directly visible as a product.

AS154262 proves operation, not a server estate

The network evidence is firmer than the hosting evidence. APNIC allocated autonomous system number 154262 to the enterprise in September 2025. Its IPv4 record for 27.126.156.0/23 covers 27.126.156.0 through 27.126.157.255, a total of 512 addresses, with ALLOCATED PORTABLE status and a South Cotabato geolocation. "Portable" is a resource-policy status: the block is allocated to the holder rather than merely being a slice of an upstream's aggregate. It does not mean each address is assigned to a customer or that the block can move instantly between providers.

At 00:00 UTC on 10 July 2026, the RIPEstat routing-status response saw AS154262 from 323 of 324 full-table IPv4 peers. It reported three IPv4 announcements covering 512 unique addresses and one observed neighbouring autonomous system. The three routes were the aggregate 27.126.156.0/23 and its two component routes, 27.126.156.0/24 and 27.126.157.0/24. Counting the route rows as 1,024 addresses would be wrong because the two /24s sit inside the /23. Installed public address space remained 512 unique IPv4 addresses.

The route detail adds two useful controls. RIPEstat's validation response for the aggregate found a valid route-origin authorisation naming AS154262. Separate authorisations validate 27.126.156.0/24 and 27.126.157.0/24. The more-specific authorisations matter because the aggregate authorisation has a maximum length of /23 and would not, by itself, authorise /24 announcements. The current arrangement protects all three observed origins against a class of accidental or malicious route-origin error.

Route-origin validity is not availability. It answers whether AS154262 is authorised to originate a prefix. It does not answer whether the routers are powered, whether the backhaul is intact, whether the upstream accepts traffic, whether a customer session is provisioned or whether an application at the far end responds. A valid route can lead to a congested or unreachable service. RPKI is a useful integrity control, not a generator, battery or repair crew.

The IPv6 record shows another difference between assigned and usable capacity. APNIC's 2001:df6:25c0::/48 record assigns portable IPv6 space to the enterprise. Yet RIPEstat reported no IPv6 announcements from AS154262 on 10 July, and bgp.tools likewise showed zero originated IPv6 prefixes. A block can exist in a registry without being globally routed. Public evidence therefore supports IPv6 resource possession, not operational IPv6 service to retail customers.

The global visibility of the IPv4 routes is strong evidence that this is not merely a dormant registration. Cloudflare Radar's AS154262 overview has shown traffic measurements and an estimated user population, while IPinfo has observed responding addresses and activity across the day. These are third-party estimates and probes, not audited subscriber counts. They support current use but should not be translated into a precise number of paying connections. A household behind address sharing, a business with several users or an unused address can each distort the relationship between addresses, devices and subscribers.

The right conclusion is narrow and robust. Your Tech Electronics and Your Shop Enterprise controls a young, active routing domain with a small portable IPv4 allocation and correctly authorised origin routes. It also holds IPv6 space that was not publicly announced on the publication date. None of those facts identifies a hypervisor, a storage array, a server inventory or the amount of compute a customer could rent.

One visible upstream concentrates the route boundary

Public routing views agree on the immediate external dependency. bgp.tools' AS154262 page lists Aioni Digital and Data Solutions Inc., AS153174, as the single upstream and the single observed peer. RIPEstat's neighbour data also identifies AS153174 as the one observed neighbour. IPinfo reports the same upstream relationship. This agreement across measurement services makes the logical dependency credible.

It does not prove there is one fibre strand. Two routers can establish multiple sessions to the same upstream AS at different sites. An operator can buy protected circuits, use diverse entrances or carry traffic over separate optical systems while showing only one neighbouring AS in the global table. Private sessions and internal transport do not necessarily appear to route collectors. Conversely, several contracts can still share a conduit, facility or upstream core. Autonomous-system diversity and physical-path diversity are related, but they are not interchangeable.

What is visible is that no unrelated second transit AS is demonstrated at the AS154262 boundary. There is no public route showing automatic escape through another carrier if AS153174 stops accepting or propagating the company's prefixes. PeeringDB shows no public exchange port for AS154262. The network's listed open peering policy therefore describes willingness, not an operating exchange connection. A policy field cannot carry traffic without a port, cross-connect, session and accepted routes.

Aioni's own service page markets IP transit, colocation, managed networking, 1 Gbps and 10 Gbps services, and says it has data-centre presence and 24-hour engineering support. Its bgp.tools view shows a much broader connectivity set than AS154262, including observed upstream relationships with HGC, Vitro, KEITH.NET and GetaFIX, plus exchange connections at BBIX Manila, GetaFIX Manila, VITRO Internet Exchange and AMS-IX Manila. That broader network can give an AS154262 customer paths to many destinations after traffic enters Aioni.

But Aioni's diversity is one layer removed. If the customer-to-AS154262 access path works but the AS154262-to-Aioni handoff fails, Aioni's four upstream-facing relationships cannot be used by that customer unless another handoff exists and takes over. If Aioni has a control-plane failure affecting customer route acceptance, physical diversity inside its core may not help. Resilience must be evaluated at every boundary, not inferred from the richest network farther along the chain.

The commercial boundary is similarly opaque. No reviewed public document discloses the capacity purchased from Aioni, committed rate, burst allowance, overage terms, interface count, cross-connect owner, protection class or restoration target. PeeringDB places AS154262 in a self-reported 5-10 Gbps traffic band, but that broad band is not a port inventory and does not guarantee 5 Gbps of unused capacity. It may describe total traffic volume, a selected category or an expected range. It does not show peak utilisation, contention or headroom after a link loss.

For a residential plan advertised at 100 Mbps, the arithmetic is instructive but incomplete. Fifty customers simultaneously using 100 Mbps would consume 5 Gbps before protocol overhead; one hundred would consume 10 Gbps. Mass-market networks are not built on the assumption that every line runs at its maximum all the time. They rely on statistical multiplexing, local caching and uneven demand. The self-reported traffic band therefore cannot be divided by the retail line speed to calculate the subscriber base or guarantee.

Without peak measurements and oversubscription policy, installed line rates and usable shared capacity remain different quantities.

The immediate failure question is straightforward: if AS153174 becomes unavailable at the only publicly observed route boundary, how does AS154262 remain reachable? A convincing answer would show a second active provider, or at least geographically and electrically independent handoffs to AS153174 with tested failover. Public records show neither. The responsible assessment is not "single cable," which is unproven, but "single visible upstream AS, with physical diversity undisclosed."

A Makati facility listing is not a property deed

PeeringDB provides the most concrete facility clue. The AS154262 entry lists VITRO Makati 2 as an interconnection facility in Makati. The facility page identifies Vitro Inc. as the operator and gives 222 Nicanor Garcia Street, Barangay Bel-Air. It also lists more than one hundred networks and several Internet exchanges at the site. This is meaningful evidence that AS154262 has declared an interconnection presence in a real carrier-rich building.

The ownership boundary is clear. Vitro, not Your Tech Electronics and Your Shop Enterprise, is the facility organisation in PeeringDB. PLDT Enterprise's VITRO data-centre page describes a national portfolio with colocation, managed servers, cross-connections, business continuity and aggregated power and rack capacity. Those are portfolio-level claims by the facility group. They do not establish how many racks, cabinets, cages, kilowatts or cross-connects AS154262 has contracted in Makati.

Presence can take several forms. The enterprise could own routers in a leased rack. It could occupy part of a cabinet managed by Aioni. It could use a remote port or layer-two extension delivered to another location. PeeringDB does not distinguish those cases. It records where a network says it can interconnect, not a bill of materials. The listing is therefore stronger than a marketing map but weaker than a current colocation schedule, cross-connect order and asset inventory.

The geography creates a consequential unknown. Retail service is marketed in South Cotabato on Mindanao. The declared data-centre presence is in Makati on Luzon. Traffic between those areas needs domestic transport across facilities, terrestrial fibre and inter-island systems or another carrier service. The reviewed record does not identify the route, carrier, landing points, protection scheme or whether traffic reaches Makati before entering Aioni.

APNIC's geolocation on the IPv4 allocation points toward South Cotabato, and public probes have reached addresses in or near Koronadal, but address geolocation does not trace the physical backhaul.

This leaves two plausible infrastructure centres without a disclosed connection between them: the local access footprint around Koronadal, Banga and Tantangan, and the interconnection footprint in Makati. A break in local distribution can isolate a neighbourhood while the Makati router stays healthy. A long-haul failure can leave local optical links lit but cut off Internet reachability. A facility event in Makati can affect the routed edge even if every South Cotabato drop cable is intact. Recovery responsibilities differ in each case.

Power must also be assigned to the right owner. VITRO markets resilient facility infrastructure, and PLDT says its data-centre facilities are carrier-neutral. A customer of that building still has to contract appropriate feeds, power density and backup arrangements. Facility generators do not protect a router whose rack power chain, power supply or configuration has a single point of failure. Dual utility or generator systems do not create a second transit path. A second power feed can be defeated if both device power supplies terminate on one distribution unit.

Public facility capabilities should not be inherited as customer-specific guarantees without a service schedule.

The same rule applies to repair windows. A staffed data centre may permit remote hands, but the network operator has to authorise work, hold spares and provide accurate instructions. A facility technician can reseat a cable or replace a labelled component only if the contract allows it and the replacement exists. A failed router in Makati, a damaged access cable in Banga and a commerce-platform outage each need different people. No public material assigns those roles or publishes escalation times.

Multi-site capacity is not demonstrated. PeeringDB lists one facility for AS154262 and no exchange connection. The company site names three access service areas, not three core sites. A municipality on a sales page is not a data-centre region. There is no disclosed second rack, warm standby, replicated control system or tested route from another facility. A buyer should therefore treat VITRO Makati 2 as an identified interconnection location, not as evidence of a redundant two-site architecture.

Installed capacity and usable capacity are different numbers

The public record offers several tempting numbers: three speed tiers, 512 IPv4 addresses, a 5-10 Gbps PeeringDB traffic band and a third-party estimate of thousands of users. None measures the same thing.

The 50, 80 and 100 Mbps figures are retail access rates stated as "up to." They describe an intended maximum at some part of the service, not a minimum end-to-end transfer rate. A home connection can be constrained by Wi-Fi, an Ethernet port, the optical access segment, aggregation, the backhaul, transit, the destination network or the destination server. The pages do not define where the rate is measured. They also do not provide a minimum or typical speed, latency target or packet-loss threshold.

The 512 IPv4 addresses are routing resources. Some may serve network equipment, some may be assigned directly, some may support address sharing and some may be held unused. A provider can serve more than 512 customers through carrier-grade translation, or far fewer customers with generous public-address assignments. The block size limits certain addressing choices but does not reveal bandwidth or compute.

The 5-10 Gbps band is self-reported interconnection metadata. It may indicate total traffic rather than purchased line rate. Even if the underlying interfaces total 10 Gbps, usable capacity after a component failure can be lower. Two 10 Gbps links operated active-active do not guarantee 20 Gbps after one is lost; a surviving link may have 10 Gbps installed and less available after existing load is shifted. A single 10 Gbps interface can also be constrained by a lower committed transit rate.

The estimated user population is an inference from measurement, not a customer register. Cloudflare states that its population estimates draw on APNIC measurements. IPinfo classifies the network from observed activity. Such observations can distinguish a live access network from a quiet address holder, but they cannot establish monthly recurring revenue, household count or the number of simultaneous users. Estimates are especially uncertain for a small network, where a few shared addresses can represent many people.

Compute capacity is absent from this set entirely. A routed address can point to a server, but it does not reveal processor cores, memory, storage media, virtualisation, backup retention, spare drives or power draw. The one hosted-domain observation does not establish a sellable server. A data-centre presence can host routing equipment alone. Calling the network "hosting" without a service specification would collapse connectivity and compute into one unsupported category.

The economically relevant measure is failure-conditioned usable capacity: what can the operator deliver when one circuit, router, power chain or supplier is unavailable and demand has moved to the surviving system? Public pages do not answer. They also do not show whether new subscriptions are admitted against tested spare capacity or simply against current average use. For customers, that uncertainty appears during evening congestion or an outage, not during checkout.

Evidence that would settle the question is concrete. For access, publish peak and 95th-percentile utilisation by serving area, optical split design, aggregation headroom and measured speed distributions. For transit, disclose active interfaces, contracted capacity, provider diversity and failover tests. For any hosted product, disclose deployed and available compute, storage, power, backup and restore performance. Installed assets are the starting point; capacity that survives failure is the service.

Repair time is part of the product

The storefront makes support look local and approachable. It publishes two telephone numbers, a contact form and a walk-in address. The about page promises responsive customer support and continuous improvement. Those are positive signals for a regional provider: a customer can identify a place and a business rather than dealing only with an anonymous online brand.

The stated hours also expose a boundary. The shop advertises Monday-to-Saturday opening from 8am to 6pm. The site does not publish an overnight fault number, Sunday coverage, network-status page, severity definition, response target or restoration target. Aioni says its own engineering support operates around the clock, but an upstream's support promise is not automatically the retail customer's entitlement. The customer relationship still runs through Your Tech Electronics unless the contract says otherwise.

APNIC's incident-response record adds a caution. The registry provides an abuse mailbox for the network, yet its public remarks marked that mailbox invalid in May 2026. That does not prove customer support is unavailable; abuse handling and retail support can use different channels. It does show that one formal operational contact had failed registry validation. For a network carrying customer traffic, maintaining working incident contacts is part of operational hygiene.

Repair is a chain of diagnosis, access, materials and authority. A customer first reports loss of service. Someone must determine whether the fault is the household router, optical terminal, drop cable, access distribution, local power, backhaul, edge router, Aioni handoff or remote destination. If the fault is physical, a crew needs permission to enter the site and enough cable, connectors, optics or hardware. If it is a configuration failure, an authorised engineer needs current backups and secure access. If a supplier is responsible, the retail provider has to open and escalate the right case.

Hardware stock matters because South Cotabato and Makati are separate repair theatres. A spare customer router in the Koronadal shop does not replace a failed line card in Makati. A spare router in Makati does not repair a cut local fibre. Critical items need to be held near the likely fault or delivered within a contracted time. The electronics retail activity may give the business useful procurement experience, but a catalogue of televisions and machines is not evidence of network-grade spare holdings.

Billing failures can prolong technical failures. If an account is incorrectly suspended, a perfectly healthy route and access link will not restore the customer. If a recurring charge fails during a commerce-platform incident, the provider needs a manual reconciliation path. The public pages do not describe grace periods, dispute handling, service credits or how an application becomes an activated line. Those commercial controls belong in resilience analysis because they can make installed capacity unusable to a specific customer.

For households, the impact of a long repair window is increasingly broad. The line may carry work, education, payments, government services, entertainment and family communication. A small business using a residential plan may also depend on it for point-of-sale or cloud applications, even if the product does not promise business-grade restoration. "Up to 100 Mbps" says nothing about how many hours the service may be absent after a cable cut.

A mature support offer would publish at least fault channels, coverage hours, severity levels, target acknowledgement, target restoration, planned-maintenance notice, escalation ownership and the treatment of widespread faults. It would distinguish access repair from customer-device support and upstream incidents. The present public offer leaves those items for direct inquiry. That may be workable for a young local provider, but it transfers uncertainty to the customer.

The commerce account and the access network have different locality

The company's local identity could lead a customer to assume that all associated data stays local. The store privacy policy says otherwise. It states that the store is powered by Shopify, that Shopify hosts the commerce services, and that submitted information is shared with Shopify and other parties that may be in countries other than the customer's. It lists contact, payment, account, transaction, communication, device and usage information among the data that may be processed.

This does not mean the access network is operated from abroad. AS154262 is registered in the Philippines, its retail footprint is in South Cotabato and its declared interconnection facility is in Makati. It means that the customer relationship has at least two technical planes. The connectivity plane carries Internet packets through the local access and upstream chain. The commerce plane can collect an application, account details or transaction information through a globally provided platform. Local routing does not force local storage of commerce data.

The distinction is central to data sovereignty. A company can advertise a Philippine service and use Philippine address space while relying on a foreign-hosted software service. Conversely, data processed by a foreign platform can remain governed by Philippine obligations when it concerns Philippine customers. The National Privacy Commission's Data Privacy Act text says a controller remains accountable for personal information transferred to a third party for domestic or international processing and must use contractual or other reasonable means to provide comparable protection.

The company's policy discloses the possibility of international transfer but not the countries, data-centre regions, retention schedule for each record type or recovery location. It gives rights including access, deletion, correction and portability subject to applicable conditions. Those are privacy rights, not a technical service-migration guarantee. A customer may be able to request personal data without being able to export a router configuration, billing history in a reusable format or a hosted workload image.

Shopify dependence also creates an operational boundary. An outage of the storefront need not interrupt packets already flowing through AS154262. It can still impede new applications, account access, payments or support messages sent through the form. The reverse is also possible: the storefront may remain available through Shopify while the local access network is down. A single brand can therefore show two different availability states at once.

For a business buyer, locality questions should be service-specific. Where are subscriber identity and billing records held? Which system controls activation? Where are router configurations backed up? Are support messages copied to external services? If any hosted workload is offered, where do its primary and backup copies reside? Which subcontractors can access them? What happens to data after cancellation? The public privacy page answers the broad international-transfer point but not these operational details.

The absence of a strict domestic-storage claim is not itself a failure. Cross-border processing is common and the Philippine framework allows it under accountability requirements. The risk comes from assuming that a local network label answers every data-location question. The evidence supports local access and routing resources, plus an externally hosted commerce layer. Customers should contract for the locality that matters to their data rather than infer it from the shop address.

Migration is the recovery mechanism customers rarely see

Resilience is often discussed as preventing failure, but migration determines how a customer escapes failure that persists. For Internet access, migration can mean ordering a second provider, moving critical devices to mobile service, changing public addresses, rebuilding firewall rules and updating DNS. For hosting, it can mean exporting virtual disks, databases, keys and backups to another environment. The company's public pages do not set out either process.

Residential access usually has a strong location dependency. A second provider must have facilities near the premises, and two retail brands may still share poles, ducts, fibre routes or upstream buildings. A backup line is only useful if it fails independently and customer equipment can switch to it. The three named service areas demonstrate a footprint, not competitor availability or diverse last-mile paths at each address.

Address portability is another boundary. The /23 belongs to the operator at the routing level. That does not imply a residential customer receives portable space or a stable public IPv4 address. If customers are behind address translation, moving providers changes the visible address and may break inbound services. If a business receives a static address from AS154262, moving away may still require renumbering unless a specific portability arrangement exists. No public plan describes the address model.

DNS can reduce migration time for public services, but only when records, credentials and low time-to-live settings are controlled in advance. Backups help only when they can be restored outside the failed environment and the restoration has been tested. A copy in the same rack, facility or provider account is not an independent recovery path. These principles would matter if the company later sells compute, yet no present hosting specification describes them.

Commercial exit can be as important as technical exit. Customers need to know cancellation notice, equipment return, outstanding-charge treatment and the time between an order and a new activation. The product pages offer an application and monthly price without a public migration or termination schedule. That leaves the switching cost unknown until a buyer asks or tries to leave.

For the operator, the same issue appears at the supplier boundary. Portable APNIC resources may make an upstream change more feasible because AS154262 can originate its own prefixes through a new provider, subject to routing policy, contracts and configuration. But changing transit is not instant. It requires a new physical or virtual handoff, accepted route filters, route-origin validation, capacity, testing and operational coordination. If the only router or facility is unavailable, resource portability alone cannot announce the network from nowhere.

A credible recovery design would show customer and operator exits in parallel: a second upstream or tested alternative for AS154262, a second operating location or deployable spare, configuration backups outside the failed system, current equipment inventory, and clear customer procedures for data, addresses and cancellation. Public evidence shows the resource foundation for such a design, not the completed design.

What fails, who notices and who has to act

The service can be read as a sequence of failure domains.

At the premises, electricity, the optical terminal, router, cable and Wi-Fi determine whether devices can reach the access link. The customer notices first and may be responsible for power and local wiring. The operator needs diagnostic information before dispatching anyone. A replacement device can solve a local hardware fault without touching AS154262.

In the neighbourhood, a drop or distribution fibre, pole route, splice, cabinet or powered access device can affect one customer or many. The responsible field organisation needs location data, safe access, splicing tools and material. Neither an RPKI-valid route nor a healthy Makati rack repairs a broken strand in Tantangan.

On domestic transport, a damaged long-haul span or failed carrier service can isolate the South Cotabato access footprint from the declared Makati interconnection. Local optical lights may remain normal while Internet traffic stops. Restoration may belong partly to a facilities lessor or telecommunications carrier rather than the retail brand. The NTC's 2025 Internet-traffic guidance explicitly defines facilities lease agreements as contracts for telecommunications facilities or bandwidth capacity, reflecting how an ISP's service can depend on another authorised network's plant.

At VITRO Makati 2, rack power, cooling, cross-connects, routers and facility access become relevant. Vitro controls the building systems; the network or its managed-service partner controls its equipment and configuration according to contract. A facility can remain operational while one tenant's router fails. A tenant router can remain powered while its cross-connect is disturbed. Accountability requires component-level diagnosis.

At the transit boundary, AS153174 must accept and propagate AS154262's routes and return traffic. Aioni's wider upstream and exchange relationships then matter. A failure before that handoff isolates AS154262 from Aioni's diversity; a failure beyond it may be routed around if Aioni's policies and capacity permit. Customers see only that destinations stop responding or slow down.

At the commerce boundary, Shopify and associated processors support applications and account-related activity. A platform failure can interrupt ordering or messages without taking down the access network. The company must reconcile records and communicate through another channel. Its published telephone numbers and shop provide alternatives during business hours, but no broader continuity arrangement is stated.

Finally, support itself can fail. A disconnected number, invalid abuse mailbox, unavailable technician, missing spare or unclear supplier escalation can turn a short technical fault into a long outage. Operational capacity includes people who can act at the right location and time. Racks and routes are inert without authorisation and labour.

The people affected vary with the layer. A single home may lose Wi-Fi while neighbours remain online. A distribution cut can affect a street. A backhaul or AS-level routing failure can affect all three service areas. A commerce outage may affect new and existing customers trying to transact while current Internet sessions continue. A facility or upstream incident can affect every route that shares the boundary. Public status communication should distinguish these scopes so customers know whether to reboot, wait, call or fail over.

The questions that turn a footprint into a service commitment

The company has crossed several meaningful thresholds since 2025. It has its own AS number, portable IPv4 and IPv6 resources, valid route-origin authorisations, globally visible IPv4 announcements, a named upstream, a declared Makati facility and retail offers in three South Cotabato localities. Those are not trivial achievements for a regional provider.

The next threshold is disclosure sufficient for customers to evaluate continuity. For the access network, the missing facts are coverage at address level, access technology, customer equipment ownership, contention, measured performance, public-address treatment, planned-maintenance notice and fault restoration. For transport, they are carrier identity, route separation, protected capacity and failover results. For the Makati presence, they are rack arrangement, power feeds, cross-connects, remote hands, spares and a second location.

For support, customers need operating hours that apply to faults rather than retail visits, escalation methods, severity definitions and target times. For billing, they need activation, suspension, dispute, credit and cancellation terms. For data, they need system-by-system locations, subprocessors, retention, backup and export. For any future hosting offer, they need compute and storage specifications, backup responsibilities, recovery targets and a practical exit method.

The public evidence grade for the network is medium rather than weak because independent routing observations corroborate the registry and storefront identity. AS154262 was active and widely visible on the publication date; the prefixes were authorised; the upstream and facility claims are consistent across several sources. The grade is not strong because the evidence stops at the logical edge. It does not reveal the physical path from South Cotabato, the contracted rack and power, an independent second upstream, multi-site operation, current utilisation or repair performance.

The hosting evidence is weaker still. The company may operate servers for its own network or customers, but that possibility is not a public product. A facility presence and one observed hosted domain are limited public evidence to say otherwise. Buyers should not substitute an ASN page for a service specification.

That leaves a fair, specific portrait. Your Tech Electronics and Your Shop Enterprise is an operating South Cotabato access provider with a young autonomous system and a plausible interconnection chain through Makati and Aioni. Its retail identity remains visibly tied to an electronics shop, while its commerce layer depends on Shopify. The network is real. The public proof of hosted compute, spare capacity and failure-independent recovery is not.

The distinction is not semantic. When service is healthy, a customer sees a monthly plan and a speed. When it fails, the outcome depends on who can reach the local fibre, who can enter the Makati facility, whether Aioni still carries the route, whether the right spare is in the right city and whether the account can be restored without waiting for the shop to open. Those are the assets and obligations behind the bill. Until they are disclosed contractually, they remain the questions a careful customer must ask before treating advertised capacity as dependable infrastructure.