Summary

  • LACNIC's record types AS263191 a DIRECT ALLOCATION with status active, registered 15 November 2013 and last changed 18 April 2023.
  • At the 2026-11-20T00:00:00Z data point neither 179.60.44.0/22 nor 2803:f480::/32 was observed announced, with empty origin sets and zero filtered-out routes.
  • Across the fourteen documents read for this article, no numeric availability percentage, uptime commitment or service-credit schedule appears.

The custodian and the observers are not the same body

A registry allocation and a routing announcement are two different documents kept by two different organisations, and on this object they do not say the same thing. The authoritative side is small and unambiguous. LACNIC's RDAP object for AS263191 is typed DIRECT ALLOCATION, carries status active, records a registration event at 2013-11-15T13:42:51Z and a last change at 2023-04-18T20:10:06Z (LACNIC RDAP, autnum 263191). The registrant handle is CO-UDSO-LACNIC, the organisation name is UPTIME DATA SOLUTIONS, the address is Avenida el Dorado 106 39, Bogotá 110911, and the legal representative is Gerardo Gutierrez.

That record establishes holder and date. It does not establish use. The AS number object as returned carries no prefix and no route objects at all, so the registry is telling us who was given the number and when, not what any address is doing.

The observing side answers a different question. RIPEstat reports the holder as AS263191 - UPTIME DATA SOLUTIONS, places the number inside the block 263168–263679 recorded as assigned by LACNIC in the IANA 32-bit AS Numbers Registry, and returns announced: false for the query window ending 2026-11-19T16:00:00Z (RIPEstat as-overview).

Four prefixes, two sampled, zero seen

Third-party registration pages attribute four ranges to the number, all in Colombia: 179.60.40.0/23, 179.60.43.0/24, 179.60.44.0/22 and 2803:f480::/32 (WhatIsMyIP ASN page). One of those pages describes the /22 as a registered allocation managed by Uptime Data Solutions in Colombia, with 1,024 total addresses of which 1,022 are usable, located in Bogotá and attributed to the domain uptimeds.com (WhatIsMyIP CIDR page). My arithmetic on the three IPv4 prefixes gives 1,792 addresses in total — 1,024 plus 512 plus 256 — and the single IPv6 /32 contains 2^96 addresses.

I did not get a per-AS prefix list: the AS-number-level announced-prefixes call timed out during research, so nothing here asserts the complete set of prefixes the number has ever originated. What I have is a dated sample of two prefixes out of four.

For 179.60.44.0/22 at the 2026-11-20T00:00:00Z data point, RIPEstat returns announced: false, an empty origin ASN set, no related prefixes and num_filtered_out: 0; the enclosing 179.0.0.0/8 block is described as LACNIC, status ALLOCATED (prefix-overview, IPv4). For 2803:f480::/32 at the same data point the answer is the same shape — announced: false, empty origin set, zero filtered out — inside the 2800::/12 block designated to LACNIC on 3 October 2006 (prefix-overview, IPv6).

The documentation matters as much as the answer. The endpoint summarises whether and by whom a prefix is announced; announced is True if the prefix is announced and False otherwise, asns lists originating ASNs, and num_filtered_out counts prefixes removed by the low-visibility filter (prefix-overview documentation). The filter itself is defined on the sibling endpoint: min_peers_seeing defaults to 10 and is described as excluding low-visibility and localized announcements (announced-prefixes documentation). Because both of my responses returned zero filtered-out routes, that threshold did not manufacture the negative in these two cases. It could still hide a weakly visible announcement elsewhere on the number — a possibility, not a finding.

Three other tools point the same way at their own dates. Qrator's prefix view for the window 2026-08-14 to 2026-11-14 states No prefixes found, though its per-prefix tables sit behind a subscription lock and only the summary line was readable (Qrator Radar). IPinfo types the AS number Inactive with 0 IPv4 addresses, 0 IPv6 addresses, no prefixes, no peers, no upstreams and no downstreams, while still giving the allocation date as 15 November 2013 (IPinfo). And the SixXS Ghost Route Hunter table records the /32 under NetName CO-UDSO-LACNIC, owner UPTIME DATA SOLUTIONS, allocated 2013-11-15, at visibility 0% with the entry Last seen: never (SixXS Ghost Route Hunter). That last one is a historical claim by a tool whose participant set and update cadence are unspecified, and I treat it as such.

None of this proves the prefixes were never announced. A registry absence at one aligned timestamp is an observation about a dataset, not a biography of an address block.

The contact handle belongs to someone else

On the same RDAP object, the administrative, technical and abuse contacts are all one handle, UDS10, named TERASYS SAS of Bogotá, whose own registration event on the record is 2018-04-05 (LACNIC RDAP). My arithmetic puts that five years after the AS number was registered — four years, four months and 21 days, to be exact.

Outsourced registry administration is ordinary practice, and nothing in the record suggests otherwise. What the record does show is that the party a network engineer would email about abuse on this number is a different company from the party that holds it, and that the role entries were established long after the asset. When you chase a contact, you are reading a delegation, not an ownership stake.

TERASYS describes its own service in the language of standards: hosting client hardware and virtualisation in data centres construidos bajo estándares internacionales: Tier II y Tier III para garantizar alta disponibilidad (TERASYS managed hosting). The page names no certificate, and it prints no numeric availability figure and no credit schedule. That is a statement about a document, not about a building — design intent written as prose is not a certification, and I am not claiming the facilities fall short of it.

What "uptime" is worth in print

Uptime Data Solutions appears in a Bogotá company listing as a Sociedad por Acciones Simplificada, NIT 900527424-7, economic activity data processing and hosting, at Carrera 55 152B 68 Of 601 (Empresas de Bogotá). A tenant directory for the city carries one sentence about it: Uptime is a Data Center offering the most advanced technology in Colombia (Cargo City Bogotá).

That is the whole of the public claim I could obtain. Across the fourteen documents read for this article, I found no numeric availability percentage, no uptime commitment and no service-credit schedule. That is a count of what I read, not a claim about what the company publishes elsewhere; a company can run an excellent facility and never put a number on a web page.

So the ladder runs like this. The allocation has an authoritative custodian and a 2013 date. The announcement is a dated observation with a peer threshold attached to it. The contact is a delegation registered in 2018. And "uptime" is a word in a directory entry. Only the first of those four is a title. The other three are claims, and the gap between a title and a claim is exactly where a diligence file should slow down.