Summary

  • The directory entry for Denis F. Villorente records six autonomous system numbers as resources attached to that identity: AS132792, AS132793, AS132794, AS132795, AS132796 and AS136028, each recorded with country Philippines and a transit service label.
  • Public registry data retrieved on 17 October 2026 assigns five of those numbers to University of the Philippines campuses and the sixth to the Advanced Science and Technology Institute. None of the six records names a natural person as the holder.
  • The entry itself asks for verification of the person's current title, organisation affiliation, country context and relationship to infrastructure events, and the registry endpoints it cites as evidence did not return usable content when inspected.

Denis F. Villorente appears in the BTW directory as a person in the Philippines, recorded under the slug denis-f-villorente-denis-f-villorente and described as listed in registry records with administrative and technical responsibilities. The entry carries six autonomous system numbers. An autonomous system number is a routing identifier: it is the number a network uses when it announces reachability to the rest of the internet, and it is allocated by a regional registry to an organisation or an account rather than to a job title or a reputation.

When those six numbers are looked up directly, the records point somewhere else. AS132792 is registered to UPV-Miagao-AS-AP, the University of the Philippines Visayas campus at Miagao (RIPEstat AS132792). AS132793 is registered to UPV-Tacloban-AS-AP (RIPEstat AS132793). AS132794 is registered to UPMin-AS-AP, the University of the Philippines Mindanao campus (RIPEstat AS132794). AS132795 is registered to UPV-Iloilo-AS-AP, the Iloilo campus (RIPEstat AS132795). AS132796 is registered to UPB-AS-AP, the Baguio campus (RIPEstat AS132796). AS136028 is registered to ASTI-AS-AP, the Advanced Science and Technology Institute (RIPEstat AS136028).

All six sit inside the APNIC-assigned block 132096–133119, so they are allocations made in the Asia-Pacific registry region rather than resources imported from elsewhere. Five of the six were announcing routes on the query date; AS132794 was not. An announcement flag says whether a network was visible in the routing system on one day. It does not say whether a campus network is well run, whether its funding is secure, or who decides what it connects to.

That distinction is the point of this article. A registry record demonstrates that a named organisation holds a numbering resource. It does not demonstrate that a person exercises control over it. The entry under review converts an institutional holding pattern into a personal resource footprint, and nothing in the registry documents recovered here supports that conversion. The entry also records its own uncertainty: its data-gap field asks for the subject's current title, organisation affiliation, country context and relationship to infrastructure events to be verified.

That is an honest flag, and it is the reason this article tests the record rather than repeating it.

There is a second, narrower problem. The entry cites RDAP endpoints at rdap.org as its evidence basis. When the corresponding document for AS136028 was requested on 17 October 2026, it did not return usable registry content; the same request pattern for AS132792 failed in the same way (RDAP autnum 136028). The working alternative was the routing-data overview service, which returned the holder names quoted above. A cited source that does not resolve is not proof that an assertion is false, but it does mean the assertion cannot be checked at the address offered for it, and reviewers who follow the citation will arrive at nothing.

What can fairly be said about the person? That a Philippine registry-linked identity carrying his name is tracked with administrative and technical responsibilities attached to it; that the resources grouped under that identity belong, in the registry, to institutions; and that no document inspected for this article shows a decision, appointment, delegation or handover by him. What cannot fairly be said is that he operates, owns or prices the five campus networks and the science-institute network named in those records. Treating an institutional footprint as a personal one would inflate one person's control.

Deleting the person altogether would erase the only documented link between the name and the resources, which is the entry itself.

The pattern is common enough to matter beyond one record. Registry data is built to answer narrow operational questions: who holds this number, whether it is announced, which network originates it. Those answers are precise and useful. They become misleading when they are read as statements about authority, accountability or intent. For a reader trying to judge who is responsible for a campus network's resilience, the holder record points to the university, to its funding and to its IT governance — not to a name that travelled alongside the allocation.

Two practical tests follow. First, any personal attribution of a numbering resource should be reproducible at the registry endpoint cited, with the holder field quoted as it stands. Second, where an entry aggregates resources that the registry assigns to institutions, the entry should say so, and readers should be able to move from a person's page to the institutions that actually hold the resources. Neither test requires new data. Both change what a reader can conclude.

The wider accountability question is not whether one entry is right or wrong. It is whether a resource-visibility record should be allowed to stand in for an operating record. In this case it should not. The dated registry documents place these six resources with five University of the Philippines campuses and one national science institute; they place nothing with the person whose name appears beside them.